Messages

171

PoKeys / Re: THREADIDNG ISSUES

« on: February 24, 2020, 10:53:31 AM »

Good morning gabedrummin,

It would be helpful if you posted the code you used to attempt to thread.  Did you write it yourself? Post that code.  Was it generated by a threading wizard? Attach a screen shot of the settings used.

Are you using Mach3 or Mach4?

More info gets more help.

RT

172

Mach4 General Discussion / Re: Problems - Win10 update + PMDX_424 + LUA

« on: February 14, 2020, 11:41:11 AM »

The mcLua.mcc file is recreated each time that m4 starts.  It reads all macros (*.mcs) for that profile and then outputs the compiled code to the mcLua.mcc file.  It appears that that file is not being made due to either lack of permission or that there is an error in one of the macros that it is compiling.  Are there any other error messages thrown before that one?

 Have no experience with encoders.  I see that pmdx has multiple encoder choices, bi or uni directional, reversed, with index, with synthetic, without index. 

I am using pmdx411 on a lathe.  Didn't think you could use 'U' as an axis.  I have x,z and b.

173

Mach4 General Discussion / Re: How to run functions in macros

« on: February 04, 2020, 11:43:42 AM »

Someone can correct me if I am wrong but I believe functions declared in the screen load script are only available to gui related activities, buttons, panels, etc.  There are two lua chunks running, a gui and a core chunk.  I believe you have to create a module either in the  Mach4Hobby\Modules directory, like the mcProbing.lua, if you want it available to all profiles or in the profiles modules directory if you want it available only to that profile.  You then reference that function within your macro. The mc.********* are available in both chunks but your personal funcs are only available in the chunk it uses.  Clear as mud eh?

myFuncs.SetSigState(mc.OSIG_OUTPUT2, 0)

HTH

RT

174

Mach4 General Discussion / Re: New to jogging/ non g-code moves

« on: January 31, 2020, 10:51:10 AM »

Instead of displaying 'failure' why not display wx.wxMessageBox(mcErrorCheck[rc])?  It might give you better debugging information.

HTH

RT

175

Mach4 General Discussion / Re: Create elements in Mach 4

« on: January 30, 2020, 02:53:31 PM »

Since no two individuals will ever agree on what should be included/excluded from a screen set NFS has given everyone the tools to make their own.  wxFormBuilder is similar to most Rad  dev systems but the linkage to a panel or interfacing with it is not well documented. 

I sent a pm to Bryanna suggesting a short step by step video of creating a form in wxFormbuilder and then using it in a panel.  Never got a response.

RT

176

Mach4 General Discussion / Re: Learning to use variables in my code

« on: January 19, 2020, 02:38:56 PM »

I believe while is only available to industrial licensed individuals.  Part of Fanuc B.

177

Mach4 General Discussion / Re: Safe and reload a Value

« on: January 19, 2020, 12:04:59 PM »

Yes, use a register and make sure the 'persistent' is ticked.

178

Mach4 General Discussion / Re: Learning to use variables in my code

« on: January 19, 2020, 12:00:17 PM »

I believe codes 1000+ are taken.  Try your same code with #'s less than 1000

HTH

RT

179

Mach4 General Discussion / Re: Mechanical speed ranges in Mach4

« on: January 15, 2020, 07:15:49 PM »

function m42()
   local inst = mc.mcGetInstance("Spindle range 2")
   local rc
   local currentRange
   currentRange, rc = mc.mcSpindleGetCurrentRange(inst)
   if (currentRange == 2) then
      return -- nothing to do!
   end
   -- Do the machine dependent range change control.
   --
   -- End machine dependent range change control

   -- Next, tell Mach what rage we are now in IF the above is successful.
   mc.mcSpindleSetRage(inst, 2) <----Should be: mc.mcSpindleSetRange(inst, 2)
end

if (mc.mcInEditor() == 2) then (to debug it should be: if (mc.mcInEditor() == 1) then
    m42()
end

180

Mach4 General Discussion / Re: Mechanical speed ranges in Mach4

« on: January 15, 2020, 11:05:20 AM »

daniba73,  you're not going to get much help if you don't follow the advice as given.  You say that you tried both suggestions and they didn't work but did not provide what you 'actually' did.  Attach the macro file that you tried and the gcode that you tried as well.

RT