Messages

731

VB and the development of wizards / Re: code "G04 P2.0" problem

« on: May 02, 2008, 10:59:45 AM »

OK, I have some updated info. If you check the box in config/general that says auto toolchanger then only the m6start runs. The m6end is only used when you do manual tool change.

Are you entering the full command- " m6 t0303" I dont think T3 alone works.

732

VB and the development of wizards / Re: code "G04 P2.0" problem

« on: May 02, 2008, 10:31:28 AM »

I am having the same trouble with my macro. It appears to me that when the m6start macro runs the tool number is the old tool, not the one we are changing to. I think when m6end runs the tool number has been changed.

I have a message in to Brian to get help on this, when I get it figured out I will post more here.

733

VB and the development of wizards / Re: code "G04 P2.0" problem

« on: April 28, 2008, 08:00:02 PM »

Always good to hear when an answer is found. There are many places in Mach for that kind of duplication. I have had several problems with macropumps using the same DROs as my wizards.

734

General Mach Discussion / Re: Macros

« on: April 27, 2008, 08:27:35 PM »

I have the following macro in the "set tool offset' button on the Offsetts screen

CurrentFeed = GetOemDRO(818) 'Get the current feedrate.
PlateThickness = 0.062 'plate thickness
ProbeFeed = 1.0 'probing feedrate


If GetOemLed (825)=0 Then
'Code "G4 P5" Time to get to the z-plate
Code "G31Z-1 F" &ProbeFeed
While IsMoving()
Wend
Code "G4 P0.25"
ZProbePos = GetVar(2002)
Code "G0 Z" &ZProbePos
While IsMoving ()
Wend
Call SetDro (2, PlateThickness)
Code "G4 P0.5" 'Pause for Dro to update.
Code "G0 Z 0.1" 'Change the Z retract height here
Code "(Z axis is now zeroed)"
Code "F" &CurrentFeed
Else
Code "(Plate is grounded, check connection and try again)"
Exit Sub
End If 


Note it has the plate thickness coded into it, and a move of .1 after the touch. You could edit those values to anything you want.

To use this select the offsets screen, then select from the Operator menu the item Edit button script. All the VB buttons will blink, select the 'Set tool offset' button. When the VB window opens delete all the code there and replace it with this code.

Note that this one is going to try to move Z to -1. If you were already below -1 it wouldnt move for a probe cycle. I ought to be more clever and do a relative mode of -1. Maybe someday Ill fix that.

735

VB and the development of wizards / Re: code "G04 P2.0" problem

« on: April 27, 2008, 02:38:22 PM »

How do you know its ignoring the G4?

try this simple test program:

code "G4 P10"
While Ismoving()
Wend

MsgBox "time done"


when I run it in the script editor there is a 10 second delay before the message box appears.

Are you sure output 5 and 6 are setup correctly? Be sure the port number is 2 if they are on the second parport.

736

Show"N"Tell ( Your Machines) / Re: Brian's Emco Compact 5 Retro

« on: April 26, 2008, 08:22:44 PM »

I had been looking for one of these lathes, then in a week I had 2 of them. Im going to sell the CNC, which looks just like Brians in the first photo of this thread. The machine is complete with turret and it all runs. Ive been able to figure out how to do some simple programs on it to test it.

I will be putting it on ebay later this week, but if anyone on this forum wants it let me know, we can save the ebay commission. Its in Maine, and I could deliver it to the CNC workshop, or anywhere along the way.

ron ginger

737

VB and the development of wizards / Re: code "G04 P2.0" problem

« on: April 26, 2008, 10:46:39 AM »

G4 is the correct function to use for a delay. G4 can measure time in either seconds or miliseconds, there is a check mark on the config screen to select.

While IsMoving is only needed on commands that cause motion, it is not needed on the activate output or deactivate. I dont think it will hurt, but it is not needed.

The following should work

Sub stop_and_lock_turret

   DeActivateSignal(Output6)
     
   ActivateSignal(Output5)
      Code "G4 P2"    'Wait for the tool to rotate onto ratchet stop
      While IsMoving()
      Wend
   DeActivateSignal(Output5)
     
End Sub   

738

Newfangled Solutions Mach3 Wizards / Re: Electrical shapes goes crazy

« on: April 20, 2008, 10:01:30 PM »

If it ran two cutouts fine, then the gcode generated is obviously OK and the wizard is out of the picture. Mach is simply running gcode.

My guess is that some other software- anti virus, auto update etc, took off in the background and confused the mach engine. Or other noise issues drove the motors nuts.

Can you get it to do that again and try to figure out exactly what conditions exist when it happens.

739

Newfangled Solutions Mach3 Wizards / V2.78

« on: April 15, 2008, 10:36:54 AM »

I have made a couple corrections so here is a new version. the fixes are:

1)Cut rectangle was not doing the rotate angle correctly.

2) On the main screen the buttons to list or delete an operation were fixed to the C:\Mach3 path. This now reads the base path so should work installs that use a different folder. I don't have a good way to test this one, so Id like feedback on how it works.

3) The preview screen now has a gcode window as well as the toolpath. I had added this to an earlier version, but somehow it got deleted later.

Let me know if there are any problems with this version. Brian will be adding it tothe install kit later.

ron ginger

740

Newfangled Solutions Mach3 Wizards / Re: V 2.77 ready for test

« on: April 11, 2008, 09:30:30 PM »

I just talked to Brian, G40.1 turns on the 'new comp' code. It doesn't hurt anything, its just an init condition.