Messages

491

Mach4 Toolbox / Re: Mapping screen button to pokeys ExtBus pin

« on: May 17, 2017, 12:20:34 PM »

I haven't had a chance to play with the pokeys and Mach4 yet myself but had look at Custom signal mapping in their manual included in the zip at the following link and it seems like it should work.

https://www.poscope.com/wp-content/uploads/downloads/Pokeys/LibrariesAndPlugins/PoKeys%20Mach3%20plugin%20+%20manual%20(28.3.2017).zip

Configure the inputs, add the input signal to the sig lib table in the screen load script and create the function there that you want to run when the input signal changes state.

492

Mach4 General Discussion / Re: Configuration of Mach4 for homing with reference contacts

« on: May 12, 2017, 12:53:17 PM »

Home in Place works fine here in Mach4 with the ESS.

493

Mach4 General Discussion / Re: image manager?

« on: April 23, 2017, 08:22:33 PM »

Open your screen in screen edit mode, then screen, then manage images. Don't be scared to poke around.

494

Mach4 General Discussion / Re: Screen load script question

« on: April 14, 2017, 01:19:07 AM »

Good, no shortage of ways to do it in lua, that's for sure. Just pick the way that works best for you.

Something like this might work too......
local hreg = mc.mcRegGetHandle(inst, string.format(your missing part of the srting here .. '//' .. whatregister .. '//' .. regname))

Or

"iRegs0//"

The best way to find out for sure is to just do it and test and adjust until you get what you want.

495

Mach4 General Discussion / Re: Screen load script question

« on: April 12, 2017, 10:56:16 PM »

Get rid of the formatting tags and see how it does.

WhatRegister = "iRegs0/%s"

Should be

WhatRegister = "iRegs0"

This isn't right either.........

local hreg = mc.mcRegGetHandle(inst, string.format(whatregister,regname))

"core/global/Version"

local hreg = mc.mcRegGetHandle(inst, string.format(your missing part of the srting here .. '/' .. whatregister .. '/' .. regname))

Play with until you can read and write to a single register in debugger then move on to functions then functions with parameters passing.

496

Mach4 General Discussion / Re: Screen load script question

« on: April 12, 2017, 09:13:08 AM »

Paste in all of your script......... the function from the screen load script and the script you put in a button that works.

497

Mach4 General Discussion / Re: Reading text box on screen

« on: April 11, 2017, 07:11:00 PM »

I'm on 2914.  Can I update without upsetting the license, screenset or directories I'm currently working on?  I know Mach 4 uses a different licensing scheme than Mach 3

Other than the license, absolutely ........assuming of course you have not been modifying anything that comes with Mach (defaults, which no one should ever modify). Customizing defaults makes a mess and is almost always a very bad idea.

License changed at some point but you can login to your account you created when you bought the license and mange your license if you need to disable the existing and generate a new one.

498

Mach4 General Discussion / Re: Screen load script question

« on: April 11, 2017, 04:16:53 PM »

Nothing special to run a function from the screen load script in a button script. Just call the function by the same name used in the screen load script and pass it any parameters if it has any.

MyFunction()
MyFunction(param1, param2, param3)

Another way to do it is to put the function in a module. Then you can run it from a buttons script or Mcode. You just have to load the module in screen load (so buttons can use its functions) and in a module that is in the macros folder (so Mcodes can use its functions) of the profile your using.

There has not been a release since I added the load_modules.mcs file to all of the default profiles macros folders but you can manually add it to any version. I have already posted this somewhere before but here it is again.

Code: [Select]

--This is the mcUserScript.lua module that goes in the modules folder
local mcUserScript = {}

function mcUserScript.UserMessage(Message)
if (Message == nil) then --No message was passed
Message = "No message passed" --If no message is passed this will be the default message
end
wx.wxMessageBox(Message)
end

return mcUserScript -- Module End

--This is what loads the module above.
--Add this to the modules load section of the screen load script so you can call its functions from buttons on the screen.
--Add this to the load_modules.mcs file in the macros folder of the profile that will be using it so you can call its functions from M codes.
package.loaded.mcUserScript = nil
us = require "mcUserScript"

--Put this in a buttons clicked script and when you click it a message box will pop up that says... No message passed
us.UserMessage() --This is not passing a message for the Message parameter so the message will be the default

--m110 goes in the macros folder of the profile that will be using it. It will be named m110.mcs
function m110()

us.UserMessage("This is my message") --When M110 is executed in Gcode or MDI a message box will pop up that says This is my message.

end

if (mc.mcInEditor() == 1) then
 m110()
end


499

Mach4 General Discussion / Re: Reading text box on screen

« on: April 11, 2017, 03:32:46 PM »

Have you tried that?

I have. Can get it and set it as expected here.

Code: [Select]

MyTest = scr.GetProperty("txtTest", "Value")
wx.wxMessageBox(MyTest)
scr.SetProperty("txtTest", "Value", "Test2")

Doesn't work on my end.  Maybe they exposed the value property in a later version.  What version are you running? 

Just so we're on the same page, we are talking about a textbox here, not a DRO.  If I place a textbox, I don't see a "Value" property associated with it.  If I place a DRO, I do see a "Value" property.

Version 3233, which you should be running too. It may well not have been accessible in earlier versions, I can't say for sure though.

Yup, I am talking about a textbox, not a DRO.

500

Mach4 General Discussion / Re: Reading text box on screen

« on: April 11, 2017, 01:32:55 AM »

Have you tried that?

I have. Can get it and set it as expected here.

Code: [Select]

MyTest = scr.GetProperty("txtTest", "Value")
wx.wxMessageBox(MyTest)
scr.SetProperty("txtTest", "Value", "Test2")