Messages

351

General Mach Discussion / Re: G31 causes an endless loop

« on: October 31, 2014, 06:27:08 AM »

Everything works fine here with your xml on my R3.042.020.

Best I can suggest is you try a re-install of Mach3 and maybe use a different/earlier version. I believe Hood is unhappy with 0.66 for all sorts of reasons - personally I've never used it so can't comment.

352

General Mach Discussion / Re: G31 causes an endless loop

« on: October 30, 2014, 02:28:47 PM »

please post your xml file. That's the file in C:\Mach3 with the same name as your profile with a .xml extension. Make a copy and rename it to Ptd.xml and post it using the forum's full-reply Additional options link.

353

General Mach Discussion / Re: motor settings

« on: October 30, 2014, 01:54:06 PM »

Are you saying that this could not be a Mach3 software problem, that it has to be my electronics?

No I'm not saying either of those.

I can only suggest things based on what you say and when you say it. You have the machine in front of you - I don't so I can only go on what you tell me and when.

Your motors ARE a poor match. However if you say 2 dozen other people have exactly the same system and theirs work fine then despite the motor's shortcomings it may well be that all other things being equal, they are up to the job (though I still suspect it's only just).

Have you set your microsteps as I suggested? Do that first because 16 is pointless anyway so you might as well start with that.

Then I'd suggest you try the following - one by one:

1) find some toolpath that reliably exhibits your problem in air - a few rapids should do it.

2) lower your accel and max velocity by half and repeat. Does it still happen?

3) Because you've just mentioned jogging is ok, try turning your toolpath display off and see if things improve when you run a toolpath that previously stalls.

354

Show"N"Tell ( Your Machines) / Re: My Build EVO v1.I

« on: October 30, 2014, 10:28:01 AM »

Hi LGF. My condolences to you on the passing of your Father.

Can I ask you to re-read this thread and take stock of where you are and where you want to be? We were dealing with homing and circle wizards but now you've jumped onto your spindle control and now probing. Maybe slow down a tad and do one thing at a time before moving on to the next.

355

General Mach Discussion / Re: G31 causes an endless loop

« on: October 30, 2014, 09:52:39 AM »

I think what we have here is a classic case of the code we see is not the code in question - the digitize wizard would not produce that code - but a bad memory and a quick hand might.

356

General Mach Discussion / Re: motor settings

« on: October 30, 2014, 08:19:39 AM »

Well - maybe so but why would motors that seem fine on a "small" machine lead you to think they'd be just as good on a different machine?

The place I got my machine from and about 2 dozen people that own the same machine and package, say that the electronics package I have works fine with their bigger machines.

Well there's a contradiction here then. If they say the same package works fine it must be that yours has a problem that theirs doesn't.

If you have any recommendations for what I can save from my electronics and what I need to change to that would be great.

See the contradiction?

Have you tried what I suggested?

357

VB and the development of wizards / Re: How to stop gcode("") by activation of signal?

« on: October 30, 2014, 06:33:37 AM »

Cheers Russ. I remember a thread a ways back that started very similar to this one. He asked how to stop a limit switch taking Mach into reset. Turned out after a long and frustrating thread the guy was trying to rewrite limits to work like a probe because he didn't realize that probe existed. Just trying to avoid that here if it's similar.

Ian

358

General Mach Discussion / Re: Step Active Low works, board specifies Active High

« on: October 30, 2014, 06:15:56 AM »

Easy way to find out. Set an output pin to the same pin as one of your step pulses is on and then with your hand on the motor, execute a few activateSignal(OUTPUT?), deactivateSignal(OUTPUT?) commands in the script editor. You'll feel which one causes the motor to step.

359

General Mach Discussion / Re: motor settings

« on: October 30, 2014, 06:00:56 AM »

Your X motor is doing just over 71 rpm at 250 in/min which is very slow and should be no problem at all. It may be that they're just underpowered for the job and running at their limit or perhaps you've developed some binding somewhere.

I guess this is a dumb question but if the motors are a bad match for the drivers and the PS is less than half of whats needed why would Keling Inc package them as as ready to go kit.

You'd have to ask THEM that.

What Drivers would be good for the motors I have? And I'm sure I can find an 84v PS.

It's hard to say without knowing the full details of your machine. It's possible that changing the motors - not the drivers and supply would improve things. As I said, these motors are 6.8mH Inductance which is very high and not really suited to the purpose.

First thing I'd try is check for any binding. Second I'd drop the microsteps to as near 10 as you can (probably 8 ) and of course half your steps/per to match.

Although this package worked OK on my small 2" x 4' machine for 2 yrs. No stalling of any kind.

Well - maybe so but why would motors that seem fine on a "small" machine lead you to think they'd be just as good on a different machine?

EDIT: changed 8 followed by a ) to 8 followed by a space followed by a ) to get rid of the darn smiley

360

VB and the development of wizards / Re: How to stop gcode("") by activation of signal?

« on: October 29, 2014, 12:53:21 PM »

I'm guessing this is a classic case of the XY problem. Can you describe what it is you want to do rather than how you think you might do it?