Messages

6481

General Mach Discussion / Re: VB or Brains Question

« on: August 13, 2010, 12:27:45 PM »

(;-) A little more testing shows we can combine a few things and make it better.

The mcode process (m2001) allows the positional date to process first( g0 x1 y1) then the Mcode runs such as

M2001 X1.000 Y1.000 P-1.000 Q.010 R.500 F20  S1000    (moves to the drill point FIRST then preceeds with the drill cycle)
M2001 X2.000 Y2.000 P-1.500 Q.010 R1.000 F5  S500

This simplifies the Gcode program a bit and still allows a self contained Drill cycle WITH lock and unlock as you need.

6482

General Mach Discussion / Re: VB or Brains Question

« on: August 13, 2010, 12:09:15 PM »

NOW another way is to use a Mcode to do the entire drill cycle including the lock unlock as one cycle. In this function we use 3 param calls from the macro to set things such as Zdepth Ztop and Retract height and Feedrate. In the example we use P= Zdepth Q= Ztop R= retract height and F=feedrate

THis IS a little simplier as you do NOT have to cancel the cycle before you move to the next location BUT you will have to modify the Cam post to use the Mcode in lou of the G81cycle


G0 X1.000 Y1.000
M2001 P-1.000 Q0.010 R.555 F5
G0 X2.000 Y2.000
M2001 P-1.100 Q0.010 R.555 F10
G0 X0.000 Y0.000


The Mcode code is this:

'M2001 , macro for G81 drill cycle
ActivateSignal(output3)
Sleep(1000)
Code"G0 Z" & (param2)
While Ismoving()
Sleep(10)
Wend
Code"G1 Z" & (param1)
While Ismoving
Sleep(10)
Wend
Code"G0 Z" & (Param3)
While Ismoving
Sleep(10)
Wend
DeactivateSignal(output3)
Sleep(1000)
End    

6483

General Mach Discussion / Re: VB or Brains Question

« on: August 13, 2010, 10:57:33 AM »

OK the easy way (programmer,operator and machine) is to use Gcode and Mcodes that way it is easy to CAM the project and let the post write all the code.

G0 X1 Y1 (move to drill point)
M1001 (Lock Bed)
G81 X1.000 Y1.000  Z-1.000 R.5 F5  (drill Cycle)
G80 (cancell cycle)
M1002 (Unlock Bed)
G0 X2.000 Y2.000 (move to new drill point)
M1001 (Lock Bed)
G81 X2.000 Y2.000 Z-1.000 F5 (drill cycle )
G80 ( cancell cycle)
M1002 (Unlock Bed)
G0 X3.000 Y3.000 ( Move to new drill point)
M1001 (Lock Bed)
G81 X3.000 Y3.000 Z-1.000 F5 (drill cycle)
G80 Cancell cycle)
M1002 (Unlock Bed)
G0 X0.000 Y0.000  Move to new drill cycle )
etc
etc
etc

The mcodes code would look like this

'M1001 , Macro to lock bed
Activate(output3)


'M1002 , Macro to unlock bed
Deactivate(output3)

Output 3 would be wired to the bed lock controller


DOES that suite your needs or do you require something more. From here on out it gets more complicated for the Programmer/operator/machine

6484

General Mach Discussion / Re: VB or Brains Question

« on: August 12, 2010, 09:24:47 PM »

What you would have to do is program a macro that does an actual drill cycle LIKE the G81 but it would include a clamp/unclamp function as part of the routine. You woul d also have to use Variables to be able to preset your hole locations. Then you could call the macro with Vars and have what you want .

You can also do the same thing using Gcode SUBS.

Each have their pitfalls and good points.

THAT is why I asked what is so important about being able to clamp/unclamp midcycle. I still don't understand the need to do that.

If you really have a need to do it we can help you work it out. BUT if you are doing it just because it seems cool to do so then I can point you to the resourses and answer questions as they come up.

Just a thought, (;-)

6485

General Mach Discussion / Re: VB or Brains Question

« on: August 12, 2010, 02:25:13 PM »

NOT a gcode but it may be possible to do it as a SUB or possibly a Mcode.

Is there a reason for wanting to clamp from inside the Cycle and not from a simple Mcode. Most CNCs that I am aware of do it like your DOS version.

6486

General Mach Discussion / Re: VB or Brains Question

« on: August 12, 2010, 01:24:21 PM »

The only way I know of would be to use a brain to monitor the Z positions and activate IF you went below a certain height and then deactivate above that height. You would also need a safety to ONY active if a condition were true. That way it would only work when you called the function pror to running the Cycle. then deactivate the function after the cycle was cancelled.

COuld you not just activate the clamp before the cycle and deactivate after??

6487

General Mach Discussion / Re: program causing pokeys to quit

« on: August 12, 2010, 12:22:36 PM »

Give it a try this way and see what happens



SetUserLED (1220, 1)
Sleep(100)
ActivateSignal(Output3) 'turn on chiller
Sleep (1000)
ActivateSignal(Output2) 'turn on spindle
Sleep(1000)
Code "S18000"
sleep(10)
Code"G4 P1200"
While Ismoving()
Sleep(1000)
wend
Code "S27000"
Sleep(10)
Code"G4 P1200"
While Ismoving()
sleep(1000)
Wend
Code "S36000"
sleep(10)
Code"G4 P1200"
While Ismoving()
Sleep(1000)
Wend
DeActivateSignal(Output2) 'turn off spindle
Sleep (1000)
DeActivateSignal(Output3) 'turn off chiller
Sleep(1000)
SetUserLED (1220, 0)
Sleep(100)
end

6488

VB and the development of wizards / Re: M6 - Turret not picking up signal correctly

« on: August 05, 2010, 09:52:53 PM »

IF you get a change try the code something like this to see IF it is any faster.



'Macro Tool Changer

Sub Main()

Dim Tool As Integer
Dim OldTool As Integer
Dim NewTool As Integer
Dim MaxToolNum As Integer

NewTool = 10
MaxToolNum = 8 'Maximum positions on Automatic Tool Changer
Tool = GetSelectedTool() 'Get the toolnumber from the command e.g T0101 M6 Tool number 1
OldTool = GetCurrentTool() 'Get current tool number



If Tool > MaxtoolNum Then GoTo 6
If TOOL = OldTool Then GoTo 7
 
ActivateSignal(Output3) 'Turn on output signal to turn off spindle and turn on the atc
sleep(10)
ActivateSignal(Output4) 'Turn atc forward
sleep (3000) 'Needed to start atc otherwise it plays up

While  NewTool <> Tool
   ' CheckPins
If IsActive(Input3) And Not IsActive(Input2) And Not IsActive(Input1) Then
NewTool = 1
GoTo 5       'StopTool
End If
If Not IsActive(Input3) And Not IsActive(Input2) And Not IsActive(Input1) Then
NewTool = 8
GoTo 5       'StopTool
End If
If Not IsActive(Input3) And Not IsActive(Input2) And IsActive(Input1) Then
NewTool = 4
GoTo 5       'StopTool
End If
If IsActive(Input3) And Not IsActive(Input2) And IsActive(Input1)Then
NewTool = 5
GoTo 5       'StopTool
End If
If IsActive(Input3) And IsActive(Input2) And IsActive(Input1) Then
NewTool = 7
GoTo 5       'StopTool
End If
If Not IsActive(Input3) And IsActive(Input2) And IsActive(Input1)Then
NewTool = 6
GoTo 5       'StopTool
End If
If Not IsActive(Input3) And IsActive(Input2) And Not IsActive(Input1) Then
NewTool = 2
GoTo 5       'StopTool
End If
If IsActive(Input3) And IsActive(Input2) And Not IsActive(Input1) Then
NewTool = 3
GoTo 5       'StopTool
End If

Wend

5:
' Stoptool
DeActivateSignal(Output4) 'StopATC
sleep(10)
ActivateSignal(Output5) 'Run ATC in reverse
Sleep (3000) 'Wait 3 seconds to allow the toolpost to lock in
DeActivateSignal(Output5) 'Stop running ATC in reverse
Sleep (1000)
SetCurrentTool(NewTool)
DeActivateSignal(Output3) 'Turn off output to turn spindle back on
sleep(10)
GoTo 7

6:
MsgBox ("Tool out of RANGE")
Goto 7
 
7:

 End Sub
 

6489

Galil / Re: Mesa card plugin

« on: August 05, 2010, 12:58:45 PM »

(;-)

6490

VB and the development of wizards / Re: M6 - Turret not picking up signal correctly

« on: August 05, 2010, 11:39:47 AM »

Another thought, can you make the dwell longer on your encoder for the grey code? that would give mach more time to see it. I looked at your code and it seems ok up front with simple testing Just need to work out the timing issues with the encoder and VB. With your mechanism you should be able to stretch the encoder signal out to JUST before the next tool position as you do a back down to lock it in it would just take a bit longer to back down

The Brians are much faster BUT I don't see a fast way to access VB from the brians. and you end up with the same problem