Hi ! I will take from the easiest to the more complex
It looks like you have parasite or power source is droppping making the serial chip "failing", in this case Simhub will disconnect, but there was a bug in the .net framework (the development environment I use) where the whole application could shutdown when the serial port was failing or being disconnected (the System.ObjectDisposedException error of death) , after years of wait microsoft finally released a fix in april, and it will be enabled with next simhub version (if you are curious
:
https://github.com/dotnet/docs/blob...re/serialport-background-thread-exceptions.md ), I waited for this fix for really long, and even when they finally fixed it, it took me a few months to find it
Concerning Afterburner, the plugin is enabled in the general setting and it will poll from time to time to see if data is available, but the technology behind it is a little archaic and requires to try to open data and see if it fails (which will leave these logs in debug mode), no worries here, it's just the effect of the debug mode tracing everything.
Concerning "speedlevel" it's the baud rate, I've renamed it for the next version to remove the mention of this simhub internal "naming' which has not much sense except for me, it's only the serial port speed (baud rate). 115200 is a safe and still fast value, no need to play with it, at best it would go slower if you reduce it, but in your case 115200 can't be an issue (pushing far above like 1Mb is another story
)
Concerning the sketch voltage "cap", I've removed it (it used to exists in old legacy version of shakeit) but after a few years I've seen that these motors even powered at 12v would hold it with no troubles (they are rated technically for 3.5v approximately, but 12v make them much more responsive) : However you can still cap the whole output directly from simhub using the general power slider, it has the same effect that this deprecated setting :
View attachment 276393
Finally for the real problem, arduino disconnecting, I see multiple causes possible :
- USB hubs : they are hell ... avoid them
- Parasites or insufficient power source or cutting which are going back to the arduino and "kill" the serial chip, the sensibility of the chip will highly depend of the serial chip itself (CH340G, FTDI, ATMEGA ...) :
In this last case I see two solutions :
- This one using the power screw plug instead of the barrel jack, it will isolate power source from the arduino and so reduce parasites or voltage drops making the ship going mad :
https://learn.adafruit.com/adafruit...power-supplies-for-the-arduino-and-motors-5-4 (you don't need to power the arduino in this way, the usb powering is sufficient)
- This one which is intended to solve motors parasites, but I've not seen anyone requiring that until now:
https://learn.adafruit.com/adafruit-motor-shield-v2-for-arduino/faq#faq-17
Finally, it could be a little sneaky, shorts ? When playing with motors they shakes (that's the objective
) and could trigger a little short somewhere on the connection ? By experience some serial chips hardly recovers of voltage drops and require a proper disconnect/reconnect cycle to recover.
Ouf ! That was a long speech ! I hope it will help