Closed geogan closed 1 year ago
OK I fixed this problem. Solution to enable running in V3 without problem is to NOT use Serial to send your tcode commands to the SR6. You must use the wireless Network option. It works perfectly like this. I still have to plug my ESP32 into USB to power it but it is not a USB on my PC that connects to actual computer, it is only a power source USB connection. So this "bug" only happens when you use the Serial option of say MultiFunPlayer or MOSA to send commands. Basically V3 / Tempest code does not work over serial. May be bug in that serial UART windows driver? No idea. Only problem now is no idea how to use MOSA over wireless - there is no option i can see - only serial port connection.
This issue was resolved in v0.25 correct?
Yes, this problem no longer happens. It seems it was caused by the t-code stream over serial somehow using too much bandwidth somehow... it was fixed when you changed something in firmware and/or Yoooi changed how commands are sent over serial from MFP I think. Now works fine for me over serial. I also just re-checked MOSA just now over serial, and that is working fine now too.
I have discussed this before, but no idea what the hell is going on.
I have noting out of the ordinary hardware wise. Use same ESP32 dev kit as everyone.
But I absolutely HAVE to keep this firmware on the V2 mode.
I tried again today to see if I could use the V3 mode (from admin page at http://tcode.local/) and it does as it always does - the SR6 goes absolutely haywire when any motion is sent to it. Tried MOSA and latest MultiFunPlayer (set to TCode-0.3 in its settings) - they both do same thing. As soon as motion is started the SR6 jerks, chucks, does not follow motion, appears to be damaging the servos.
Both these programs ONLY work for me when firmware is set to V2 mode.
No idea what's going on.
Using ESP32 v0.23b right now.