-
Armond30: No, it's not that simple. Just plugging in the correct hardware won't do any magic until someone writes software for the raspberry pi. I've looked into this raspberry pi idea, and it seems people are having problems with FTDI drivers with raspberry pi locking up. I think I'll go to my other idea, and just use a dedicated microprocessor to scan the serial frame, examine if it is valid, and if so, pass it to the LCDBC. By not using the built-in hardware serial, it will require a lot of processor time to collect the 1's and 0's and then use an algorithm to determine where the valid start bit is, etc.
DrGonzo: Have you tried ECU Delay = 10 (nearby the CEL menus). If this makes an improvement, then you may be in the same boat as Armond30 and fastbikes76.
-
I think that the most rational way of solving these problems is to send and ECU to BlackStealth and let him test it and come up with a solution. Solving this problem over the interwebs with various dongles and filters doesn't feel like the right solution giving how long this has been going on now.
We should also compile confirmed non-working ECU's so that people looking to buy the LCDBC know if they have a compatible ECU until these problems are solved.
-
I'll go in and change the setting and let you know how it works after that. I'm running one of Jesters Chrome ECU's so not sure is that qualifies me as being in the same boat as the other guys as I think they are using regular ECU's. I haven't been following the thread and don't have the time to go through 100 plus pages either.
-
Antero, I just wanted to make sure whichever unit I purchased (all I remember is upgrading to the 20Mg proc) will assimilate all of the updates/upgrades you've incoprorated lately - I'm about to install an Innovate LC 2 wide-band, and I have the latest ECUflash and EvoScan software.
Do I have any concerns?
Btw - thanks again for staying so totally on top of development on the LCDBC - you've set an enviable standard for accomodation and response time. :wink:
EDIT:
Referring to your firmware/software updates, sorry...:p
-
Anyone that is running firmware v3.xx can upgraded to the latest firmware 3.42. For most people they will choose the 20mhz processor, very few people have the 16mhz version. So no, there should be no concerns.
-
Aye, xlnt - I have the faster proc, so I'm good.
Thanks, Antero. :)
-
Not seeing the ECU Delay in the settings. I only see the screen refresh. I'm running the version where you added the WBO2 option for Pin 93 for the chrome ECU.
-
@antero
Can you modify the screen that shows Inj duty cycle to also show a max duty cycle reached with a push reset like the boost has?
It looks like there is plenty of room on that screen. Also a max duty cycle would be nice to know if we are pushing the inj too much.
-
Okay, I'll add that feature request in. There's an ECU cost whenever you monitor more parameters; the more you monitor, the slower or less frequent the other ECU parameters are monitored. So I'll add an extra Config Menu to enable/disable Peak Injector DC monitor. I'll also prioritize injector DC% such that RPM and Injector pulse width (ms) are asked in sequence to make it as accurate as possible.
-
Thats perfect! After you check it you can then just turn it back off until there are more changes to the setup made.
