Hello Guest it is May 22, 2024, 03:57:15 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 - thosj

PoKeys / Re: PoKeys 57U, Mach4, Buttons and you.
« on: March 24, 2019, 10:41:37 AM »

PoKeys inputs don't have to match Mach4 inputs. You can assign whatever PoKeys input to any of the available Mach4 inputs. I guess you won't be able to use all 75 PoKeys inputs, but 64 at least!! I have a 57E so only 55 inputs, not 75, but nonetheless.......

So in Mach4, Config/Plugins/Pokeys, configure pin 75, back to Config/Control, inputs tab and set that to whatever Mach4 input you like. Then write your code.

If I misunderstand, well, that's pretty normal:)


Go into your profile's macros folder and delete, or MOVE someplace else just in case, ALL the *.mcc files, ALL of them. Start Mach4, all *.mcc files will be compiled anew from the *.mcs files, and MAYBE your error goes away. Or not...but this worked for me. Bryanna told me this trick when I had the path error trying 4124. Not sure it was the same error you had as you didn't post the exact error. Must be something with LUA 5.3.


Mach4 General Discussion / Re: DRO Properties
« on: March 13, 2019, 12:10:45 PM »
I'll go for 2 of the 4!

In place means  you can click in the box and edit the number

Read Only means you can't click in the box and edit the number.

Looking forward to learning what the other two mean!!

Mach4 General Discussion / Re: Lua Error Code on Start up
« on: March 03, 2019, 11:58:54 PM »
Did you look around line 702 of screenscript.lua and see if you can figure out where that part of the code came from? Maybe the screen start script or the PLC script? Like Craig said, screenscript.lua is a compliation of eveything, but you can usually figure it out. It might trip your memory as to what you were doing that caused the error. It likely won't point directly to the error causing line, but should give you a clue. On mine around line 702 is the screen start script, but yours might not be. I use Notepad++ to see the line numbers!!


Mach4 General Discussion / Re: touch probeing
« on: March 01, 2019, 09:35:23 AM »
Hey Chad,

Just out of curiosity, what's that little side thingy on that tool setter you linked? I almost bought one to find out, still might!!!


Mach4 General Discussion / Re: changing value in CurrentX dro
« on: February 28, 2019, 12:23:43 PM »
I have tried several things to get a specific number in the CurrentX dro.

Have you tried clicking in the DRO and typing the number you want?


Mach4 General Discussion / Re: Mach 4 and fusion 360
« on: February 16, 2019, 09:01:52 AM »
Are you milling or turning? You mentioned a square with holes so I assumed milling.

Google shows G71 as a Fanuc turning gcode, not a G21/G20 alternative. That M26 in your gcode is a little odd, too, http://www.cncsnw.com/G92G52M26.htm

Perhaps, even LIKELY, I misunderstand your dilemma:)

What Fusion post are you using?



Mach4 General Discussion / Re: Setting up Spindle/VFD control Issues
« on: February 07, 2019, 08:49:33 AM »
Wow, Craig, most excellent post!!

Only thing I'd even consider adding, for the OP's understanding, is the PWM frequency is unrelated to the VFD's frequency!!

I got my post all tuned up, too. Wish I'd understood this G30 thing before. I went in the post and edited the G28 stuff by hard coding it to use G53, kind of clunky and I wasn't sure I didn't screw something else up. With the G30 thing I just set the property Use G28 from true to UseG30 so it's the default, then I simply had to redo my M43 macro stuff, which is easy.

So I'm all good, I learned some stuff along the way which always makes me smile:)


Added this at the end of my Ref All Home function in the Screen Load Script:

        --Set G30 # variables
   mc.mcCntlSetLastError(inst, "G30 # Variables set")

Works! Fire up the control, Ref All Home, G30 Vars are set each time. Goes with my screenset, so no need to remember if/when I upgrade Mach4.

Off to VS Code to work on my post!