I am also currently updating all of the plugins, and then goign to try to update octoprint.
after updating both octoprint and the plugin, it restarted octoprint when I tried to connect
now stating that it "could not connect sio"
I have now gotten the same error message 3 times in a row, without crashing. said error message is that the "sio device incompatible". I am currently using an elegoo uno r3
Ok.. this is indicating that the device is not responding to the "VC" Command.
Unexpected(valid) Comm during compatibility check:IO:00000
2024-02-16 11:35:42,169 - octoprint.plugins.siocontrol - DEBUG - resetting comms resending VC request
It should send back the compatibility lines but it is sending back some Debug message.
Which of these do you have in the firmware on line 92
bool _debug = true;
or
bool _debug = false;
If you can it would be good to just connect to it with a terminal program and send it the VC directly and see what its response is.
I have it set to false, should it be set to true?
after connecting the arduino to the serial monitor through the IDE, and sending the VC command I get back "DG: "
No, false is good. When it is true it can add a lot of noise to the comm... I thought maybe you had turned that on.
If your board has a "reset button" on it, try hitting that and then try to reconnect in the settings dialog. I had a user that was using a Nano where this solved some issues for him because the nanno was resetting and getting in a bad state when the usb line was connected. Your board might be doing something similar. (Long shot)
I think you will need to connect to it with a terminal program and send it the VC directly and see what its response is. So we know it is capable of responding to that command.
after looking at the documentation on Serial Communications · jcassel/OctoPrint_SIOControl_Firmware Wiki · GitHub
I have tried multiple commands and none of them have worked, just giving me a blank response.
How would I go about connecting to it using a terminal program, instead of the IDE monitor system
The Arduino IDE monitor is just fine.
We know it talks. We see data in the log. So if you are getting nothing you likely do not have a good connect in the monitor
How would you suggest fixing this?
First make sure OctoPrint is not still connected to it.
Try resending the firmware to it and open the monitor window. Hit reset and it should report some diag. Then go into the ioreport which sends out the IO State every second or 2.
Once you have that. Issue the VC
Gather results for review
I have sent the firmware to the board again, and I have opened the serial monitor. I hit the reset button, and then watched it start up. it then started sending "IO:0000" three times, and then saying "RR". it kept looping this, I then sent the VC command, and it returned a message of "DG: ". did I miss a step or is this just not working?
also when I attach the button I have set up, it will return "IO:0100" whenever I click the button
The message returned for VC
That is the issue. Not sure why you would get that.
here is a screen recording of it restarting and reacting to commands that I send it
what is the response I should be getting when I send the VC command?
According to the firmware you sent me... Not sure if it is really what you are using.
Should return:
VI:SIO_Arduino_General 1.0.8
CP:SIOPlugin 0.1.1
And then continue to send the IO:0000 and RR repeatedly.
The VC response is how the PlugIn knows it is able to talk to the device and that is is compatible with the commands it will send it. It is also there to ensure that if I make changes in the PlugIn in the future this is how I can be sure that the device can support new commands and the like.