rusefi.com

What do we know about msDroid?

There is http://www.msdroid.com/ which has MS all over it but not much info like the license or source code link, if this software is open source. Does anyone know anything about msDroid?

It is not open source. If you have any specific questions about the software, I should be able to answer (I do have source code access) so I should be able to help. Just hit me up on Skype.

Well, it's a show stopper I guess.



update: there is also http://dtadroid.com/

The bottom line of that is that we don't want to promote counterfeit MS (anything that is against the MS licensing). Since rusEFI doesn't fall into that category, I don't see any problem to support it.

DTAdroid is pretty much just a rebranded MSDroid (95% same code) to be used with DTA ECUs.

you managed to connect? bluetooth or usb? how do i enable otg or whatever is needed? (my android recognizes usb drives, so i guess otg works fine)

this programm support only ftdi usb devices?

USB FTDI, USB Prolific and Bluetooth

that's a pity. what bluetooth data rate is required? (we have to set up speed of tuner studio port and the bluetoot module)

Can you elaborate on why it's a pitty please... The app doesn't care about the bluetooth data rate, that's between the bluetooth adapter and the ECU.

Can you elaborate on why it's a pitty please

i presume the usb used in discovery board is neither prolific nor ftdi. It's a ChibiOS/RT Virtual COM Port (PID:0x570, VID:0483 - STMicroelectronics), and that's what is a pity.
For some reason I couldn't connect to it via bluetooth either (got the log file). I added rusefi.ini to the corresponding folder, but it didn't help… Besides, it seems my screen is too small: when I open the can pass through settings - they are never saved, probably, there should be a 'save config' button but I don't see it.

FTDI makes a chip specifically for androids http://www.ftdichip.com/Android.htm

The data from that FTDI chip is either TTL or typical 232.

From my quick research, sounds like we're dealing with a CDC/ACM USB device. Support for that would need to be added to the app. Possibly this would work?: https://github.com/ksksue/PhysicaloidLibrary/blob/master/PhysicaloidLibrary/src/com/physicaloid/lib/usb/driver/uart/UartCdcAcm.java

I am pretty much sure this should help. I'd like to be among the first beta-testers If you add this support I wouldn't need to mess with soldering ftdi chip on frankenstein
Bluetooth is a separate problem. What is strange is I am able to pass communication test easily with tuner studio, but it does not work with msdroid. Another strange observation is when in bluetooth mode my tuner studio works sort of a slower than with direct usb connection working at the same speed. As Andrey says, in usb connection baud rate doesn't make any sense, the board works at the maximum available speed, and this could explain everything. Or, when in Bluetooth mode it might be overflooded with errors, which makes bluetooth connection work slower

why msDroid send "Q" and "S" symbols when in rusefi.ini defined "H" ?

I downloaded rusefi.ini and moved it to msdroid ini files directory . connected power to bluetooth , connected tx line to logic analyzer . Started msdroid , pushed "connect to ecu" , and started recording on the logic analyzer programm .

In msdroid logs i saw rusefi.ini file , but it doesn't use definitions from rusefi.ini

[video][/video]
it's works !

but having some problem : gauges from this error doesn't works .

update rusefi.ini from 28 january to current .
added 2 new errors and msdroid doesn't connect to rusefi :

Was that a bluetooth module? If so was it a ITEAD_HC-05?

it was HC-06 bluetooth module

If only we had a chance to troubleshoot this with the *droid developers

Tryed to connect it again
Used last version of rusefi simulator and rusefi.ini . Connected via wifi
But something went wrong

Такое ощущение, что он не нашёл rusefi.ini на телефоне? или нашёл, но ему не понравилось?

ещё бы знать, как туда этот файл помещать...
с ДР!

файл то нашел , закинул его в /sdcard/msdroid/ini
когда в ini меняю signature на ту что выдает сообщение ошибки , в следущий раз в сообщении она выводится уже не 2 а 3 раза


спасибо)

@ you were asking for the status of msDroid. The status is unclear - I have no idea why does not not work and if the problem is anywhere on the rusEfi firmware side or on the msDroid side. Unfortunatelly msDroid is not open source so we really depend on the author

@russian ok. I heard you. I make connect with autor and ask him manual to connect rusefi to MSDroid