|
RomRaider
Documentation
Community
Developers
|
|
Page 1 of 1
|
[ 13 posts ] |
|
| Author |
Message |
|
XNWRX
|
Post subject: standalone reflashing device Posted: Sun Jul 15, 2012 4:34 am |
|
 |
| Experienced |
Joined: Fri Apr 06, 2007 6:09 am Posts: 116 Location: France
|
|
I'm thinking about something similar to Cobb accessport. I find some situations where I would like to switch from different maps, but the laptop way is a constraint. I'm sure Romraider generated maps cannot be used with an Accessport. But Tactrix could built a small device, very similar to the Accessport, considering OpenPort 2.0 already use an ARM processor and a microSD card for logging. Flashing kernel could be embeeded in openport and some kind of very simple HMI could be implemented. Another good solution (I know you will like it) would be to developp an app for smartphones. Everyone carry its smartphone in any occasion, and the smartphone has a USB interface, GUI, storage and processing power to perform such a very simple reflashing task... Any plan ? Thks
|
|
| Top |
|
 |
|
throttlehappy
|
Post subject: Re: standalone reflashing device Posted: Sun Jul 15, 2012 9:04 am |
|
 |
| Senior Member |
Joined: Sat Feb 12, 2011 7:27 pm Posts: 2031 Location: Northern NSW
|
|
Ezyflash is what you want. Will take 20 maps on one device
|
|
| Top |
|
 |
|
XNWRX
|
Post subject: Re: standalone reflashing device Posted: Sun Jul 15, 2012 9:36 am |
|
 |
| Experienced |
Joined: Fri Apr 06, 2007 6:09 am Posts: 116 Location: France
|
|
Thanks, didn't know this device. It seems compatible with .hex files from Romraider. But what about a smartphone app ?
|
|
| Top |
|
 |
|
throttlehappy
|
Post subject: Re: standalone reflashing device Posted: Sun Jul 15, 2012 12:20 pm |
|
 |
| Senior Member |
Joined: Sat Feb 12, 2011 7:27 pm Posts: 2031 Location: Northern NSW
|
XNWRX wrote: Thanks, didn't know this device. It seems compatible with .hex files from Romraider. But what about a smartphone app ? Yes, it is definitely compatible with RomRaider files. I have used it a few times for people who do not have a laptop(along with upgrading the tunes that are sold with the device  Smart Phone is a end point storage device in USB, it is not a 'output device' via USB
|
|
| Top |
|
 |
|
XNWRX
|
Post subject: Re: standalone reflashing device Posted: Sun Jul 15, 2012 3:25 pm |
|
 |
| Experienced |
Joined: Fri Apr 06, 2007 6:09 am Posts: 116 Location: France
|
What annoy me with ezyflash is that it encrypts data and that the device is paired with the ECU. And it is not a cheap device I'm not sure concerning smartphones as USB port on modern smarphone's Chipsets support OTG and master device. Could be an OS limitation then. Anyway, bluetooth or wifi included in the diag connector will do the job perfectly (I know one could worry about bad connection during reflash process)  Have a look at laplogger.com : http://www.laplogger.com/solutions.shtml?fily=dongle
|
|
| Top |
|
 |
|
throttlehappy
|
Post subject: Re: standalone reflashing device Posted: Mon Jul 16, 2012 1:00 am |
|
 |
| Senior Member |
Joined: Sat Feb 12, 2011 7:27 pm Posts: 2031 Location: Northern NSW
|
XNWRX wrote: What annoy me with ezyflash is that it encrypts data and that the device is paired with the ECU. And it is not a cheap device I'm not sure concerning smartphones as USB port on modern smarphone's Chipsets support OTG and master device. Could be an OS limitation then. Anyway, bluetooth or wifi included in the diag connector will do the job perfectly (I know one could worry about bad connection during reflash process)  Have a look at laplogger.com : http://www.laplogger.com/solutions.shtml?fily=dongleI have seen secondhand EcuFlash Units sell for US$250 which makes them perfect for containing a Valet map, a fuel economy map, along with a few maps with different boost levels and even a few maps for E85 or track days etc.
|
|
| Top |
|
 |
|
Nuke209
|
Post subject: Re: standalone reflashing device Posted: Thu Jul 19, 2012 5:34 pm |
|
 |
| Experienced |
Joined: Sun Oct 15, 2006 9:10 pm Posts: 195
|
|
Seems a bit more simple to just get a used accessport and accesstuner race
|
|
| Top |
|
 |
|
throttlehappy
|
Post subject: Re: standalone reflashing device Posted: Fri Jul 20, 2012 2:45 am |
|
 |
| Senior Member |
Joined: Sat Feb 12, 2011 7:27 pm Posts: 2031 Location: Northern NSW
|
Nuke209 wrote: Seems a bit more simple to just get a used accessport and accesstuner race Except AP only works on USDM cars
|
|
| Top |
|
 |
|
XNWRX
|
Post subject: Re: standalone reflashing device Posted: Sun Jul 22, 2012 1:35 pm |
|
 |
| Experienced |
Joined: Fri Apr 06, 2007 6:09 am Posts: 116 Location: France
|
|
USDM cars only, and not compatible with romraider .hex files. Anyone heard about the Blitz touch-Brain ?
|
|
| Top |
|
 |
|
wrxt4cy
|
Post subject: Re: standalone reflashing device Posted: Thu Aug 02, 2012 4:56 pm |
|
 |
| Experienced |
 |
Joined: Fri Mar 02, 2012 2:09 pm Posts: 183 Location: DSM, IA :: 2011 STi - Dom3.5XTR - E85
|
|
One of my winter projects is to look int making an Android based app for logging/reading/flashing. I completely agree that the OS world needs something comparable to the AP for quick configurable logging, seeing a learning view and of course reading and flashing.
It would only work on phones that support usb communication with a peripheral device. Many phones only support the basic protocol to allow them to have their storage mounted on a host device. As I understand it, some devices can be the host and of these, most should support a peripheral device like the Tactrix Open Port. Using this protocol would probably require root access as I don't believe its available in the public Android API.
I'm a Java software developer at my day job and I've written a few Android applications already so that's two hurdles I'm already past. My challenge is going to be gaining an understanding of how to communicate with an ECU. I'll need to figure out how to develop some custom drivers for the taxtrix as well. That could be a really big challenge.
So there could be a number of things that make to impossible or unfeasible but I don't even have the time right now to look into it all.
|
|
| Top |
|
 |
|
XNWRX
|
Post subject: Re: standalone reflashing device Posted: Fri Aug 03, 2012 3:08 am |
|
 |
| Experienced |
Joined: Fri Apr 06, 2007 6:09 am Posts: 116 Location: France
|
|
I'm a Blackberry guy, and Blackberry's OS does support USB host mode. New programming tools like Cascade comming with the new OS 10 plateform (QNX kernel) should be a great deal
|
|
| Top |
|
 |
|
dschultz
|
Post subject: Re: standalone reflashing device Posted: Fri Aug 03, 2012 10:05 am |
|
 |
| RomRaider Developer |
Joined: Wed May 20, 2009 9:49 pm Posts: 7314 Location: Canada eh!
|
wrxt4cy wrote: My challenge is going to be gaining an understanding of how to communicate with an ECU. I'll need to figure out how to develop some custom drivers for the taxtrix as well. That could be a really big challenge. Since the OP2 uses J2534 as its API, you would need the OP2 driver ported to your dev OS of choice (or reverse eng the driver to OP2 dev comms). Or go with something like an FDTI based cable and write against it's USB driver which is available to devs. The most universal interface for portable devices is BlueTooth, but there are no BlueTooth compatible cables that allow SSM to pass through them. All I've seen on the BlueTooth front are ELM chip based which want to get in the middle and do a protocol conversion for you, this breaks SSM unfortunately.
|
|
| Top |
|
 |
|
Sasha_A80
|
Post subject: Re: standalone reflashing device Posted: Fri Aug 03, 2012 3:39 pm |
|
 |
| Senior Member |
Joined: Mon Jan 19, 2009 2:31 pm Posts: 1615 Location: Moscow, Russia
|
|
| Top |
|
 |
|
Page 1 of 1
|
[ 13 posts ] |
|
Who is online |
Users browsing this forum: No registered users and 3 guests |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot post attachments in this forum
|
|