For Those that cannot see the wood for the trees
http://warp9td.com/downloads.htmAt the top of the page is the driver
Scroll down for the plugin
2009-11-07 PlugIn: SmoothStepper_Beta2_v015ogx2.m3p- There was a problem with the version of "include files" that I was using when I compiled the plugin. Brian has sent the latest version and I recompiled the plugin. Version "ogx" has been replaced with version "ogx2".
- FRO can now be made to go as high as Mach allows, since Mach is in control of it now.
- There was a problem with an asymmetry between CW and CCW when jogging. The asymmetry was evident at very low step rates. This is fixed now.
- The debounce filter has been improved. Now its behavior mimics a low-pass filter.
- Offline mode has been added. It saves the machine coordinates before entering Offline mode and restores them upon exiting.
- The Homing routine has changed significantly. The old routine reset the machine coordinates as it progressed through the state machine. It shouldn't do that if the homing routine is also to be used for the Verify command. Verify will perform a home operation, but in the end it will not change the machine coordinates. As long as your homing is repeatable, the Verify routine will let you know if you have lost any steps. If you have no backlash and you're not losing electrical pulses, when the machine comes back to machine zero, it should read zero. I added a feature to limit the amount of distance the machine will travel when searching for a home switch. This feature was mostly for when a slaved axis is de-slaved from its master. You can specify a short distance so that the gantry does not get twisted up. Unfortunately, I don't think the homing routine is working perfectly well yet. The problem is in syncing with Mach. As soon as the axes are de-slaved, there is a tiny adjustment that is made and it should not move at all. I need to dig into this to figure out why this is happening. I have not tested the Verify function, though the code is in the homing routine now. It should work, but it has not been tested. I need to get a new release out, so this is something I can fix for next time, if it needs fixing.
- The ESC key used to cause great pain in the last plugin. It is handled properly now. It does the same thing that Stop does, except for stopping the spindle. Please note that Stop is an abrupt stop, just like EStop.
- There was a bug in limits, where the EStop would not occur in the device. Instead the data was being relayed from the device, to Mach, and then back to the device. This took too long and if the machine was moving rapidly it would overtravel. Now it is trapped in the device and it stops in an instant (or a bit later if you are running it through the debounce filter).
- If you hit a limit switch, you should be able to back off of the limit now.
- There was a bug in the spindle acceleration. It was 8 times too fast, so if you got your spindle working just right you are going to need to tune it again. Sorry about that, but the acceleration is right now.
- If a G28.1 was performed as part of a gcode program, there was a bug in the homing routine that would not permit the program to continue after it had executed the G28.1. That has been fixed.
- There is an option now for de-referencing the axes if an EStop occurs. By default that is turned off, so that it will be the same as it has been. But if you want the axes to be de-referenced, you can check off that box in the SmoothStepper's config and it will do that when you EStop.