rusefi.com

Tuner Studio reports a difference. TS engine type is Ford_Inline_6_1995, the controller engine type is GY6_139GMB.

Accept the TS setting?

Not sure. This particular part - adjusting engine type via tuner studio - is still very raw. You would need to flip a coin

I created the rusEFI TS project a week or more ago. I'm still using the original .ini file, not the latest one I downloaded today. I'll have a look and see if I can spot any differences. Seems to me the file size on the latest one is larger.

Page size in the latest rusefi.ini file is 3144, in the mainController.ini file I have page size is 3004. There are some other differences but at this point no matter. I was able to connect and that was the object. TS can wait until development matures.

e4odnut, i suggest that prior to instaling everything on the boat, you'd get a logic analyzer (devcon's logger is good but it doesn't reflect the hardware levels which is important from my point of view)
russian, we still need make it clear where does the firmware take the settings: from setenginetype command in devcon (i am fond of this abbreviation, though might sound confusing) or the ini file derived from the build server. what's the difference between these two types of setting everyhing, why is it needed, etc.
personally i don't know much. setengine writes some value to eeprom and chooses algos in accordance with ghis value. besides, from ts's point of view this value is a bit shifted. two weeks ago when i set the deired type of engine in ts, i got it also cnged in xevcon, and these two enginetypes were not equal. i don't know whatshould have been changed to fix it: ejther ts, or the ini file, or the devcon...

"buzz click buzz click (or what ever robots make for noise)

I see content, must assimilate http://rusefi.com/wiki/index.php?title= ... _TTL_cable assimilation complete.

buzz click buzz click (or what ever robots make for noise)"

Ha ha ha , you´re funny

puff wrote:russian, we still need make it clear where does the firmware take the settings: from setenginetype command in devcon or the ini file derived from the build server. what's the difference between these two types of setting everyhing, why is it needed, etc.
personally i don't know much. setengine writes some value to eeprom and chooses algos in accordance with this value.

This is a great question! I will try to explain it and maybe this would even be assimilated...

There is no difference. Tuner Studio and devcon are just to doors into the same areas of RAM and EEPROM. Once you set new value via TunerStudio, you can see it via devcon if there is a command, like 'showconfig' or something. Once you set it via the devcon, you kinda should see it via Tuner Studio - but I am not sure how to do this, it could be that Tuner Studio is a one-way street it would be surprised if values change outside of TS. That's in theory - in practice devcon would also reboot the firmware automatically, and this is still a TODO for tuner studio. So, they are changing exactly the same areas of memory - but some minor details are different and sometimes that's noticeable.

puff wrote:from ts's point of view this value is a bit shifted. two weeks ago when i set the deired type of engine in ts

Contrary to the first part of the message, this is not helpfull. Two weeks ago? No steps to reproduce? That's not helpful, that's spreading rumors. In order to make things better I would need more than "two weeks ago I did something". Two weeks for this firmware is like 2 years of life. And I need EXACT steps to REPRODUCE. Without an ability to reproduce, there is very little ability to fix

now it seems i got what happened. i set fiesta in ts butwithout rebooting i got iniially set aspire in devcon
ps we probably need better, more informative help messages forcertain commands...

kb1gtt wrote:When it comes to sniffing serial traffic with putty, I have had good success with com0com...

http://rusefi.com/wiki/index.php?title=Manual:Software:Serial_protocol