rusefi.com

Hi there,

Just got my rusefi board soldered together and firmware loaded via SWD.

However

Once I have connected Tunerstudio @ baud 38400 PC10/11, it works fine. Until I change any setting and hit burn, it automatically disconnects. If i reconnect without resetting the board it start right back up again fine. But once I restart/reset the board I get the firmware FATAL error RED led of doom!

Any known issue?

BTW, if I ground PD6 during reset it reconnects fine again "firmware reset"

Regards,
Joachim

Wow, you've taken the hardest route with our brain board!

Is it the latest firmware? Is it matching TunerStudio project .ini file? Please post a screenshot of TunerStudio - I am interested in bottom indicators, one of them confirms if version is compatible.

Have you tried connecting with rusEfi console once you get the red LED? It could have a better error message.

As an option try older bundles just to confirm it's not that latest version is broken - see https://svn.code.sf.net/p/rusefi/code/firmware_archive/

Hi, yes I usually end up taking the hardest route on everything unfortunately. Latest meaning probably two-three weeks old? Same .ini in tunerstudio.

Unfortunately the console will not connect once the firmware fatal is present.

I will try an older firmware and check

"version" is green so looks good. please post once you try an older bundle (firmware and project), for instance https://svn.code.sf.net/p/rusefi/code/firmware_archive/rusefi_bundle_20160706.zip

do you have a discovery board by any chance? discovery would allow you both TS and console simultaneously. Do you have the 20x4 LCD by any chance?

OK, a couple of good tries later...

The 20160706_2358 build works OK without the firmware FATAL error.

I have a couple of LCD's here, but i can't seem to get the 20x4 to work... "the 128x64 doesn't work either, just had to try..."

No, unfortunately I don't have the Discovery board. Although I am tempted to get one now.

When hitting burn I have to manually connect afterwards. Is this normal?


*edit: The 20160907_0025 build also works OK without he FATAL fault.

Just made https://svn.code.sf.net/p/rusefi/code/firmware_archive/rusefi_bundle_20161002.zip
Just reset/flashed/created new project using this version.
Via USB/TTL it works, no red light but yes, same loss of connection on burn. Added a comment to https://sourceforge.net/p/rusefi/tickets/276/

Via virtual serial (micro USB on discovery) it works, no red light and no disconnect on burn.

Which exact setting are you changing to get the red light on current version? I would love to reproduce this issue on my end.

OK, long story short. Tacho output set to PD11 gives the FATAL error led...

Somehow I can't replicate the dead comm's fault at the moment. But I will keep trying

I've misread your original error report a bit now I see what was going on!

PD11 is assigned as one of joystick pins by default (default firmware is for Frankenso board) so using it for tach output produces a fatal pin conflict. Good news is you still have TTL communication and you can still go change joystick settings in order to fix your configuration, right?

todo: https://sourceforge.net/p/rusefi/tickets/316/

PS: joystick pins are not visible on TunerStudio, let me fix that right now...

Joystick pins are now visible on TunerStudio project, give it some time to build new bundle. Thank you for discovering two issues!

What is this green wire next to the button?

OSH park had an issue with my boards, so instead of them replacing them i just "repaired" the ones i got. There was no connection to GND at C1.

Do I see another wire between the USB and push button? Is that a potential issue that should be resolved, or is that another MFG issue?

Heh, sorry you had to see that. That was my fault not reading the datasheet of the nuf2101mt1g before placing it, I placed it 180 degrees wrong and sadly the magic smoke escaped! So i budged the D-&D+ without ESD protection, it's fine on the bench but I'm getting a new filter before I put the board in my car

No worries. If you think that silk screen or anything like that could have helped, by all means let me know and I'll see what I can do to make it less likely to happen. What ever you say can only make it stronger. Keep up the good work, I look forward to seeing what you make of it, and how well it goes.

So... I'm having a new issue. Just benchtesting now before trying it in my car I noticed it shows double the actual rpm's.

Settings are 4stroke with cam, 60/2.
Primary PA5, crank - 60/2
Secondary PC6, cam - single pulse.

Thing is, when i choose 4stroke without cam, it shows actual rpm.

If i switch over primary and secondary it doesn't recognize rpm's.

Everyting measures ok on my digital osciloscope...

Snake____1 wrote:Settings are 4stroke with cam, 60/2.
Primary PA5, crank - 60/2
Secondary PC6, cam - single pulse.

this is super error-prone dialog at the moment, can you please post screenshots of both ways you were trying it with more details?

I am currently feeding a 60/2 signal directly via an Arduino, with built in cam generator. This runs at a steady 1000rpm.

Signal on the Crank input: Signal on the CAM input: TS 4-Stroke with CAM "correct way" Still feeding crank Secondary, and cam primary signals: TS 4-Stroke with CAM "inverted primary and secondary": And TS 4-Stroke WITHOUT CAM:

Unfortunately we have a usability issue here. Maybe a better choice of words is needed
"4 stroke with cam" does not mean that your first channel becomes cam. For your "60/2 with cam signal" you need to follow the http://rusefi.com/wiki/index.php?title=Manual:Software:VVT article. In this case your cam input is VVT (again, need a better choice of term since it's not VVT it's sync input in your case), and your 60/2 is the primary trigger input It's a mess, I can see how this would make zero sense.

I will post once I make some changes to the project files to reduce the confusion at least a little bit.

Tiny progress: secondary channel is now disabled for triggers where it is not needed, and "vvt input" is now "Cam Sync/VVT input" because that's what it is and that's what you need in your case.