Messages

731

General Mach Discussion / Re: UC300 (USB) to Mach3 erratic connection losses

« on: February 20, 2017, 02:17:27 AM »

Definitely a PC issue, if it is not maintaining USB connection.

Have a look in the device manager for USB bus and see if there are any power settings.

Also google something like "windows xx USB disconnects" and so on.

732

General Mach Discussion / Re: A dumb question

« on: February 20, 2017, 02:13:41 AM »

You can't jog while a program is running.

733

General Mach Discussion / Re: Workshop + Automation

« on: February 19, 2017, 03:47:03 PM »

How much automation?

I know of users that have built bar-feeders for lathes, step-and-repeat saws etc but no one that has a fully automated production line.

734

General Mach Discussion / Re: How many Mach3, Mach4 users?

« on: February 19, 2017, 03:45:11 PM »

I am sure there are more Mach3 users than pro system users, it was the only system that was available to small machine builders, home users, specialist developers etc. It has been adapted for many machines - mill, lathe, plasma, drag cutters, 3d printers and many more and has had new screens developed for it - how many pro systems can switch screens in seconds?

It has weaknesses, many of them, but i think it still stands up as an excellent system even in the face of offerings like linuxcnc which is gaining acceptance now.

Mach4 has a long way to go yet i feel.

735

General Mach Discussion / Re: UC300 (USB) to Mach3 erratic connection losses

« on: February 19, 2017, 03:37:40 PM »

If yu have just the UC300 and BOB connected does it disconnect then?

736

General Mach Discussion / Re: UC300 (USB) to Mach3 erratic connection losses

« on: February 19, 2017, 05:46:27 AM »

Thanks for the update , two drivers would certainly be a bad thing.

Hope the test goes well.

737

General Mach Discussion / Re: UC300 (USB) to Mach3 erratic connection losses

« on: February 19, 2017, 03:39:51 AM »

sounds like a possible ground loop somewhere.

I would first make sure (with a test meter) that the USB cable shield and therefore the UC100 is NOT connected to the machine ground at all, this should only be grounded by the PC - do this with all other wiring disconnected.

Now connect the UC to the BOB - the same condition must exist.

Now designate a point on your chassis as ground - this will be you star grounding point. The shields to the motors will connect here but NOT at the motor ends.

Connect the shields (if any) on the limits cables here too, but not at the switches.

connect the 5v supply to the BOB (power off), the USB shield must still be isolated.

At this point you have TWO systems of grounding - the control side (PC,USB,UC300) and the power side (BOB, MOTOR CONTROLLERS, MOTORS)

Imagine it as two circles - control and power, now each circle can be connected to supply ground and no problem as no loop is formed, but let the two circles touch (say by connecting the BOB to ground) and you now have a full loop and issues will arise

That should remove any ground loop effects, of course whether it makes a difference i dont know its how i wire my stuff

738

General Mach Discussion / Re: I've Done My Homework, but Can't get Relay to Fire Plasma Torch

« on: February 18, 2017, 01:19:01 PM »

No worries, glad to help.

The Proma is a good little unit, its limited to smaller, slower machines as it can't track really rapid height changes very well.

739

General Mach Discussion / Re: I've Done My Homework, but Can't get Relay to Fire Plasma Torch

« on: February 18, 2017, 11:39:06 AM »

no, you are using the proma - Mach has no knowledge of your voltage etc - ALL height control is done via the Proma, mach simply controls the motion in XYZ, nothing more.

you set the voltage on the proma but before you do that you need to know what voltage you desire.

this means test cuts - straight cuts about 150 - 200 mm long, set the height manually as per torch manufacturer specs using feeler gauges etc and then set mach to cut at the speed recommended or the speed you deem it will cut properly.

now you need to make a test cut and watch the voltage on the proma - it will jump about a bit but should settle long enough to get an average reading, say its 150v for example.

when the cut finishes, dial in 150v on the proma, connect the up/down signals etc so the proma is talking to mach, then when you make the next cut, the proma should try its hardest to move the torch height to maintain the set voltage +/- a small dead-band which i think is adjustable.

that is basically it, but DON'T FORGET, the voltage you have just set is ONLY correct for that thickness metal AND at that speed - change either one and you need to get a new voltage by the same methods, soon you will have a list of voltages, thicknesses and speeds and can simply dial in what ever metal you are cutting.

There are more complex THCs and these DO have the voltages on the mach screen etc but i think the cheapest one is going to be up in the £700-900 range

740

General Mach Discussion / Re: I've Done My Homework, but Can't get Relay to Fire Plasma Torch

« on: February 18, 2017, 03:50:19 AM »

The Proma setup is about as easy as it can be, you need to have the torch wired to the proma and displaying proper torch volts when working, do this first by triggering the torch manually. Then get the proma talking to mach3 - this needs three mach3 inputs, up, down, arc ok.

Make sure you have a fully licensed version of Mach3 or it will not work. Then get the proma into test mode - this outputs sequential up and down signals, the z axis must respond to these but to get this you might need to check the setup option of "allow thc inputs when not in thc mode" in ports and pins plasma settings.

once that is working, turn that option off or it will ignore the arc-ok signal.

IIRC that is all thats needed, BTW proma are or were very good on email support, broken english but good still.

The torch on/off relay is not connected to the proma and again this must be verified working before trying to use the proma, the torch must fire when you press the spindle on button on screen or issue an M3/M4 command and go off with an M5 command.