Hello Guest it is April 23, 2024, 09:56:48 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.


Topics - damo green

Pages: 1
1
Are G16 polar moves limited to the x-y plane?

If they are limited to the x-y plane then I will use FORMULAS instead

Thanks in advance.

2
 | INPUT#1    0/:1  | -------| COMPARE =1 |               when I toggle the physical switch, I can watch the brain and see the input rung color & value toggle accordingly between 0 & 1 , bu the COMPARE rung will never toggle  even though the input matches "1"

I also tried  with | COMPARE >0|  , also does not work, just like above. I suspect it is because it is boolean  and 1/0 does not  represent true/false  exactly ?...but can not input "true" into the compare field…
---------
I found a workaround by comparing and LED set to "1" to the input and that did work…..which was a workaround in itself because trying to set an Input to be a local variable causes  Mach3 to hang…..


Would like to be able to write the brain without having to edit a screenset and set an led to "1" as a crazy workaround...

3
I've googled a lot so I've checked the usual things (see below)

Problems:  No RPM showing in Mach3 (Mill OR Turn)
                  
 
Data:  [YES] Mach3 IS showing consistent index pulses
            [YES] I am starting spindle with Mach 3 "spindle button" or M3 in MDI
            ALSO when using this board and Mach3 *TURN*  code will run to G76 line and then "waiting for trigger"
 
Checks: [YES]Selected Pulley is set to Ratio=1 , mach3 throws appropriate error if speed is out of range of selected  pulley (  setting S number in DRO…as a test as my  spindle is simple on off by M3/ relay)
               Index pulse sensor is mounted on spindle
               Pulses are clean on scope and long enough in duration , very consistent
                       I am using a JNC-40M USB controller board and Index pulses are consistently triggered in Mach3
               [YES] Debounce interval and time are both 0,0 higher numbers make no difference (probably not relevant   in  my case anyway ,since using USB Controller board)
               Spindle feedback and averaging are both checked/on

Could the code that OEM DRO 39 calls be incorrect? Can a user examine/edit it somehow?
(note: probably NOT the problem as  Mach3 is also not recognizing index pulse as a valid threading trigger)
            


4
General Mach Discussion / Coding error in M6End.m1s
« on: July 07, 2015, 06:08:45 PM »
I was getting an unexpected Z move after a tool change.
The file M6ENd.m1s that come with the Mach3 download contains this:


REM The default script here moves the tool back to m6start if any movement has occured during the tool change..

x = GetToolChangeStart( 0 )
y = GetToolChangeStart( 1 )
z = GetToolChangeStart( 2 )
a = GetToolChangeStart( 3 )
b = GetToolChangeStart( 4 )
c = GetToolChangeStart( 5 )
if(IsSafeZ() = 1) Then
   SafeZ = GetSafeZ()
   if  SafeZ  > z then StraightTraverse x, y,SafeZ, a, b, c
      StraightFeed  x, y,  z  , a, b, c
else
Code"G00 X" & x & "Y" & y
end if


Should it not really be THIS:

REM The default script here moves the tool back to m6start if any movement has occured during the tool change..

x = GetToolChangeStart( 0 )
y = GetToolChangeStart( 1 )
z = GetToolChangeStart( 2 )
a = GetToolChangeStart( 3 )
b = GetToolChangeStart( 4 )
c = GetToolChangeStart( 5 )
if(IsSafeZ() = 1) Then
   SafeZ = GetSafeZ()
   if  SafeZ  > z then StraightTraverse x, y,SafeZ, a, b, c
   else   StraightFeed  x, y,  z  , a, b, c
else
Code"G00 X" & x & "Y" & y
end if
_______________
My safeZ was higher than z.....so it was doing a rapid move to safeZ and then ALSO an unexpected feed move to z (i'm ignoring other axis for this discussion)

The else needs to be included otherwise it performs both moves (when  SafeZ  > z)  ...?

5
Mach3 under Vista / G84 tap cycle spindle not turning random error
« on: July 02, 2015, 12:25:03 AM »
I'll do some more testing on this problem, but maybe you have some experience with it already.

I have a job where the PM45CNC with WIndows Vista & USB motion controller & normal (not variable/VFD motor) is tapping about 160x  4-40 holes, all in a row, 90 rpm spindle speed via gearbox.

It uses a G84 cycle and Mach3 is configured to wait about 1.5 seconds in between spindle reversals to allow the spindle to coast to a full stop before turning on again (in either direction). I have checked that even after the machine is very warm (longer coast down times), it always comes to a full stop before reversing in either direction.

I may actually have two problems.:

1) G84 is a modal cycle with 160 x-y tapping coordinates following it.
After some amount of holes ..could be around 70, Mach3 will throw an error "Spindle not turning clockwise" ...and so it pauses, if I hit F5 to turn the spindle CW , I am able to continue, and it will continue for many cycles as it should. This seems like a Mach 3 issue as there is no feedback to Mach 3 from the mill for it to know if the spindle is turning. It could only "know" the spindle is not turning because it did not command the controller to turn on...but why did it not command the controller to turn on after many cycles of normal behavior.....buffer problem or such maybe?

2) Other times , I will get a sever "buzzing" noise from the motor when it turns the motor CW...I think it only fails in the clockwise start from zero rotation, not CCW. (need to do more tests) . It may buzz for a few cycles in a row, but eventually it will trip the breaker.

I am experimenting with electrical fans on the motor as it may be heat related....or time related...However with #1 happening sometimes I think it may be a software problem with the Mach3 to the controller, my gut says it may be trying to rapidly tell the motor to go clockwise then counterclockwise rapidly...So far I have not noticed any problems with the earlier holes only the later holes (with respect to run time,not line number)...and it if it does occur and I restart the cycles without either a cooldown or a reboot it does seem to recur sooner than from a fresh start.

I'll do a lot more testing but....maybe someone has experience with this already

6
G-Code, CAD, and CAM discussions / How to make a Macro Modal in Mach3
« on: June 17, 2015, 06:20:30 PM »
I want to make a custom tapping cycle (floating) Macro.

I have successfully done this with manual coding, but I would like to make a Macro but it should be MODAL...i.e I call the Macro and then after it follows a list of hole coordinates to tap.

S0 how does one make a Macro to act in a modal way similar to how G81 is MODAL

REALLY want to avoid having to have a line for  every coordinate and then the next line have to call the Macro again....and again...and again

Pages: 1