rusefi.com

5ms timeout?

puff wrote: ↑

Sun Feb 19, 2023 11:36 am

5ms timeout?

Please use more words

there seems to be a 5 ms pause between these two bytes - could be a timeout

puff wrote: ↑

Sun Feb 19, 2023 6:05 pm

there seems to be a 5 ms pause between these two bytes - could be a timeout

So we both see two bytes on the wire yet my code fails to read at least one byte. At the moment I would be happy to just read one byte. Not sure how is that 5ms relevant for my current cry for help to read one byte

what's the schematics? which exactly wire is that? kline usually works at much higher levels (12v).
can it read bytes sent from usb-uart adapter?

Thank you!!! That's actually an amazing idea for me to try next.

It's https://github.com/rusefi/rusefi_documentation/raw/master/Hardware/Hellen/hellen125honda-a-schematic.pdf it already after the LIN transceiver so I show RX exactly how it goes into stm32. had to add a 1K pull-up since that's missing in the schematics at the moment

"No LIN transceiver is fully compliant to the K-LINE, but compatible. You can see the difference from the document. So I think TJA1021 can work"
https://community.nxp.com/t5/MPC5xxx/TJA1021-K-LINE-compatibilty/td-p/550725
unfortunatelly, it's 403 for me.

rusEFI discovery, adafruit, secondary serial feature with perfect timing https://github.com/rusefi/rusefi/issues/5105 fix

9600 and 14400 works while 10400 does not work. Smells like uart configuration magic?!

10400 is not supported by some usb-uart converters... (that's why people prefer ft232)

I got a chance to try my fake cheap eBay 16 channel logic analyzer! Looks like CP210x has performed as expected at 10400?

10400 9600

you can tell for sure by measuring the length of the start bit probably.
still, didn't get: it doesn't work even when bytes are sent from the usb-uart dongle? so, it's a firmware bug?

puff wrote: ↑

Sun Feb 19, 2023 11:06 pm

you can tell for sure by measuring the length of the start bit probably.
still, didn't get: it doesn't work even when bytes are sent from the usb-uart dongle? so, it's a firmware bug?

As a test step I've decided to run proven and known to work TS protocol at 10400 not k-line connector. And at the moment TS protocol does NOT run at 10400 which makes me stretch my head and post https://forum.chibios.org/viewtopic.php?f=16&t=6194 wondering if I can blame stm32 or ChibiOS

please use a dedicated thread instead of clogging a pinned announcement thread

mck1117 wrote: ↑

Sun Feb 19, 2023 11:12 pm

pinned announcement thread

What pinned thread? What announcement thread?

Wow just wow.

The fix for https://github.com/rusefi/rusefi/issues/5354 turned out to be https://github.com/rusefi/rusefi/commit/1e43299eab2b2af033cb79d03446dbf07e4bd2c3

F4 does not seem to care. F7 cares deeply but compiled only throws us under the train at -Os optimization level.

Kudos @dron_gus for fixing.

Daihatsu 4 cylinder cam trigger added https://github.com/rusefi/rusefi/wiki/All-Supported-Triggers#daihatsu

Anyone with a Bluetooth board interested to test https://github.com/rusefi/rusefi/issues/5927?

Time flies - it has been over three years since @mck1117 has contributed that amazing performance tracing!
@andreika has just fixed a defect reviving it and I've added a touch of usability.

I have some questions around high frequency CANbus processing with Lua let's see if PTrace would be the magic tool.

@dbh97 has revamped the build scripts! I expect way less broken local proteus builds now.

ADC sample value just a bit above 12 bits, that's not what one would expect from stm32f7?

Do we have a wild memory overrun which just happens to touch ADC region? Are we not good at reading that ADC app note? Else?

That's https://github.com/rusefi/rusefi/issues/6376