Hello Guest it is March 28, 2024, 09:38:21 AM

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Ron Ginger

701
Newfangled Solutions Mach3 Wizards / Re: Wizard output - saving
« on: August 15, 2008, 09:31:07 PM »
Yes, the wizard generates a main file called NewProgram.tap that is placed in the Gcode folder, and Index.tap that is placed in the subroutine folder.

You can simply rename the files using Windows Explorer to whatever you like. You will have to also edit the NewProgram.tap file to call whatever name you give to the index file. Then simply use the Load Gcode button and choose the file. When it runs mach will find the subroutine.

702
The problem is that the wizard generates some A axis moves, in a subroutine and the mach display code does not handle A axis moves. When Brian makes the graphic changes he is working on this may change.

The wizard generates working code, you just dont get the toolpath display

703
Newfangled Solutions Mach3 Wizards / Re: Pocketing Wizards Fin Pass
« on: August 15, 2008, 09:18:36 PM »
There are no plans to make any major wizard changes.

 However, you can do what you want with the current wizards rather easily.

Remember, the wizards are meant to be used in a series to make more complex parts. First use the pocket wizard,  but specify a Pocket diameter smaller than you want by the amount of the finish cut. Then use a cut circle wizard to cut a final size circle. For finish on the bottom of the cut you could make the second finish pocket to full depth, and specify just one cut of the full depth.

The rectangle pocket does have a finish cut setting and will generate correct finish cuts.

This is not quite a simple as one wizard that deos it all , but it works.

704
VB and the development of wizards / Re: Buttons to turn on LED's
« on: August 15, 2008, 09:08:58 PM »
Do you mean a mach screen LED or a physical LED in a panel? The above answer would handle physical LEDs that were connected to Output# signals.


If you mean screen LEDs. then each button needs to have code in it like this. Assume we are using LED1000, 1001, 1002 etc Each button looks the same, except it turns on its number and off all the others

 Call SetUserLED (1001,1)   'button 1 turn on led 1
  Call SetUserLED (1002,0)  'turn off all otehrs
  Call SetUserLED (1003,0)
  Call SetUserLED (1004,0)
  Call SetUserLED (1005,0)
  Call SetUserLED (1006,0)



705
The wizard sets G98 in the init code. Im not sure why it was designed to use G98 instead of G99, but it does. I will talk to Brian and see if he has a good reason for this.

The G43, H3 line is complicated. The wizards are designed to let you build a complex job by using several of the individual functions. There is code in each function to see if the tool has been changed in this function, and if so it add the G43 H(tool num). However, if this is the first function in this session,  its going to insert this code- in your example you are using tool 3, and the wizard cannot tell if you have previously set tool3 so it must do it to be safe.

If you do not use tool table values be sure to set the tool number to Zero in the tool screen. If you are using tool offset then it is important to have the  offset applied. If it happens that the offset was already applied before the wizard ran there is no danger in doing it over.

706
The while IsMoving loop is not needed here, thats only when Gcode is being executed and you need to wait for it to complete. That probably doesnt hurt anything, since there is nothing moving it falls right thru.

Try the if test like this:

IF Cur_Z_Inhibit then
  DoOEMbutton(167)
END IF

TRUE should be 1, but any positive number is OK, so maybe the LED function is returning some other positive number.


707
Newfangled Solutions Mach3 Wizards / Re: V2.78
« on: July 15, 2008, 07:44:30 PM »
Ok, very sorry for the long delay, but here it is.

I called it 2.78T because it is the same as 2.78 except for 2 changes.

1) The main screen has been fixed to test for the path using an old VB command, instead of the newer Mach specific call. It works the same, just more trouble to code. I think I have found all the places that refer to path, but if Ive missed any let me know where and Ill fix them.

2) on the tool select screen the button that displays the tool table cannot show the tool description, it will show as 'unknown'. This is because the Tormach version does not have the new VB call GetToolDesc.

I spoke to John and he expects a new Tormach version will be ready 'later in the summer' He is aware of the need for these VB fixes and they should get added then.

sorry it took so long,

ron ginger

708
General Mach Discussion / Re: classes on g code and mach 3
« on: July 05, 2008, 08:44:37 AM »
I agree that we need to be able to read basic Gcode. But I do not think one needs to spend days learning what is really trigonometry to be able to write G code. Even the simplest projects are likely to be more accurately done using decent software to generate the  code.

I have made several signs and name plates and obviously they would be impossible without CAM software. For simple tasks, like facing stock or circular pockets or bolt circles then use wizards to generate the code.

709
General Mach Discussion / Re: classes on g code and mach 3
« on: July 04, 2008, 03:01:01 PM »
Dont waste your time studying G code. You will only write the most trivial of programs by hand. For any interesting work you will need to use some software to generate the code. Pick a good CAM system and lean it.  Any interesting parts will be thousands of line long, no one can write that directly.

For plain mechanical work I use Sheetcam. I recently bought Vetric Vcarve Pro and think its great for the more artistic and sign making work.

710
Flash Screens / Re: Mach3 Flash OEM .fla: "Mach Nation 11-20.fla"
« on: July 01, 2008, 07:49:16 PM »
First you buy the Flash compiler, for about $700. Then you learn Flash. Then you figure out how Flash is hooked to Mach.

Not as easy as using Screen4.