Messages

1101

Mach4 General Discussion / Re: Mach 4 Bug Reports

« on: May 05, 2014, 06:18:08 PM »

This is what I get.  You might have some other setting bonked?  Look in the general tab and make sure.  It has got to be something local to your machine. 

Steve

1102

Mach4 General Discussion / Re: Mach 4 Bug Reports

« on: May 05, 2014, 04:53:58 PM »

G65 local vars?  You mean the parameters?  Or this:

#1 = 2
#2 = 4
G65 P1000 X#1Y#2

type of thing?

The general rule of thumb is that result accessing local vars without first setting them "locally" is undefined.  They may have a value.  But it may not be what you want.

Try this...  Graham converted and it seems to work fine.

G50 G40 G80 G20 G94 G91.1
#101=1 (size of box)
#102=.125 (cutter radius)
#103=.125 (size of box bars)
#104=1 (degrees of resolution)
#105=#104 (COUNTER)
#106=[[#101/2]+#102] (ACTUAL RADIUS OF CIRCLE - CUTTER RADIUS + RADIUS)
G01X0Y0F100
m3 s3600 m8
M98 P140 L40
G0Z0
X0Y0
M30
%

o140 
   #108 = [[SIN[#105]*#106]*SIN[45]] ( X AND Y POSISION)
   #109 = [0-[[1-COS[#105]]*#106]] (Z HIGHT)
   g4 p0
   G1X[#108]Y[#108]F30
   Z[#109]
   G18 G02 X[0-#108] Z[#109] I[0-#108] K[0-[#109+[#106]]] F5
   G19 G03 Y[0-#108]Z[#109]J[0-#108]K[0-[#109+[#106]]]
   G18 G03 X[#108]Z[#109]I[#108]K[0-[#109+[#106]]]
   G19 G02 Y[#108]Z[#109]J[#108]K[0-[#109+[#106]]]
   #105=[#105+#104]
M99

1103

Mach4 General Discussion / Re: Mach 4 Bug Reports

« on: May 05, 2014, 04:11:19 PM »

I'm glad Graham caught it because I was missing it.

To explain further because this IS a change from how Mach 3 operated.  It is because you are using local vars to pass values to a sub.  Used global vars instead.  Because the local vars are "local" to the main program just as they would be "local" to a sub.  local vars acted like global vars in Mach 3, which was not correct.

Steve

1104

Mach4 General Discussion / Re: Mach 4 Bug Reports

« on: May 05, 2014, 03:51:22 PM »

Hmm...  I know that G17/18/19 have all been made to work "correctly" as to conform to Fanuc.  So it may be a case that the older Mach3 G code just may not work anymore.  We will have a look and see!

Steve

1105

Mach4 General Discussion / Re: Mach 4 Feature Request

« on: May 05, 2014, 03:28:06 PM »

I think this is a Sim issue.  Because Sim always starts at machine 0 for any given motor.  So when Mach fires up, the motion controller provides the machine position to Mach.  Sim is sending 0 because it is not a real motion controller and we don't save the positions anywhere during shutdown.  With my Galil, I always get what the encoders says.

I'm working on a new build.  It will have the updated screen plus a lot of other stuff that you guys have asked for.

1. Pop up keypad for editing DROs (Auto Calc).
2. Feed Rate tracks G20/G21 correctly.
3. Recent files can have a path longer than 80 characters.
4. File->Open "remembers the last directory instead of starting with the current working directory.
5. Button actions to show the tool and fixture tables.
6. Fixed the softlimit enable check boxes in the configuration.

1106

Mach4 General Discussion / Re: Mach 4 Feature Request

« on: May 05, 2014, 01:16:16 PM »

Dan,

Explain to me what you are wanting.  Because the DROs seem to be persistent for me.  But I might just be missing the point of your request.

Steve

1107

Mach4 General Discussion / Re: Lua Editor Crashing

« on: May 05, 2014, 12:44:22 PM »

Russ, are you running XP or any other 32 bit OS?  Just curious...

1108

Mach4 General Discussion / Re: Mach 4 Bug Reports

« on: May 05, 2014, 12:40:21 PM »

Recent File entries not working with long strings

Description:
When loading G code files with filename length > 80 characters, the file will load successfully. Clicking Recent File button later will fail, if full path and filename is longer than 80 characters, because path is stripped after 80th character.

Ok, good one!  Thanks.  It has been taken care of.

1109

Mach4 General Discussion / Re: Mach 4 Bug Reports

« on: May 05, 2014, 12:33:31 PM »

Yes, please provide an example.  The sub stuff is all new code (as most of Mach 4 is), so there is bound to be something that doesn't work the same as Mach 3.  The example will help me make it more compatible.

Are you talking about macro A?  Because that will not work at this time.

Steve

1110

Mach4 General Discussion / Re: Mach4 Probing and reporting

« on: May 04, 2014, 02:17:50 PM »

Terry, I just gave the way to do it right above.  I wasn't arguing.  I was giving you what you wanted!  Or did I miss something?

I'm talking just a few lines of code in a script file (not tons) and you can have what you want.  That is why we built Mach 4.  So that people could make it do the things they want without having to wait on some programmer to do it.

Now, the torque limited move is something a little harder to do because it requires that the motion controller be able to do this.  But everything else you wanted can be done rather easily.