Messages

5491

General Mach Discussion / Re: Manual Z up/down while code running on my gantry torch.

« on: July 30, 2011, 08:58:09 PM »

That trick may ONLY work with a LPT version of mach. I KNOW it works with the LPT. But I use it with a hardwired BUTTON to 2 inputs and a simple hand pendant. Many otheres have as well.

The galil may not handle the THC in the same manner depending on the plugin.

Please be VERY carefull with the wirless GAME controller it was never ment to be used in a machine control application. It does NOT have the proper built in safeguards that commercial wireless units have that were designed to be run in this enviroment(noise,com loss safety, 2 button safety interface,etc)

Just a thought, (;-) TP

5492

General Mach Discussion / Re: G31 Probe problem

« on: July 30, 2011, 08:22:55 PM »

HIYA DAVE,So when I do a Code"G31 X10" and the probe never stops when it hits the switch(led comes on) it is the programmer fault(;-). When I do a Code"G31 X10" and it does not make the move untill 3 OTHER commands have processed and THEN the G31 show up and is processed, THAT is the programmers fault?

I almost forgot my personal favorite. I a probe cycle with the proper wait states so the entire Cycle will work on this computer. Run it on the computer next to it and it fails by  jumping over sections of code. The wait state timing was off.

Yea I know semaphores. Dang Dave this is 2011 the Control program has to do something on its own like keeping track of its threads. (;-)

(;-)

I have 5 years worth of error and crash data that says otherwise. I have probably over a million (literally) probe cycles in gcode without failure.Can't say the same thing about the macro side.

BUT I am allways open to learn a new trick and I would be MORE than happy for you to show us the PROPER way to do the macro Probing so it NEVER fails.

NOW I will leave my soapbox,

 (;-)TP

5493

General Mach Discussion / Re: Circuit board isolation routing and probing

« on: July 30, 2011, 03:53:45 PM »

I am not a PCBer. I just help develope functions for other MACH users to use.(;-)

(;-)TP

5494

General Mach Discussion / Re: Circuit board isolation routing and probing

« on: July 30, 2011, 11:39:19 AM »

Sage I will keep this on my mind to see IF anything comes along that might be of help to yall. You never know when an idea might pop up.

One of thebig problems that alwys pop up is that MACH's monitor loop only updates at 10 cycles per sec MAX. That is not anywhere near fast enough to do anything constructive for live height comp.

Is there a Site where the Probing comp software is available for reveiw?

(;-) TP

5495

General Mach Discussion / Re: why does tool offset not stick?

« on: July 30, 2011, 12:56:10 AM »

Glad you got it slinging chips, GOOD JOB (;-) TP

5496

General Mach Discussion / Re: Circuit board isolation routing and probing

« on: July 30, 2011, 12:51:42 AM »

YOu could isolate the PCB board from the machine easy enough. AND you can easily probe before every Zdown.  BUT IF the height of the board changed from one end of your cut to the other you loose(;-).

But hey  Give it a whirl ya never know, (;-) TP

5497

General Mach Discussion / Re: G31 Probe problem

« on: July 30, 2011, 12:39:05 AM »

IT DOES use the same rate. That is why I mentioned running the G31 from inside a macro it is not always the same as running it from the Gcode side.

I have a box full of broken probe tips and 1 broken probe from running the G31 from  macros. NEVER have I broken one from using G31 on the Gcode side.

Try your move from the MDI line and see IF it stops as it should. From the Gcode side it will always obey the acel/deacel parameters of the called axis's.

Do a simple axis move at your probing rate of 60 see how far it takes to stop.

Then make the same axis move with a g31 and trip the switch THEN see how far it takes to stop from the same speed.

(;-) TP

5498

Video P*r*o*b*i*n*g / Re: Machcloud file extension question

« on: July 29, 2011, 09:38:51 PM »

The pointfile  is raw data it must be converted to a MESH with machcloud.  That will results in a STL file.  Next the STL has to read into a program that can convert it to a Soild then dxf or straight to Gcode.

Not every Cad can handle the STL format directly. DOn't know if your version of Acad can or not. (;-)

(;-) TP

5499

General Mach Discussion / Re: Circuit board isolation routing and probing

« on: July 29, 2011, 09:27:02 PM »

In plasma the THC is reading the arc voltage measured at the Powersource for the plasma. It then compoares that to the set point the machine is to follow. It then send s commands to teh THC up/down pins to have mach move the motor forward or backwards to keep the voltage in range. As the metal moves away from the torch the voltage goes UP so the THC tells the machine to move down UNTIL it sees the proper voltage again. The opposite for when the metal moves closer to the torch the voltage goes down an the THC tells the machine to move UP.

The THC up/down is not a real time compensated move.It is NOT even done with accell/deaccell values that control all other moves . BUT it also does not have defined moves the pulses just jolts the motor at full power so it moves at wide open speed. For a millisec. IF the top speed is set too fast it WILL miss steps and then mess up everything. It is also VERY easy for it to over run the setpoint and have to be corrected again.

The method to do this for the PCB would be to use a very sensitive linear encoder. that would hook to a circular ring that surounds the cutter bit very closely. The output from the encoder would have to hook to a device that reads the values and sends the THC up/down signal to MACH. BUT remember the controll is NOT a precision move so the quaility of the move would have to be controller from the Height controller. That precision controller setup would probaly cost more than your machine did WITH mach3 software (;-)

AND the swarf that the cutter puts OUT would effect the reading IF it got under the monitor ring that surrounds the cutter. Then at best you only get an AVERAGE height based on the relationship of the cutter to the ring size.

So yes it could be done to a point(;-)

(;-) TP

5500

General Mach Discussion / Re: why does tool offset not stick?

« on: July 29, 2011, 08:48:24 PM »

General rule of thumb, NEVER use tool0 for anything.

Start with a master guage and set all tools compared to it OR you can use one of the tools as a master then set evrything compared to that tool.

With  a knne mill I always use the LONGEST tool as the master. Set it as 0.000 and then compare all the rest of the tools to that. They will be + or minus from that tool. Then when you load the part and do the setup set the top of the material to 0.000 useing the master tool or guage.

THEN all your height will be corrected when you do the tool change BUT you must call the Tool offset into play with the G43 call IT is what actually calls for the COMP to take place based on the comp values you entered into the tool table. You also have to allow a move for the comp to take place before you get to the surface and begin to cut.

M6 T2       ' calls for the tool change and use T2

G43  Z1     " Does the actual comp based on the loaded t2 and comps itself on the way to Z1 for the difference in the 2 tools.

YOu  also have to have enough room for the machine to comp the move.  You can't be at the top end of Z and comp another 1" for a longer tool it will limit out.

Just a thought, (;-) TP