Machsupport Forum
Third party software and hardware support forums. => NC Pod => Topic started by: Greolt on January 18, 2007, 12:06:11 AM
-
I am building a router that has R&P drive on each side of the X axis.
Although the Y and Z axis are not done the slaving in Mach through LPT has tested well on the completed X
So as Art has released a plugin for the Pod that has slaving I thought I would give it a go :)
One side of the drive is designated X and the other side A. Slaving is selected in Mach X to A
Motor tuning is set the same to both drives. Try to jog. No go. Just acts like it is stalling. (turns slowly, makes a lot of noise)
Tried all sorts of velocity and accelleration settings. Nothing works.
Deselect slaving and X jogs perfectly on its own.
What am I doing wrong. Something stupid I guess. ;D
-
Have you got the 2 motors running in the same direction?
Are they mounted mirror style or in parallel?
If mirrored they need to run in opposite directions.
Graham.
-
Motors are set to run in the correct direction. They are not fighting one another.
Being R&P I can simply release the spring that holds the pinion against the rack untill rotation direction is set correct.
Incidently I could not simply toggle "direction low active" to reverse motor direction as you can when using LPT.
Had to physically reverse two motor wires.
-
Can you swap your motor wires at the drives? Make x=a and a=x. This might help narrow it down. Before you do that, have you tried the a axis with the x axis disabled?
Brett
-
Brett
When X and A is slaved together no go. When slaving disabled both axis jog perfectly independantly.
Of course I have disengaged one pinion.
Wire it back up to LPT and slaving works as it should.
Fairly certain it is not a mechanical, driver or motor problem. Just something to do with slaving with the Pod.
Thanks, Greg
-
Of course I have disengaged one pinion.
Wire it back up to LPT and slaving works as it should.
Are you saying all is well with both engaged now?
Brett
-
Sorry I think you misunderstood Brett. I have been trying to get slaving going using the Pod.
LPT works but I only mentioned that to demonstrate that I don't believe it is a mechanical problem.
It is slaving with the Pod that I am posting about.
-
Your right, I did misunderstand. Sorry about that. Yes, I doubt it is in your setup.
Brett
-
Greolt,
Sounds like there might be a problem with the slaving function. Do me a favour, can you disengage the A axis motor and try to slave X and Y together. If this works, disengage your X axis Motor and re-engage your A axis and slave Y and A together. Let us know the outcome.
On the Motor reversal issue, the place to do that for the POD is in your Homing/Limits in the config not in Ports and Pins. In the table in this section under Home/Limits, the first column will allow you to reverse the motor direction, this works, I had to do it on my machine.
Hope to hear the results soon.
Regards
Dave
-
Dave
Yes that was the right place to reverse motor direction. Had not noticed that before. :D
As I said in the first post this half built machine up to now only has two motors, both driving the X from both sides.
However in response to your request I tried those two motors in every combination I could by
plugging them into the Pod as X, Y, Z, A, B. and C
Every time slaving would not work and with slaving deselected each motor would jog perfectly as an individual.
Could it be a noise issue? Wiring is physically separated but not shielded.
As signal should be identical when slaved it would not be a problem. Wouldn't it. ???
I spose if slaving is working for everyone else then something like that may explain it.
-
greolt,
I will try slaving my axes and see what I get. I am just about to go into a meeting so it may be a little while before I get to it. Best for me to try first before you go and re wire you machine in the hope of reducing any noise issue that may not be there.
Regards
Dave
-
Yeah no worries Dave.
Please be aware I am not a user desperatly seeking support to get his machine going.
Just someone who is interested in the advent of the ncPod and similar devices.
It is quite possible that my input simply "muddies the waters" and would be better to
leave this type of posting to more "expert" users.
Thanks, Greg
-
I was wondering if any beta users out there are having success with the slaving function.
Not sure whether I am just doing something wrong or if others are having the same issues.
-
I'll go try to set up a slave now. I'll report back.
-
I just slaved my A axis to my X and everything worked. I didn't do any perfomance test but the axis moved together.
-
Thanks for letting us know Ryan.
Guys, I have to go away for a few days, I will try to check in while I am away, but if I seem a bit quiet, thats why. I will be back next Wednesday.
Take Care
Dave
-
OK thanks for that Ryan.
I must be doing something wrong, however I am working on my Y and Z axis now so can't play with
the Pod for the moment. When I get that done I will be asking more questions. ;D
-
Good luck with the retro Greolt, I bet you are looking forward to seeing all the Axes finished and moving well.
Regards
Dave
-
Sent you a PM dave :)
-
Got it
Dave
-
Got my Y and Z axis done so now I am back to trying the Pod. Really want this to work now. ;D
Latest version of Mach .041, Plugin .038 and Pod Firmware 2014
First thing is slaving is now working like a dream. YAY!!!!
Everything else is still the same so the fix must have come about through software updates.
One thing that has come up and only happens when on the "Tool Path" screen.
The out put starts to stutter. Change to any other screen and it smoothes right out again.
Any ideas on this one?
-
It happens because the toolpath graphics bogs down the processor. I had the exact same problem. I downloaded the Mach optimization file and rechecked everything on the list. I also went into my BIOS and allocated more memory for my video card. This helped allot. DO NOT ROTATE the toolpath while cutting. Art was going to lock the toolpath window from rotation while cutting. Also stay away from rapidly changing screens while running. I also found that jog follow mode magnified the problem.