Machsupport Forum
Third party software and hardware support forums. => SmoothStepper USB => Topic started by: neptune on October 09, 2010, 05:40:22 AM
-
Hi
I recently changed to smooth stepper on my lathe. Everything seems to work fine except I cannot run anything from the MDI. Jogging works fine, running G Code from files works fine, but if I try to run a single command such as an axis move from MDI, the system locks up and I cannot jog or start spindle. all controls are dead. Pressing Estop then resetting clears the fault and everything is then back to normal, but if I try again to enter anything via MDI, the same thing happens.
Grateful if anyone has any ideas.
Neptune
-
I dont have a problem either on the lathe or mill, in fact I have just done a MDI on the lathe this morning to turn a 38 bar down to 32mm before running the code.
What version of Mach and SS plugin are you using? What are you trying to MDI?
If you attach your xml I can test with it here and see if I can get the same problem.
Hood
-
Hi Hood
Mach Vn. R3.042.035 SS USB Driver 2.08.02 SS Plugin v015ogx2.m3p
I am just really trying to commission the changeover to smooth stepper. I have run several part programs successfully, the problem only seems to be with the MDI.
What I am trying to do is take a cut to set my X datum. G1Z-20F50 neither the axis or the DRO move. If I then try to jog, nothing happens unless I press Estop and reset, then I can jog again normally.
XML attached
Thanks, Neptune
-
Cant test until I get home as the lathe is being used and wont be home until probably after midnight. In the mean time load the standard screenset just to make sure that is not the issue.
Hood
-
No worries.
The problem is the same with the standard screenset. Also the screenset currently in use works fine under PP control.
I'm glad I'm not the only one working late nights.
Thanks for your help
Neptune
-
Just got home, loaded your xml and had to change the active state of the E-Stop as I am just simulating with a smoothstepper hooked up. Pressed reset went to MDI and typed G0Z100 and it went there according to the DRO, Just to make sure the SS was outputting I hooked up the scope and typed G0Z0 and I get pulses out.
So safe to say your xml is not the problem.
Do you have a macropump, plugin (other than SS one) or any Brains running that could be affecting it?
Hood
-
I've seen a few problem XMLs that acted quite differently between a SS and LPT. Investigating them with an XML viewer showed no strange things with the the SS configuration but a few odd things on the Mach side. I could never figure out what those particular variables did though. Starting a new XML from scratch solved the problem. Since Hood did not have a problem with your XML it seems unlikely that it would be at fault but it would be easy enough to create a new one to test with.
-
Hi guys
No macropumps or brains. The only other plugins were video window and turn diagnostics which I have removed from the plugins folder. I have started a new profile from scratch but problem remained. I have also swapped out the computer with a spare, No change.
However I have moved forward with this. Firstly I discovered that M3, M4, M5 ans S word worked normally from the MDI input, it was only G code that wouldn't work. I changed the keyboard from a USB type to a PS2 but problem remained.
Then I discovered that if I had a G code program loaded, the MDI input would work in all respects. But I could not load a G code program after I had tried to input an MDI G code because I would get an alert every time I tried (See atachment).
To explain better, there are 2 scenarios:
1. Start up smooth stepper, try to input G0z20 into MDI, nothing happens, system is locked up. Press Estop and Reset, system is working normally except for MDI input. Try to load a part program, get SS alert as attachment.
2. Start up smooth stepper, load part program (any of several), everything is working normally including the MDI, no alerts.
This has solved my problem really, I don't understand why it is the case and whether it is just the way it works or if it is specific to my setup.
Anyway, thanks for your help and I will be running with SS from now, if there are any further developments, I will keep you posted.
Neptune
-
Its certainly not the way it works and I am unsure why you are seeing it. Thankfully you have found a work around but hopefully the true fix can be found.
Hood
-
My oft feeble old mind seems to remember an issue with MDI and Gcode loaded or not loaded but I can't remember exactly when/where it was. It might have been in the dev versions while testing with the MachStdMill screenset.
Would it be possible for you to install the latest lockdown version of Mach, 040, and try that? You could make a backup of your Mach3 folder beforehand and just replace it if the new version doesn't fix your problem and you really want 3.042.035 installed (don't try this folder swapping while running on PP, pp driver version problems!).
-
Now you talk about it I seem to recall that Daniel had an issue with MDI, If I recall it was ok if he jogged first but then again I think it was possibly only after a feedhold. Plugin update cured that so it wont be neptunes problem as he is using the latest one but I suppose it could still be related and needing looked at.
Hood
-
Thanks thosj,
It's a good point and worth a try. I will update this evening and post the results.
Neptune
-
Just to say, upgraded to version 3.042.040. The situation is the same as before.
Neptune
-
Hmmm......maybe time to look at what your steps per and velocity are in motor tuning and check the SS setup to be sure you're setup fast enough and not too fast.
Read thru Jeff Birt's SS setup doc here http://www.soigeneris.com/Document/Installing_and_Configuring_the_SmoothStepper.pdf
Read the last couple paragraphs on Page 9 and get your head around this. Check your motor tuning numbers, do the math, and be sure the SS setup matches. I'm not sure if something here can cause what you're seeing, but seeing as you're new to the SS, Jeff's setup doc is a must read anyway. It's impossible to know TOO MUCH about this stuff!!
Also, you stated you "started over" with a fresh XML. How did you do it? Clone the Mach3mill profile and re-enter all your setup info? That's the ONLY certain way to be starting fresh I know of. This exercise will give you cause to document your entire setup, too!!
An aside. I don't know how to do it, but someone who does should write a script or something to extract all the Mach3 settings, Ports & Pins, Motor Tuning, Homing & Limits, etc., to a text file or something. I do it with a combination of screen shots and Excel spreadsheet, but it's a pita amd every time you change something you have to remember to update your stuff.
-
I went through Jeffs set up guide before I installed the smooth stepper. I have experimented with changing the values in the SS setup page but then reset them to the calculated values.
I have all my XML settings documented. The new XML was cloned from the standard mach 3 Turn profile then edited with my settings.
The machine has been running today for around 10 hours on several part programs and everything else is running well.
Neptune
-
An aside. I don't know how to do it, but someone who does should write a script or something to extract all the Mach3 settings, Ports & Pins, Motor Tuning, Homing & Limits, etc., to a text file or something. I do it with a combination of screen shots and Excel spreadsheet, but it's a pita amd every time you change something you have to remember to update your stuff.
Saving the xml will do that as that is where the majority of the info is stored. You can open the xml in notepad and see all the settings but its hard to read as they are all one after the other. If you open the xml with Internet Explorer it is much easier to read but better still is Jasons xml reader which is linked to in a sticky on the general forum.
Hood
-
Now you talk about it I seem to recall that Daniel had an issue with MDI, If I recall it was ok if he jogged first but then again I think it was possibly only after a feedhold. Plugin update cured that so it wont be neptunes problem as he is using the latest one but I suppose it could still be related and needing looked at.
Hood
Hmm... was that me...? Not sure this is the issue I had, but then may be you just have better memory ;) What I do remember I had is that I was getting wrong moves made when commanded from the MDI. Another problem I had (I think it still exists) was after hitting softlimits while running a program or an MDI command, I was not able to jog that axis. Had to jog other axis to enable this one. The issue with feedhold was a another different problem.
Now I can say this - sometimes I enter a command in the MDI hit Enter and nothing happens. Look back at the screen "may be I missed the Enter key", but can see the command in the MDI history. Going up with the arrow and highlighting the command and hitting the Enter executes the command. Have it happening every now and then, but can't see what's causing it.
Dan
-
Probably not then ;D
It could have been the problem you were describing that I was thinking of or it could have been someone else.
Hood