Hello Guest it is May 22, 2024, 04:26:59 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

61
Mach4 General Discussion / Re: Mach4 license Debug Report
« on: March 22, 2022, 04:25:32 PM »
This doesn't LOOK like a license issue, but seems like a crash for some reason. Try installing fresh and see what happens.

I'd submit a support ticket for this, I guess.

62
Mach4 General Discussion / Re: Multiple Mach4 Installations
« on: March 22, 2022, 08:51:09 AM »
Here's my drill:

Rename the mach4 folder to something memorable, like mach4hobby_4612
Download and install whatever version you're interested in.
Get two explorer windows open, your old install since renamed and your new one
Copy the appropriate files from the following folders:
Licenses - ***.dat file, but copying both works, too.
Profiles - any profiles you've created, an entire folder
Screens - any screens you've created
Plugins - any plugins you use, ESS, PoKeys, pendant, whatever, two filer per plugin
Macros - these should come with the profiles folder
Modules - if you've written any, I have not, so I don't copy this, but you might.

I think there is a way to export your entire profile and import it into the newly installed version, but I've always done it like this.

All this said, this past weekend after upgrading to a new dev version, I had a license issue. Running Mach4 showed unlicensed. I checked online and my PCID didn't show up. I copied the PCID and got a new license, but this is the first time this has ever happened, not sure why!! I went back to the previous version by renaming folders and the old one was unlicensed, too. Not sure if PCID's somehow change with new versions or what happened there, same PC for a while now. Maybe if Steve or someone sees this they'll reply.

And YES, if you're installing on a new computer, you could install on the new one and copy your Mach4 folder over. Your license will need to be redone on the new one, with the new one's PCID, however. Everything should work. I always copy me entire Mach4Hobby folder off to a NAS periodically just for belt and suspenders security!!

OH, and just now remembering you have Industrial, Industrial might now work like this going to a NEW PC, just a new install on the SAME PC, especially with regard to licenseing. I don't think you get 10 PCID's with Industrial

Tom

63
Mach4 General Discussion / Re: Multiple Mach4 Installations
« on: March 16, 2022, 08:31:30 AM »
I do this all the time with hobby. I rename the Mach4Hobby folder so something else, install from scratch, copy the stuff over, license, macros, screens, profiles. Works great and I can roll back. Not sure it'll work with industrial, but I would think so.

64
Mach4 General Discussion / Re: Enforce Ref-All-Home
« on: March 15, 2022, 09:26:36 AM »
I'm not sure I'd want RefAllHome to just run on boot up, commercial environment or otherwise!! I ran Mach3 for years and I don't remember it running all by itself on bootup! Seems scary to me, but perhaps I misunderstand.

Just hit the RefAllHome button after it boots.

65
Hmmmm, isn't your G81 line drilling to Z0? So with the tool length offset applied, .1304, wouldn't it drill to PLUS .1304, "short by about 1/8"?

Don't know why T2 would be going about an inch too deep, it should be .2758 too deep assuming your drilling to "Z0" as your G81 lines indicate.

What's generating your gcode, or is it hand written?

And, I don't think the G43 line matters what order the G43, the H3, or a Z move are in.

66
Mach4 General Discussion / Re: Persistent Spindle Range DRO
« on: March 09, 2022, 09:48:51 AM »
Very cool, glad it worked!

67
Mach4 General Discussion / Re: Persistent Spindle Range DRO
« on: March 03, 2022, 12:17:08 PM »
It's been a long time since I did this, but here's what I find in the screenset and mine works like I think you want.

Screen Unload Script, my entire thing:

function Mach_Screen_Unload_Script()
    inst = mc.mcGetInstance()
                     
   
    local IsOpen = mc.mcProfileGetString(inst, 'TOffParams', 'ToffDialog', '0') -- Get the Value from the profile ini.
    if (IsOpen == '1') then --The TouchOff dialog is open and we need to close it
        Tframe:Close()
        Tframe:Destroy()
    end
   
    --Saves Spindle Range to profile on screen unload
    --local inst = mc.mcGetInstance() -- not needed if already declared
    local val = mc.mcSpindleGetCurrentRange(inst)
    mc.mcProfileWriteInt(inst, 'SpindleDefaultRange','Range',val)
end



Screen Load Script, at the end

ButtonEnable()
--Screen Load Script to set Range saved in screen unload script
--Screen Load Script
--local inst = mc.mcGetInstance()  -- not needed if already declared
local val = mc.mcProfileGetInt(inst, 'SpindleDefaultRange','Range',0)
mc.mcSpindleSetRange(inst, val)

68
Great stuff from Craig, as usual. An A axis doesn't NEED to be rotary, but that said, on your router, it's unlikely you have a linear A axis either, so disable it!!

69
You don't have to be a programmer to use Mach4, just some simple screen editor changes to get things "your way" then off you go. And.....Mach4 WILL run your machine much better that Mach3 ever did. Trust me, it was a hard pill to swallow for me, too, but now that I'm there, Mach4 is SOOoooo much better.

If you need the axis to be a slave, don't you NEED it to be a slave? Normally a slave axis is used on a machine that needs two motors driving one axis, like a gantry router. I don't know much about slaves, homing with a slave axis, or anything, really, so someone else will need to chime in here to help you out.

Hang in there, man, there are lots of folks here to help, but they're somewhat intolerant of questions asked that are easily answered by searching the forums or watching a few youtube videos!!! Not like LinuxCNC, however, where you're a dumb ********* if you can't program the kernel itself!!!

Tom

70
I don't know about the first part, but the last part explains why your Z is not going there!!

That is LUA, and you have to comment out the first line, add --, and remove the comment -- from the second line. Kind just like it says there!!

Axis 3 is likely not enabled unless you have some sort of third axis. If Axis 3 is a slave, it should move with it's main axis. If Axis 3 is A, likely, try removing the commanded A0 in the Go To Work Zero line you just commented/uncommented!!! It should look like this:

mc.mcCntlMdiExecute(inst, G00 G53 Z0\nG00 X0 Y0\nG00 Z0")--With Z moves   NO A0.

That line, BTW, moves Z to HOME, UP to the top typically, moves X and Y, then Moves Z back to it's Work Zero spot, so you don't hit something!!

Tom