Messages

3561

General Mach Discussion / Re: Plasma Consumable Tracking

« on: November 16, 2012, 03:23:58 PM »

The reason for stopping mid point is that when a tip starts going bad it can do so very fast from not bad to blowout in a wink. IF you stop soon enough most times you can save the cut. IF it is a 10cent item no problem but a 1 hour cut time piece gets expensive to replace 40 minutes into the cut.

The trick here is to KNOW what values you have to collect and WHEN to collect them. I'll help out. You will need to know .

Best to think it out then write down the order of events that HAVE to happen in your own words . Best to break it down to2 functions STOPPING and restarting.

Zpos
Ypos
line number.

(;-) TP

3562

VB and the development of wizards / Re: SystemWaitFor(INDEX) ...will it work?

« on: November 16, 2012, 03:11:38 PM »

YEP that is how that approach usually ends up. You have absolutely ZERO control over the process.

Try it this way lets NOT give the spindle time to get wound up. As soon as it sees the first pass it shuts off the spindle back off.  hopefully friction will be our friend at that speed.


'M2920 Macro for spindown Point
SetOemDro(817,20)       'set RPM
SetUserDRO(2001,0)   'Clear DRO to zero

RefCombination(32)
DoSpinCW()

Do While  GetOemLED(812)  
Loop


DoSpinStop()
Message"Ready For Tool Change"

End  

3563

General Mach Discussion / Re: Plasma Consumable Tracking

« on: November 16, 2012, 02:57:56 PM »

Glad to see you back Grasshopper(;-).

(;-) TP

3564

VB and the development of wizards / Re: SystemWaitFor(INDEX) ...will it work?

« on: November 16, 2012, 01:31:14 PM »

The brains will NOT be faster at detecting the signal than the last routine I used. That routine ran at kernal freq to detect the index signal. HERE I could not outrun it as it looks for the signal at 25,000 times per sec.

The brains will run fast interally BUT STILL have a 10hz loop to read and write the I/O.

SO on the last routine I posted what failed to happen ?

(;-) TP

3565

General Mach Discussion / Re: OEM Mach3 machine suppliers

« on: November 16, 2012, 10:16:58 AM »

The problem with MOST knee mill conversions is the very limited amount of Z travel. In this case you are limited to about 4 inches of Z.

(;-) TP

3566

Show"N"Tell ( What you have made with your CNC machine.) / Re: Isolation Routing PCB's and Local System Rotate.

« on: November 15, 2012, 05:08:09 PM »

Tweakie you can change the resolution of the dro with MachScreen. I have mine set to

0.0000 degs

(;-) TP

3567

VB and the development of wizards / Re: Script to pulse a pin when the Z axis hits 0.00

« on: November 15, 2012, 03:40:47 PM »

NO guaranties that it can see it during motion.

IF  GetOemDro(802) = 0 then
ActivateSignal(output1)
Sleep(10)
DeactvateSignal(output1)
end

3568

Mach Screens / Re: Axis hot keys don't work in new screen

« on: November 14, 2012, 08:34:29 PM »

Do you have the Jog on/off button placed on the screen ? Without it you cannot jog from that screen.

(;-) tp

3569

General Mach Discussion / Re: M4a & Mach3 startup ???'s

« on: November 14, 2012, 08:29:35 PM »

MIght want to look at home assignment again  I know them as Home1=X  Home2=Y   Home3 =Z

Just a thought, (;-) TP

3570

VB and the development of wizards / Re: SystemWaitFor(INDEX) ...will it work?

« on: November 14, 2012, 07:47:33 PM »

OK this works here as best I can simulate it. You need to activate the C axis then set Chome input the same port/pin as the spindle index input.

Place the code in a test button. AND give it a whirl.

'M2916 Macro for spindown Point
SetOemDro(817,20)       'set RPM
SetUserDRO(2001,0)   'Clear DRO to zero

DoSpinCW()
Sleep(2000)            'Adjust for stable RPM
RefCombination(32)

Do While  GetOemLED(812)  And GetUserDro(2001)<6
SetUserDro(2001,(GetUSerDro(2001)+1))
Sleep(1000)
If GetUSerDro(2001) >5 Then
DoSpinStop()
Message"Spindle Detect Timeout"
End
End If
Loop

Sleep(1000)             'Adjust for Spindown Stop point
DoSpinStop()
Message"Ready For Tool Change"

End 


(;-) TP