Mitsulogger for iPhone??
Evolved Member
Joined: Mar 2008
Posts: 730
Likes: 3
From: Lattitude 48.38°, Longitude 17.58°, Altitude 146m = Slovakia, for common dude
http://pargon.nl/?p=6
Thats similar to the original adapter I put together, its original purpose was the allow sync to a physical serial port.. I had success at that time using the serial port and communicating to a host system (FROM THE iPHONE using a jailbroken phone and communicating with the host system using a serial terminal app for the jailbroken iphone)
If you notice the dock connector doesn't appear to have a complete serial port implementation, so you have to init the ECU at 5baud then switch to the communication baud rate.
These are nonstandard rates and therefore "Difficult" to convince the iPhone to do for you.
Thats similar to the original adapter I put together, its original purpose was the allow sync to a physical serial port.. I had success at that time using the serial port and communicating to a host system (FROM THE iPHONE using a jailbroken phone and communicating with the host system using a serial terminal app for the jailbroken iphone)
If you notice the dock connector doesn't appear to have a complete serial port implementation, so you have to init the ECU at 5baud then switch to the communication baud rate.
These are nonstandard rates and therefore "Difficult" to convince the iPhone to do for you.
Saves the effort for OBD part.
Very nice that development on loggers for cellulars have already started
jack i would give anything if i could log on my 3gs. i trust my phone over any computer lol. plus i was never able to get anything to work on my macbook running windows in a partition.
That's unusual, if you're dual booting it should just run like any other Windoze box. The only thing I boot into XP for these days is EVO tuning, DSMlink even has an OSX app.
this is a very cool devlelopment, I have become quite the iPhone programmer myself and I hope to have an app out soon.
I look forward to the future devlelopments on this..
I tried using it, couldn't get XP or 98 to install, kept getting hung at different points. For as little as I use it, I'll stick to dual booting, plus I had problems connecting to the ECU when running through virtualization with Parallels on DSMlink.
A little tease..
It doesn't do much yet, it basically just initialized the interface and gets back an acknowledgement when its connected.
Right now I'm evaluating Mono, MonoDevelop, and Monotouch for this, which made it a little easier to get this far.. But its getting there I suppose..
The hard part is actually getting information on how to recognize and utilize the accessory port (The same port that others are using to create external GPS devices and whatnot since it works almost identically) without using undocumented API calls.
It doesn't do much yet, it basically just initialized the interface and gets back an acknowledgement when its connected.
Right now I'm evaluating Mono, MonoDevelop, and Monotouch for this, which made it a little easier to get this far.. But its getting there I suppose..
The hard part is actually getting information on how to recognize and utilize the accessory port (The same port that others are using to create external GPS devices and whatnot since it works almost identically) without using undocumented API calls.
I dont know if this helps, im no software writer so dont know if its even poss but there is something called 'GPS serial' on cydia that uses the port on the bottom to connect to an external GPS antenna. Can you have a look inside the program to see how they do it? Its a free download..
Thanks for the info, I'm somewhat aware of the app, but its not really open source so its not really possible (the effort to get that info out of a run-time app isn't really justified)
I did want to note that the issue isn't getting it to work, its getting it to work properly in an app that can be downloaded from the App Store. Which means no "hacks" and private API calls. The issue I'm having at the moment is learning curve
And the nonstandard baud rates (and switching between them without resetting the connection)
This is definitely a challenge, and I can only say that "I'm trying"
A byproduct of the effort is The current version of mitsulogger has been rewritten in C# (actually refactored by some dev tools, then touched up to get working properly) and it mostly runs under Mono, and once I remove the windows specific FTDI driver dependencies, and get the comm libraries to work consistently, I'll have a version of Mitsulogger that runs under Mac OSX and Linux.
These efforts are always slow going due to my current life commitments that prevent me from doing much for long periods of time, but you guys will see a bunch of new tools and improved apps as they come together.
I did want to note that the issue isn't getting it to work, its getting it to work properly in an app that can be downloaded from the App Store. Which means no "hacks" and private API calls. The issue I'm having at the moment is learning curve
And the nonstandard baud rates (and switching between them without resetting the connection)This is definitely a challenge, and I can only say that "I'm trying"
A byproduct of the effort is The current version of mitsulogger has been rewritten in C# (actually refactored by some dev tools, then touched up to get working properly) and it mostly runs under Mono, and once I remove the windows specific FTDI driver dependencies, and get the comm libraries to work consistently, I'll have a version of Mitsulogger that runs under Mac OSX and Linux.
These efforts are always slow going due to my current life commitments that prevent me from doing much for long periods of time, but you guys will see a bunch of new tools and improved apps as they come together.
I'm actually glad to hear ECUflash is working under Mac OSX, It means that driver support for the openport cable has matured to the point where my logger should work alot easier than expected. I have to assume you don't tune under OSX simply because of a lack of logging tools..
I'm REALLY surprised virtualbox didn't work for you, I can understand having difficulty with Windows 98, I honestly wouldn't bother at all with it.. But XP installs with no problem whatsoever, I don't use VirtualBox as I use primarily VMWare (v7 Workstation is VERY vmHackintosh friendly) however I have installed Virtualbox on every platform I work with and it has worked fine.
I'm actually glad to hear ECUflash is working under Mac OSX, It means that driver support for the openport cable has matured to the point where my logger should work alot easier than expected. I have to assume you don't tune under OSX simply because of a lack of logging tools..
I'm actually glad to hear ECUflash is working under Mac OSX, It means that driver support for the openport cable has matured to the point where my logger should work alot easier than expected. I have to assume you don't tune under OSX simply because of a lack of logging tools..
ECUflash works great on OSX, as you said I don't use it only because there's no viable logging app yet. There is actually one called MacLogger, but it's not nearly as flexible as Mitsulogger or EVOScan.
http://www.cs.unm.edu/~donour/cars/libmut/
You may also want to check out some of the downloads from ECMtuning. They've done alot of work to get a nice version of their V3 app on OSX, and they've "given back" to the community by posting an update to the RXTX source with some fixes. Dunno if any of this will help you, but it's worth a shot.
http://www.ecmtuning.com/downloads.p...9hfnvdid41fhj4
I'm actually glad to hear ECUflash is working under Mac OSX, It means that driver support for the openport cable has matured to the point where my logger should work alot easier than expected. I have to assume you don't tune under OSX simply because of a lack of logging tools..
d
They've got ECUflash for OSX, comes in handy when I just want to open/save a ROM and not necessarily do any tuning.
I tried using it, couldn't get XP or 98 to install, kept getting hung at different points. For as little as I use it, I'll stick to dual booting, plus I had problems connecting to the ECU when running through virtualization with Parallels on DSMlink.
I tried using it, couldn't get XP or 98 to install, kept getting hung at different points. For as little as I use it, I'll stick to dual booting, plus I had problems connecting to the ECU when running through virtualization with Parallels on DSMlink.



im definately intrigued by this thread

