Guest
Show Posts
1
CS-Lab / Re: New CS Lab plugin 3.122 released
« on: July 01, 2019, 12:17:25 AM »
Hi Fledermaus,
I am retrofitting an old VMC with a CSMIO/IP-S and simDrive motion gear. I was nearing the end and had nearly finished configuring Mach4 and testing the machine when I came across an issue with the MDI input becoming non-responsive. I wasn't sure if that would also cause issues with G-code execution.
I saw that there was an update available so I updated the plugin and the module firmware to see if that would fix the issue. The update does seem to have fixed the intermittent MDI issue but now I cannot control the spindle speed. When I activate the spindle using either the button in Mach4 or a direct M03 S1000 command in either MDI or G-code, the CSMIO/IP-S analogue outputs stay at zero volts.
I have tried setting both analog-0 and analog-1 as spindle output in the csmio plugin config panel but both are non-responsive. I have verified that the outputs are not physically damaged using another computer running the old plugin and firmware.
Have you experienced anything similar since upgrading to newer firmware? Have I missed a config option somewhere?
Cheers,
Josh
I am retrofitting an old VMC with a CSMIO/IP-S and simDrive motion gear. I was nearing the end and had nearly finished configuring Mach4 and testing the machine when I came across an issue with the MDI input becoming non-responsive. I wasn't sure if that would also cause issues with G-code execution.
I saw that there was an update available so I updated the plugin and the module firmware to see if that would fix the issue. The update does seem to have fixed the intermittent MDI issue but now I cannot control the spindle speed. When I activate the spindle using either the button in Mach4 or a direct M03 S1000 command in either MDI or G-code, the CSMIO/IP-S analogue outputs stay at zero volts.
I have tried setting both analog-0 and analog-1 as spindle output in the csmio plugin config panel but both are non-responsive. I have verified that the outputs are not physically damaged using another computer running the old plugin and firmware.
Have you experienced anything similar since upgrading to newer firmware? Have I missed a config option somewhere?
Cheers,
Josh