Firmware developent status

[puff]

couple of not really issues (not sure about usability either):

when you disconnect the board, the devcolsole in its caption bar still says that it's rvr8 (empty engine line expected)
when you disconnect the board, you can still see the phantom engine sniffer (on the other hand this might be handy - you can see the last data of the ecu).

I still see the difference of 0.1 ms between duration of each two pulses on spark 1. (however, it seems the board now gives much better accuracy in terms of RPM)

When you do spark or fuel bench command - you can't see it in engine sniffer (needs confirmation - i couldn't manage to see anything there)

btw, now I get an error regarding the absence of some xml file (for maps editing) - sort of a bit confusing (where do I get the one?).

[AndreyB]

btw, now I get an error regarding the absence of some xml file (for maps editing) - sort of a bit confusing (where do I get the one?).

I want a screenshot.

that's probably about the romraider part we are using for table editor - should be in the same folder with the bunlde, rusefi.xml - you should not be taking it from anywhere.

[AndreyB]

When you do spark or fuel bench command - you can't see it in engine sniffer

https://sourceforge.net/p/rusefi/tickets/174/

[AndreyB]

new feature: timing advance correction by intake air temperature and RPM.

Here is the default correction table:

[AndreyB]

when you disconnect the board, the devcolsole in its caption bar still says that it's rvr8 (empty engine line expected)

done

[puff]

I don't have it.
I'm using this link: http://rusefi.com/build_server/separate_files/rusefi_firmware.zip

[AndreyB]

not latest
separate_files is probably the issue here - you need to download the full http://rusefi.com/build_server/rusefi_bundle.zip
I will pack the console with the file into the single files folder, the .jar alone would not work any more. Thank you for the defect report!

[AndreyB]

the bundle now comes with two versions of the binaries - a faster one, and one with more sanity checks

the faster one is recommended for bikes or guys with 60/2 trigger, everyone else should use the one with more checks. https://sourceforge.net/p/rusefi/tickets/171/

[AndreyB]

http://rusefi.com/forum/viewtopic.php?f=15&t=644&p=14926#p14926

[kb1gtt]

Very nice, very nice.

[AndreyB]

New feature: TPS-based acceleration enrichment.

TPS needs to be in FAST adc moce


New parameters are available in TS


Enrichment could be monitored via TS


New commands are documented @ http://rusefi.com/wiki/index.php?title=Manual:Software:dev_console_commands#Acceleration_Enrichment

[puff]

still no rusefi.xml in separate_files?
downloaded the zipped bundle, put rusefi.xml in the same folder with devconsole.jar, run devconsole and got
Error reading from rusefi_console_properties.xml in terminal.
Is that supposed behavior?

[AndreyB]

Error reading from rusefi_console_properties.xml in terminal.
Is that supposed behavior?

That's totally fine, I've just made the message less scary.

[puff]

will you please add this rusefi.xml to the separate files folder?

[AndreyB]

will you please add this rusefi.xml to the separate files folder?

Done - http://rusefi.com/build_server/separate_files/

[AndreyB]

New feature: "use only front" of the trigger signal, I believe that's the right way to handle VR signal, also a performance optimization in case of a high-number tooth wheel.


https://sourceforge.net/p/rusefi/tickets/172/

[puff]

Done - http://rusefi.com/build_server/separate_files/

can't see it!

[AndreyB]

can't see it!

http://rusefi.com/build_server/separate_files/rusefi_console.zip

[AndreyB]

Good progress on https://sourceforge.net/p/rusefi/tickets/167/



Still need to implement 'enable/disable' pin logic

[AndreyB]

30% performance improvement of trigger handling logic - https://sourceforge.net/p/rusefi/tickets/181/ - not sure if there really was a problem there in the first place

[AndreyB]

More open issues with Tuner Studio - https://sourceforge.net/p/rusefi/tickets/182/ & https://sourceforge.net/p/rusefi/tickets/183/

[AndreyB]

Usability: https://sourceforge.net/p/rusefi/tickets/188/ - ADC fast/slow mode is now hidden from user, this is now configured automatically

Also some progress with dev console

[AndreyB]

vehicle speed sensor decoding works - http://rusefi.com/forum/viewtopic.php?f=3&t=696&p=15109#p15109

[AndreyB]

[Number-One]

Nice.

[AndreyB]

Usability: it is now possible to change injection & ignition pins assignment on the fly. This should make things easier while setting everything up.

todo: make most/all pin assignments configurable on the fly. https://sourceforge.net/p/rusefi/tickets/198/

[AndreyB]

Usability: CLT and IAT curve parameters are now applied without reboot. https://sourceforge.net/p/rusefi/tickets/201/

[kb1gtt]

Just for clarity to potential contributors. I understand the goal is to offer diagnostics information, and not to spoof the messages like VIN, or govt emissions codes. The goal is to only provide diagnostics like TPS position, flow rates, temperatures, ect and we can offer MFG error codes. I understand the MFG codes like P1XXX are OK to offer, but codes like P0XXX are government controlled and not OK to play with. The 0 is mandated codes, and the 1 is MFG codes. I don't know what 2-9 would be.

[puff]

shit! you are aware of any legislation regulating the use of those codes?
actually, i dont think it makes any difference since probably these aftermarket ecus are totally forbidden on pubic roads.

[kb1gtt]

Regulatory issues are very hard to track and follow. They vary based on a variety of un-clear boundaries, so I wouldn't wager a guess about what the potential issues are in different parts of the world. I have a basic idea of what they probably are in my neck of the hundred acre woods, but I don't know squat about your area. For example, I understand China has basically no regulation on this kind of thing, while California will probably put you on a death sentence.

Back around 2002, I got to read a physical copy of the the OBDII spec. My gray matter remembers it like this. California wrote the spec, and mandated it's compliance for car's to be sold in CA starting after 1996. They originally mandated many emission codes and established a list of basic diagnostics features. They also created an area were OEM's could pass what ever information they needed for diag purposes and such. The spec back then also laid out the different categories like P for power train, and codes for ABS, SRS, body, ect. At different dates, various codes like ABS were made mandatory.

Most OEM's complied with the OBDII requirements and started offering it world wide. As it became common place many other areas started using it for various purposes. For example, in NH if you get a OBDII code that you can't remove, you can not get inspected which means you can not use your car on the road. If you inspection sticker is the wrong color or non-existent you'll get pulled over and mean nasty things will happen to you. The scan tool looks for your VIN and specific codes. I'm sure tampering with that process is illegal, and I would say do not try it. I know several people who have suffered significt finical hardship due to these check engine light issues. Nothing wrong with the car's emissions or safety, but that doesn't matter in NH. I also know CT doesn't have any inspection until you car is 10 years old. Then you only have inspect the car when you sell it. Also they require SMOG ever 2 years. You have to bring it to there station and they don't care how you pass as long as you pass. So they have a completely different approach than NH.

Dealing with P0XXX is very dangerous, and that's not what this project is intended for. However I'm also not the law and I don't know of any specific regulatory issues. So all I'll do is recommend it be used for track and non-regulatory controlled applications.

While it could be perfectly legal to wave a toy gun around as you run down a city street, I don't recommend that either. In general use your brain or you'll get in trouble.

This is getting a bit OT, so might as well stop talking about it. I just wanted to write a brief explanation of what features we expect to be developed some day.