Messages

4551

General Mach Discussion / Re: G65 and Macro Variables

« on: March 11, 2012, 09:18:58 PM »

Well actually IF you had true conditional Gcode with access to the system parameters it would not really be a problem AS you would not have to depend on the CB Macro system for such.  Conditional along with SUBS provide everything you would need.

Just do like everyone else does, route all the dros and sys parameters to a #var. Then call them as needed in the Gcode as a #var. There IS a segment of #vars already linked to a set oemdros. BUT there is no easy way to fill the Dros with known systems values and keep them current OTHER than a macro pump or a large brain.  BUT both of those are SLOW with updates.

One can dream, (;-) TP

4552

General Mach Discussion / Re: G65 and Macro Variables

« on: March 11, 2012, 11:43:23 AM »

HIYA ROGER, I would not hold your breath for Conditional in MACH4. (;-(

Even using CB it is not dependable at times and certain processes. I try to get the job done staying strictly in Gcode whenever possible. ROGER has a method that he can make work ,I get lost in its logic. BUT it works for him.

(;-) TP

4553

General Mach Discussion / Re: Can't raise feedrate past 50 in./min. without messing up... suggestions?

« on: March 10, 2012, 10:39:32 PM »

I would check your voltage then contact the motor manf and find out what the maxium voltage the motors can safely run . The Geckos can handle up to 80 volts but i would  give it a small safety and just use up to 70-75 volts.

AMPS in general give you torque and VOLTs give you speed.

(;-) TP

4554

General Mach Discussion / Re: G65 and Macro Variables

« on: March 10, 2012, 10:29:10 PM »

WIth mach3 there is NO G65 function. #vars have full math functions and can be loaded at any time.

M98/99 deals with Sub programming

Mcode (m1001) are available to use special internal functions and mixed with Gcode inside the macro and does give conditional INSIDE the macro only.

Mach3 Gcode does not have conditional Gcode .

I wouold start with teh Mach3 manul then goe the Mach3 /CB (Cypress Basic, similar to VB) programmers manual and the Mach3 macro programmers manul.

That should get you going.

(;-) TP

4555

General Mach Discussion / Re: Can't raise feedrate past 50 in./min. without messing up... suggestions?

« on: March 10, 2012, 02:49:55 PM »

What is the power supply VOLTAGE to the drives That more than anything will set the max speed of the motor. What are your motors rated for?

(;-) TP

4556

G-Code, CAD, and CAM discussions / Re: More questions on calling sub-routines

« on: March 10, 2012, 12:31:37 PM »

NOT with MACH3 it does NOT do conditional Gcode.

What you would need to do with MACH3 is do the DEPTH value/ step depth then round UP to the next whole number. NOW this does mean you will have to start eh process HIGH to account for the roundup.

IE:  Depth of  10.5mm / 1mm =  10.5 steps RU to 11.  NOW figure 11x1mm = 11mm  ,  11mm-10.5 = .5   So you would start the process .5mm high to get to the proper depth with 11 steps.

Then just apply that to the Gcode  M98 P?? L11

Hope that helps, (;-) TP



(;-) TP

4557

General Mach Discussion / Re: Encoder Problem

« on: March 09, 2012, 08:59:30 PM »

THis could also be a lost steps senario IF the only thing you are looking at is the DROS.  Just because Mach3 puts out the pulses does not MEAN that the motor actually follow it perfectly all the time. In this case IF the motor lost steps the Axis Dro would say one thing BUT the encoder would say another.

Just a thought, (;-) TP

4558

General Mach Discussion / Re: subroutines

« on: March 09, 2012, 08:51:03 PM »

Yes after the M30.

(;-) TP

4559

General Mach Discussion / Re: G65 and Macro Variables

« on: March 09, 2012, 08:45:52 PM »

IF you are referring to subs, nested subs and #vars then yes MAch3 does it to a point.  Look in the manual for info on M89/99 sub programming. 

NOW be aware that Mach3 does NOT do any conditional gcode.  There is some limited support for this thru the macro subsystem

AND there are restrictions as to what is possible from the #var side. You cannot directly access the ALL the System DROs for example. BUT you can supply the system values through a macro subsystem. It just gets complicated and sometimes unpredictable (CB).

(;-) TP

4560

General Mach Discussion / Re: Encoder Problem

« on: March 09, 2012, 04:00:13 PM »

I think what he is alluding to IS the encoder is attached to the stepper motor shaft. AND the encoder should read what the DRO says IF the two are properly calibrated and IF the steps per rev indicate close enough to be repeatable.

(;-) TP