Messages

1

Mach4 General Discussion / Re: Mach 4 Bug Reports

« on: June 05, 2015, 08:27:52 AM »

I'm running build 2472 and am unable to get limit sensors in Mach4 to work with an ESS and C25 BOB.  The issue is that Mach4 and the ESS conflict in their reading of the switches state and if I get them to agree, I still have no motion. 

I have 2 active low limit switches that I am connecting to my X axis as X-- and X++ limits.  I have added them to Port 2, pins 2 and 3 and selected Active Low in the ESS.  Port 2, Pins 2-9 are set as inputs in the ESS (and that is the only supported config of the C25 on port 2).  I have confirmed by measuring the voltage at the BOB that the inputs are 5V until tripped and then they are ~100mV.  When in the ESS diagnostics the limit switch inputs are unchecked until they are tripped (as they should be).  However in the Mach diagnostics (default screen), the two limit switches are lit up as though they are tripped and go out when the limits are actually tripped (opposite what is expected).  Although Warp9 specifically says NOT to set the active low in Mach4, I have even tried that.  Even though the display in the Mach4 diagnostics are now correct at that point the machine doesn't move when jogging.  When the active low setting is off in Mach and Mach shows the limit switches tripped, no axis move and the X axis reports that you can's move towards a limit.  I have a solid green light (and no red) on the ESS as I did before adding the limit sensors.

If it helps, the first line in my history shows "ESS: Limit hit" and when jogging away or another axis the Machine State shows "Jogging", but the DRO's don't change and the machine doesn't move.  The diagnostic logging shows: "2015-05-31 23:00:43.168 - API: mcJogIncStart() called. Axis 0, inc = -1.000000" for each jog, but no other information.  After every configuration change I have exited Mach and restarted it.   

I have tried connecting just one, or using the 5V source on the C25 and every other permutation I can think of with the same results.

Has any one else experienced this or have any suggestions? Hopefully I'm just missing something?

I did see a Youtube video by DaztheGaz where he has limits connected to his ESS and they appear to be working.

Thanks!

I tried changing the input pins on the C25/ESS from Port 2, pins 2 and 3 to pins 10 and 11 and it works.  My guess is there is an issue because these pins could be inputs or outputs.

2

Mach4 General Discussion / Re: Mach 4 Bug Reports

« on: May 31, 2015, 11:19:07 PM »

I'm running build 2472 and am unable to get limit sensors in Mach4 to work with an ESS and C25 BOB.  The issue is that Mach4 and the ESS conflict in their reading of the switches state and if I get them to agree, I still have no motion.  

I have 2 active low limit switches that I am connecting to my X axis as X-- and X++ limits.  I have added them to Port 2, pins 2 and 3 and selected Active Low in the ESS.  Port 2, Pins 2-9 are set as inputs in the ESS (and that is the only supported config of the C25 on port 2).  I have confirmed by measuring the voltage at the BOB that the inputs are 5V until tripped and then they are ~100mV.  When in the ESS diagnostics the limit switch inputs are unchecked until they are tripped (as they should be).  However in the Mach diagnostics (default screen), the two limit switches are lit up as though they are tripped and go out when the limits are actually tripped (opposite what is expected).  Although Warp9 specifically says NOT to set the active low in Mach4, I have even tried that.  Even though the display in the Mach4 diagnostics are now correct at that point the machine doesn't move when jogging.  When the active low setting is off in Mach and Mach shows the limit switches tripped, no axis move and the X axis reports that you can's move towards a limit.  I have a solid green light (and no red) on the ESS as I did before adding the limit sensors.

If it helps, the first line in my history shows "ESS: Limit hit" and when jogging away or another axis the Machine State shows "Jogging", but the DRO's don't change and the machine doesn't move.  The diagnostic logging shows: "2015-05-31 23:00:43.168 - API: mcJogIncStart() called. Axis 0, inc = -1.000000" for each jog, but no other information.  After every configuration change I have exited Mach and restarted it.    

I have tried connecting just one, or using the 5V source on the C25 and every other permutation I can think of with the same results.

Has any one else experienced this or have any suggestions? Hopefully I'm just missing something?

I did see a Youtube video by DaztheGaz where he has limits connected to his ESS and they appear to be working.

Thanks!

3

Mach4 General Discussion / Re: Mach 4 Feature Request

« on: May 28, 2015, 10:48:06 AM »

I have 3 suggestions:

1) A lot of motor drives include fault indication.  Have default fault input available for each motor.  While this could be done by the user adding some code, including this feature would make it much easier for a hobbyist to just "plug and play".  (I know that these signals could be added to the EStop input, but then you don't know what Motor/Axis has the issue).  Alternatively multiple EStop inputs with the ability to "label" them so that Mach can report which EStop was triggered.

2) Digitally sign your program (as you are doing with the plugins) so that Windows reports the publisher as ArtSoft or Newfangled.

3) Display some message when the demo stops working so that we know whether it has timed out or there is another issue that needs troubleshooting.

Thanks!