Existing command TEST_RESONANCES not found in RatOS override
Hope someone can help me with this..
I have freshly installed and updated ratos to 2.1.0 RC3.
From the first step to set up the wifi I see the error in the subject. First updated ratos, then configurator and then everything else. I still see this error.
I have a btt octopus pro 1.0.1 446 and a pi4b (2018)
Rapido 2 UHF
I have tried to set everything up in the configurator and used dfu on the board and after that the toolboard ebb42 v1.2 wich was detected and dfu was succesful. Then I set everything up in the final steps which also was ho problem. But when I selected the save button suddenly it Saïd it couldnt find the toolboard.
After a restart in mainsail (host shutdown, waited for green light to go out and then rebooted the system) I can no longer set the toolboard. I attached the pictures.
5 Replies
Pick an accelerometer for X and Y and it'll stop complaining. This bug is fixed in development, but has not been merged yet.
Thnx will try that tomorrow. Do you have an idea about the ebb42 or any other board not being able to show? The error is in the pictures. I was able to dfu and flash but in the end it was not being detectied anymore
It's caused by the same bug
I was able to dfu and flash but in the end it was not being detectied anymoreHow? I'd try a reboot, go back to printer selection, select a different printer, then select the VC3 500 again (click Start Fresh, when prompted) and proceed through the configurator. That will most likely solve the issue, make sure to select accelerometers in the hardware configuration page.
Yeah it was connected and seeing the toolboard when i was doing the configurator steps. Also dfu manual and then flash the board where succesful.. at the final step to save it said not found all the sudden. But the green and blue light on the toolboard are still on. Cable is Apple iPhone original cable.
I will look at your suggestions tomorrow Morning and report back. Thnx for your input!
That was the solution for all the problems. The toolboard was recognised again and klipper has no errors for this topic. Some other minor issues to be solved but if needed ill open another post. Thanks for your help!