I finally got around to upgrading my firmware from 1.1.1 to the latest version via flashing a new SD card.
I have two issues: one annoying, one disabilling. 1. my wifi controller needs reconfiguring (mode change) whenever I use it after it has disconnected/gine to sleep. Annoying, but not a showstopper.
My real issue is the latter. The controller no longer communicates spindle speed requests to my VFD.
What I Did:
I maticulously screen snagged all my existing controller settings.
I flashed a new SD card with the latest firmware image
I replaced the old SD card with the newly imaged card
Switched on the controller.
I re-typed in my previous controller settings. I used the custom VFD tool setup.
The controller and VFD communicate with each other (no comms error messages, it is a modbus comms setup).
The controller is unable to make the spindle turn either via a gcode file or midi instruction.
Next Action:
Ask the forum if anyone has experienced this or has any suggestions
put the old previously working sd card into the controller and see if that still works.
The latter action i will do tomorrow.
Any and all thoughts welcome. I hope it is something daft i’ve done.
I haven’t put the old sd card back yet (a few family tasks to do first). also It is a fiddle as i have mounted my controller under the table. Which must be ok as i had little dust accumulation inside the controller.
I did use a ‘S’ . Although i also doubted myself with respect midi so i created a small 2mm deep pocket file, which loaded but failed to fire the spindle into action.
With The configuration i have the VFD sends the spindle RPM back to the 1F controller which then presents the gcode requested speed alongside the VFD speed. what might be interesting to share is that the returning VFD speed to the controller is not 0 (whether running gcode or idle) but some random 2-digit number around 54 rpm. It varies +/- 4 rpm but essentially a stable number. Makes me think the controller is getting a rogue signal. I haven’t changed the VFD config (i shouldnt need to) and controller states thay comms are good.
Note: My control cable is shielded. Also i have not changed anything else. Note whilst it is a bit nippy in the UK my shed is rarely below 5 degC.
I would try that first since with new firmware you never know.
But what you describe could rather be that you impacted the proper connection somehow when fiddling with the open controller while exchanging the card. Bad connection or something like that. I would check the seat of the DB-25 I/O connector. It is a source of faulty connection, as was reported sometimes.
Agree. The connector can be flakey. I did give it a tweak. Plus checked the holding screws.
But they are communicating . The VFD is configured to go to stop state and require a reset if a check signal is not received from the controller. But all is good. Likewise the controller states a good connection.
Gymnastics!!: you have the correct image; dusty back from lying on the floor, strained neck muscle from checking and double checking cabling.
I enjoy that very much too everytime just have to replace a few hard disks on the computer that is the lowest been avoiding for days already
Regarding CNC Controller, I plan to put it next to the VFD control cabinet, would be good for you too at the moment, if it was next to your VFD . But I know, the Onefinity cables
This seems as there is a bad noise over the signal, but the connection is a balanced connection, so it’s rather a bad contact on the connectors I would think. Or a chip failure, be we won’t hope that!
PS: If you put the old SD card in, save a configuration! That avoids typos when screenshooting and re-entering settings.
.
been avoiding for days already
