Getting the bugs out of my Smoothstepper setup

[LN-JET]

Typically using the mouse to change Mach screens, or entering Mach menus would make the Smoothstepper run out of data, also hitting the STOP button in Mach made the SS lock up. I am running a Fujitsu Siemens Amilo 1840 laptop, and have been afraid that it was running low on RAM.
Today I decided to try the "Mach standard mill" screen set. This required installing Mach3 V3.043.012.
The latest SS plugin and driver was also installed.
Now after the software upgrade I don't have the same problems anymore. I can access all the menus in Mach, and open other applications while the mill is running.
MSM will take some time to get used to, but there are some nice features, and the looks are a great improvement over the regular Mach interface.

Now there is one bug left; At startup I can not home the machine or run programs without moving one of the axis with the MPG first, and what ever axis the MPG is set to at startup I have to change to another axis to get it moving. If I do a "ref all" nothing happens before I have moved one axis a few steps with the MPG, then the homing sequence takes over, and after that everything runs as normal. Thoughts?

My router

Lars

[Big-tex]

I have tested smooth stepper and had problems as well. not same as yours but.....
Alot of problems you will have due to power setting options that laptops have but not desktop computers. I f you have another computer try it just to see if same problems are happening. That would give you good indication if its laptop related. Once you try that write your observations here and we get to the bottom of this. Remeber 2 heads are better that one.

[LN-JET]

Correction; the problem with the axis hanging on startup did also go away with the latest update. The only thing that will get the SS to stop now is if I try to zoom or rotate the toolpath screen in Mach.

I am running a stripped version of XP, and it actually shows 0% cpu activity if I run Mach minimized. The ordinary RUN screen takes 4-5%, and the large toolpath screen takes 10%. All power saving functions are turned off, and the USB ports have power all the time.

I will leave it as is now. But is there is a way to disable the use the mouse on the toolpath screen while running, so I don't do it inadvertently?

Big-tex; what problems did you see?

Lars

[Big-tex]

I had SS had up all the time, with xp pro not exeeding 20% on CPU.
This computer is strictly dedicated to control machine.

What I did, I bought cheap $20 parallel card and run on 2 ports and 2 breakout boards. Returned SS.

Now no problems she is making chips with out glitches.

[Fastest1]

I believe the MSM beta is only stable with Mach release .010

[LN-JET]

Originally Posted by Fastest1 I believe the MSM beta is only stable with Mach release .010

.012 runs stable, but they recommend .010 because of some safety issue that has shown up.

Lars

[Fastest1]

I thought a safety issue would mean unstable.

[LN-JET]

Ok, sorry. I was more thinking of unstable, as in suddenly stop running the machine. The bug seems to be recognised as a stable issue:-)

Lars

[najnielkp]

get rid of the ss. waste of money.go with 2 pports.i doubt that the ss will ever be out of beta.

[LN-JET]

Originally Posted by najnielkp get rid of the ss. waste of money.go with 2 pports.i doubt that the ss will ever be out of beta.

Thank you very much, but that would really be waste of money right now.
The SS is working to my intentions, beta or not, and I am running it from an old laptop, also to my intentions.

Lars

[ger21]

Greg posted some SS info on the Mach3 Yahoo group a few days ago.

Hi all, There have been so many postings on this topic I won't be able to individually reply to all of them. I will try to address everything in this posting. I purchased a USB analyzer to help identify the source of the communications problem. While using it I found a path in the software that would allow it to get into an infinite loop, but only if the data was corrupt. I instituted an integrity check and now the data is discarded if that happens. Data corruption isn't supposed to happen in the Bulk mode of USB. The communications dropout usually happens when something noisy happens in the system, leading me to believe it is related to FTDI's driver. I think the new plugin will help a lot of systems where noise is an issue. The latest plugin is not ready for prime time yet, but you can try it out if you are having trouble and hopefully you will not have any lockups due to noise. Here is a link: http://www.warp9td.com/files/SmoothStepper_v16bd.m3p The filtering for debounce in the SS isn't very complicated. At 33 MHz it cycles through 24 inputs, spending two clock cycles on each input. If an input is asserted, it counts up by one until it reaches the debounce threshold and sets the internal input value to '1'. If it is de-asserted it counts down by one until at zero, at which time the internal input value is set to '0'. This behavior kind of mimics the charging and discharging of a capacitor. As for ground loops, I seriously doubt the SS has any internal ground loop problems. I agree that PCBs can have ground loops on the board, but the SmoothStepper PCB is a 4-layer board with solid ground and power planes. Planes have very low inductance, ensuring low impedance access to ground anywhere on the board. Any component that needs to connect to ground has less than 10 mils of distance before it reaches the ground plane. Ground loops of the type we're concerned with are formed over greater distances with impedances between the two grounds. As Henrik has pointed out, mounting the SS inside of the PC case with a short USB cable is very effective at keeping the ground of the SS and the ground of the PC at the same potential. A number of people have done this and it works very well. Even if it is not inside the case, a 6-inch USB cable works well. Wolfram has done an excellent job of designing the SmoothStepper Pro. As far as I know, he never has any reports of communications problems. In his design he decouples every input and output with ferrites, capacitors, and resistors. I would recommend his product to anyone, especially those that are having trouble with my SmoothStepper. Hood and Jeff Birt did a lot of testing on their systems, trying to figure out where the noise was coming in. In Jeff's case, he found the noise from his spindle motor was coming in on the cable connected to the 26-pin header of the SS. Shielding that cable fixed the problem. He was also able to make the problem go away by using the new plugin (without shielding the cable). Hood also reported success with the new plugin, but a startup condition is faulting his drives, and that is one reason why I say the plugin is not ready yet. I am thinking the noise raised or lowered the voltage of the ground of the SS, which caused communication problems since the ground of the PC was at a different potential. USB is not a purely differential signaling standard. There are parts of the protocol that are single-ended, and I suspect that might explain the problems. Many people have found success by connecting a heavy duty ground wire between the SS and the computer. Thinking about the grounding arrangement from a "star ground" point of view, where would you say the center of the star is with a SmoothStepper installation? Assuming the USB cable is not zero impedance, it might be somewhere in the middle of the cable. I think it is best to maintain a low impedance connection between the SS and the PC. That makes the center of the star less ambiguous. It would be really cool if we could put on special glasses that would allow us to watch the flow of current. I'm sure it would be flowing in places you wouldn't expect. One thing is for sure, it will follow the path of least impedance. I know I haven't been producing new plugins for the SmoothStepper often enough. I'm slowly un-burying myself and working towards a release. I want to get all of the promised features finished so that I can move on to future products. An Ethernet SmoothStepper won't be far away, and I promise that it will not lose communications like the USB version does. You will be able to light a torch next to it and it won't skip a beat. I will also make sure it has enough resources so that I will not be constrained like I am now. More updates soon, since I have been working on the plugin lately. Thanks, Greg