You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using an ESP32 to read/write the serial of a TSDZ2 with OSF as part of some experimentation for a project. I'm using 9600 baud, and was able to read the incoming packets from the original firmware, including 0x43 start byte etc.
After that worked, I flashed the recommended opt data and OSF 1.1.1 according to instructions (with stmflash8 on Mac), and now this is the output I get on serial/motor tx after connecting the motor to battery (I'm printing bytes read in hex with a space in between, the "[nnnn] reset frame size" strings are debug messages) without having written anything to serial/motor rx from the ESP32 side:
if I reboot the controller, it will again start the same pattern, that will change after a few seconds, so this is repeatable and consistent.
I know to support my experimentation is way beyond the scope of the devs here, but I thought it might not hurt to ask: did anyone experience something like this, or has an idea where I could look what's going wrong here? I've read the OSF source (specifically ebike_app.c), and I'm not finding anything that writes to serial that would do this.
While I haven't been able to use it yet, looking at the source this seems like an amazing project where a lot of effort went into it. I'm very impressed. Thanks for all your time, I hope I can be of some help in the future.
The text was updated successfully, but these errors were encountered:
Hey,
this is not a bug report, but a question :)
I'm using an ESP32 to read/write the serial of a TSDZ2 with OSF as part of some experimentation for a project. I'm using 9600 baud, and was able to read the incoming packets from the original firmware, including 0x43 start byte etc.
After that worked, I flashed the recommended opt data and OSF 1.1.1 according to instructions (with stmflash8 on Mac), and now this is the output I get on serial/motor tx after connecting the motor to battery (I'm printing bytes read in hex with a space in between, the "[nnnn] reset frame size" strings are debug messages) without having written anything to serial/motor rx from the ESP32 side:
if I reboot the controller, it will again start the same pattern, that will change after a few seconds, so this is repeatable and consistent.
I know to support my experimentation is way beyond the scope of the devs here, but I thought it might not hurt to ask: did anyone experience something like this, or has an idea where I could look what's going wrong here? I've read the OSF source (specifically ebike_app.c), and I'm not finding anything that writes to serial that would do this.
While I haven't been able to use it yet, looking at the source this seems like an amazing project where a lot of effort went into it. I'm very impressed. Thanks for all your time, I hope I can be of some help in the future.
The text was updated successfully, but these errors were encountered: