Hello Guest it is April 19, 2024, 05:03:42 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 - Elektroniker

Pages: 1 2 »
1
Mach4 General Discussion / Re: How to change probe parameters
« on: August 10, 2023, 06:44:07 AM »
Hello,

Today I had the same experience with Mach 4 Hobby 4.2.0.5165.

Hope somebody has good advice for us.

2
Mach4 Plugins / Re: Pokeys Mach4 plugin LUA reference for LCD
« on: March 29, 2019, 11:43:57 AM »
Hello Danie,

I'm glad to read that your problem is solved.

Kind regards,
Wolfgang

3
Mach4 Plugins / Re: Pokeys Mach4 plugin LUA reference for LCD
« on: March 28, 2019, 02:38:27 PM »
Did what you recommended. I've completely removed the code in the On Update Script and linked the DRO register to the PoKeys LCD register from the drop down list. But the LCD doesn't update when moving the axis.

4
Mach4 Plugins / Re: Pokeys Mach4 plugin LUA reference for LCD
« on: March 28, 2019, 01:23:19 PM »
At the moment I'm using Build 4132.

Kind regards,
Wolfgang

5
Mach4 Plugins / Re: Pokeys Mach4 plugin LUA reference for LCD
« on: March 27, 2019, 12:01:44 PM »
Hello Danie,

the code  of the On Update Script which is working seemlessly on my machine looks like here:

local val = select(1,...)
Xcoords = val
val = tonumber(val)
local inst = mc.mcGetInstance()
mc.mcCntlSetLastError(inst, "On update ran")
local Xcoords = string.format("X:% 10.4f", Xcoords)
local hreg = mc.mcRegGetHandle(inst, string.format("PoKeys_34497/LCD Line 1"))
mc.mcRegSetValueString(hreg, Xcoords.."        ")
return val

Not too much differences to your code. Maybe this helps a little.

Kind regards
Wolfgang

6
Mach4 Plugins / Re: Pokeys Mach4 plugin LUA reference for LCD
« on: March 22, 2019, 11:23:07 AM »
Hello,

with the recommendations of Bryanna the output of the DRO to the LCD of the PoKeys is working.

What I've found is the fact, that the values on the LCD are lagging the DRO values when I use this code:
local Xcoords = scr.GetProperty("droCurrentX","Value")

The correct value which is identical to the DRO on screen is val by itself.
So we can simply write:
local Xcoords = val

Sometimes the changes in the On Update Script are showing no effect after saving and leaving the editor.
Only when closing and restarting Mach4 the changes in the code where recognized.

Hope this is of help for somebody.

Wolfgang



7
Mach4 Plugins / Re: Pokeys Mach4 plugin LUA reference for LCD
« on: March 16, 2019, 04:36:12 AM »
Hi,

same effect to me...

Even 2 hyphens as comment in this code section of the On Update Scripts are inhibiting the update of the DRO values. It seems, that this is a more as a matter of principle.
At the moment I'm working with Mach4Home build 4095 which is licensed.

Maybe some of the experts have an idea what could be wrong?

Thank you in advance,

Kind regards
Wolfgang

8
Mach4 Plugins / Re: Pokeys Mach4 plugin LUA reference for LCD
« on: March 04, 2019, 08:01:33 AM »
Hi,

got to implement all the code for outputting the axis DRO values to the Pokeys56U LCD. But the values of the axis DROs and the LCD are updated only once when the axis are moved and no error messages apeared. What could be the reason for this effect?

Any help is appreciated

Kind regards
Wolfgang

9
PoKeys / Re: Pokeys56 and Smoothstepper (ethernet)
« on: March 19, 2014, 04:24:48 AM »
Hi NeoTo,

I experience exactly the same effect, but with an Smoothstepper USB. If the encoder of the pendant, based on the PoKeys56U, for SRO at pins 5 and 6 is disabled, there are absolutely no problems with the smoothstepper. The fault with the smoothstepper, as mentioned by TanTan, occurs only with the encoder for SRO set active, even with RC- filters attached to the inputs. There is no difference whether you make a move of an axis with the MPG or by running a job.
With the spindle switched off, it doesn't matter whether the encoder for SRO is active or not.

Wolfgang

10
PoKeys / Re: Pokeys56 and Smoothstepper (ethernet)
« on: March 18, 2014, 05:46:07 PM »
Hi,

I think I've have to agree with you. I hope this issue could be cleared by an update of the plugin.

Pages: 1 2 »