431
SmoothStepper USB / Re: SS DISCONNECT SAFETY CONCERNS
« on: December 09, 2008, 06:27:39 PM »
Hi,
Any sort of safety feature is a bonus and should be added if at all possible.
As an example, the ModIO I designed has a charge pump feature. As soon (configurable delay) as a Modbus master stops sending requests to the ModIO, the ModIO will disable the outputs.
To me this is just common sense.
I would expect that if you pulled out the USB cable of the Smoothstepper, all the outputs, including the spindle control would be disabled. It probably does this but I haven't checked.
It would also be useful for the Smoothstepper to have a chargepump output similar to the parallel port functionality (maybe it does). It would then retrofit well with breakoutboards that require such a signal. This chargepump signal would be removed if the SmoothStepper detected that Mach was not communicating with it, or if the SmoothStepper detected a fault with itself.
As an example of poor safety functionality, I was developing a motherboard for the ncPod. While testing the spindle control functionality, I accidentally pulled out the USB cable to the ncPod. The ncPod did not seem to detect the problem and continued to output the spindle PWM signal. The ncPod has sat on the shelf since that moment.
And in the end make sure you have a proper Emergency Stop circuit as gumbyrulesyou has stated. It make me shudder every time I see someone write that they have their EStop feeding into Mach3. The purpose of that input is not so that Mach3 can perform an EStop. It is there to politely notify Mach3 that an Estop has occurred and been handled by the appropriate Estop circuitry. After all the EStop buttons are sometimes hid because Mach3 is doing something wrong. In fact ArtSoft should probably replace the EStop input with something more appropriatly labelled, in both the software and manuals.
Cheers,
Peter.
Any sort of safety feature is a bonus and should be added if at all possible.
As an example, the ModIO I designed has a charge pump feature. As soon (configurable delay) as a Modbus master stops sending requests to the ModIO, the ModIO will disable the outputs.
To me this is just common sense.
I would expect that if you pulled out the USB cable of the Smoothstepper, all the outputs, including the spindle control would be disabled. It probably does this but I haven't checked.
It would also be useful for the Smoothstepper to have a chargepump output similar to the parallel port functionality (maybe it does). It would then retrofit well with breakoutboards that require such a signal. This chargepump signal would be removed if the SmoothStepper detected that Mach was not communicating with it, or if the SmoothStepper detected a fault with itself.
As an example of poor safety functionality, I was developing a motherboard for the ncPod. While testing the spindle control functionality, I accidentally pulled out the USB cable to the ncPod. The ncPod did not seem to detect the problem and continued to output the spindle PWM signal. The ncPod has sat on the shelf since that moment.
And in the end make sure you have a proper Emergency Stop circuit as gumbyrulesyou has stated. It make me shudder every time I see someone write that they have their EStop feeding into Mach3. The purpose of that input is not so that Mach3 can perform an EStop. It is there to politely notify Mach3 that an Estop has occurred and been handled by the appropriate Estop circuitry. After all the EStop buttons are sometimes hid because Mach3 is doing something wrong. In fact ArtSoft should probably replace the EStop input with something more appropriatly labelled, in both the software and manuals.
Cheers,
Peter.