Machsupport Forum
Third party software and hardware support forums. => dspMC/IP Motion Controller => Topic started by: pofo on August 11, 2015, 10:17:11 PM
-
Something has changed on my mill. I boot up Mach3 and the DSPMC. I can move the table with my pendant. If I try to enter a G01 x1, I get an error 'Estop button pressed'. This message continues to be reposted continously. There are no other messages in the log.
I don't have an estop button. There is an estop button assigned in the inputs (port 1 pin 10). Its always been that way and has worked fine. I cannot disable that assignment. If I do, when I check it again, it is enabled.
The diagnostics screen does not indicate an estop is present.
Only a reset of the DSPMC clears the problem.
Ideas?
-
Hello,
What Mach3 plugin and firmware version are you running? You can view this in the status window.
Perhaps the polarity of your EStop signal is incorrect?
-Marc
Vital System Inc.
-
Changing polarity on the estop signal makes the axis go drifting off and I am not able to reset.
Plugin 4.0.17
-
I reloaded the DSPMC firmware and FPGA load. That fixed it.
-
The problem persists.
I reprogram the Flash with 8.24. It loads successfully and I reboot it.
I start Mach 3
I test that I can move the x axis with a shuttle
I test that I can use a G0 or G01 command
I execute a G31 command without the probe being detected. All is well to this point
I execute a G31 command and detect the probe. An emergency stop occurs and Mach 3 posts the message 'ERROR: Following error limit exceeded on Axis 0. Servo disarmed'
I hit the reset button.
I make a shuttle move ok
A G0 or G01 command results in emergency stop and the error message 'E stop button pressed'.
Hitting the reset button and trying again gives the same results.
I turn the DSPMC off and back on. This does not clear the problem. A g0 or G01 results in the error message 'E stop button pressed'. I have to reload the firmware.
The G31 causes the problem and reloading the firmware clears it.
Nothing was changed before the problem started.
-
Hello,
In this step of your test:
I execute a G31 command and detect the probe. An emergency stop occurs and Mach 3 posts the message 'ERROR: Following error limit exceeded on Axis 0. Servo disarmed'
I hit the reset button.
Maybe your digitize signal and EStop signal are mapped to the same input? Does this behavior only happen with G31?
Also, what other plugins do you have loaded?
-Marc
Vital System Inc.
-
That did occur to me last night. But the diagnostics page shows the probe flashes the Digitze LED and it does not trip an Estop when activated. But even if they were, that does not explain this sequence:
After G31 error, reset DSPMC, restart Mach 3, and hit the Mach 3 Reset button. All is ok. Mach 3 Reset button stays green. The probe going active does not cause an Estop. Only after a G00 or G01 does the Estop trip, and the Reset button flashes. I cannot reset Mach3 until I reboot Mach3. The Estops messages are continuous. The Diagnostics screen does not show the Estop button active.
I cannot get G00 or G01 to work until I reprogram the firmware.
The only plugin I'm using is for the Russian pendant, ShuttleRu (Andrey67 on CNCZone).
-
Hello,
Ok, so I ran the test using the files on the web and I did see the same thing during probing. So I tried the test with some newer files and the probing worked fine. Also tried some other test GCodes just to make sure that these versions worked fine.
Send an email to support@vitalsystem.com and I'll reply with these newer files so you can test them and see if the problem goes away. We typically don't update the Mach3 files on the web (especially the firmware) since we're not 100% sure that all the newer features that we're adding for Mach4 will play nice as far as Mach3 compatibility goes. But if it works out well for you, we can consider uploading them.
-Marc
Vital System Inc.
-
I tried it and it solved the G31 problem. My edge detection buttons are working again. I ran a circle pocket program and that also worked. It looks ok.
Thanks.
-
I too am getting this error when using my probing scripts. I have tried dspmc firmware versions 8.24 8.37 9.01 and they all are giving me the axis error and the estop error.
What did you do to fix this?
-
I used the firmware that Vital Systems sent me. I don't have the firmware number handy. But I suspect if you download the latest firmware, you will get the fix.
-
9.01 is the latest firmware. Can you post a probe macro then I could see if its something with my macro file.
-
Message("Edge X Axis")
Code "G31 x100 F5"
sleep 100
While IsMoving()
Wend
SetOEMDRO (800,0)
Sleep 300
Code"G01 X-.03 f1 "
sleep 1000
Code "g31 x100 f1"
While IsMoving()
Wend
SetOEMDRO (800,-.196)
-
Thanks Pofo for the code. I have tested it and as soon as the probe is contacted I get "Following error limit exceeded on Axis0 SERVO D". This is doing the same as my probe scripts. Maybe Vital Systems gave you a different firmware.
I updated from firmware 6.45 to 9.01 to do rigid tapping only to find out that tapping was removed from 9.01 to add features for Mach4. Now my probe doesn't work. Probably going to contact Vital Systems and see if they can get the files to get back to 6.45
-
Hello,
What plugin, firmware, and FPGA version are you using?
Here are some thoughts to get the issue fixed.
- Download the latest Firmware from this link: http://www.vitalsystem.com/portal/motion/dspmc/DSPMC_StepGen.zip
- Check if your firmware version is the latest.
- Check if your FPGA is the latest (because firmware version 6.45 is quite old)
- Check if your Mach3 plugin is the latest.
The firmware and FPGA version can be verified from the VSI Device Manager application, while the current plugin version can be verified from the DSPMC Status Window. Also, we used to get issues when people would copy the plugin file into the "C:\Mach3" folder, and not the "C:\Mach3\plugins" folder, you may want to take a look at that as well.
Also, there are some useful details that were indicated in the earlier posts of this thread, such as if your digitize and estop signals were mapped to the same digital input.
Although this may be negligible, there is an off-chance that this could be caused by the firmware config that we had added to our motion controllers sometime in the middle of last year. Upgrading a very old firmware to the very latest one may produce "unpredictable" effects as far as the on-board configuration goes. This, of course, shouldn't be a cause for concern if the gap in the firmware versions isn't so large. See page 10 of this user manual:
http://www.vitalsystem.com/portal/motion/VSI_Device_Manager_Manual.pdf
What you want to do is look over the "Firmware pins" in the firmware configuration and make sure that each setting is set to "-1" with an unchecked active low. Then click the "Download" button if you make any changes.
Hope this helps, and if you still see issues, let me know what plugin, firmware, and FPGA version you're using.
-Marc
Vital System Inc.