Hello Guest it is March 28, 2024, 01:04:10 PM

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 - thespindoctor

Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 »
91
Danke, Heinhard

I am still working on it but had to delete another tab and rob everything from that tab to make it work.  Still don't understand it completely but I could not seem to effectively modify the screen load script to add another MDI to the CycleStart function.

Keith

92
Figured out how to load a gcode file with wx.widgets and it shows up in the other gcode windows on the stock tabs in Mach4-Mill.  However, when I add a gcode window to the tab I have created, the window is loaded with the code from the file but when I either hit the cycle start button or try to program a cycle start, it says nothing to run.  When I switch to another tab, the gcode is properly listed and will run with cycle start.  How do I link the new gcode window to the loaded code?  I cannot see any difference on the lua scripts or the properties of the other gcode windows.  Seems odd that is would not work.  I see the Lua code necessary to make an MDI window run code, but is there something not stated that I have not done?

Thanks
Keith

93
Mach4 General Discussion / Re: more lua (?) questions
« on: May 02, 2017, 08:04:22 PM »
But how do we learn how to use wxformbuilder?  I have not been able to get started with it and have dropped back to just trying to copy Lua code from example programs.
and making better progress.  So far can't find a basic tutorial and can't seem to find a doc for wxformbuilder that is understandable.  All the docs are more like a dictionary. 
Isn't there something out there for the beginners to get us started?  How did you guys set started with wxformbuilder?  Staring at the code has not worked for me.  I seem
to be doing better with Lua itself and screens.

94
Mach4 General Discussion / Re: Probing Question PoundVar 5062 amd 5072
« on: April 30, 2017, 06:45:01 PM »
Alan, makes sense to me.  I still have not been able to test a good fixture offset.

95
Mach4 General Discussion / Re: Probing Question PoundVar 5062 amd 5072
« on: April 30, 2017, 04:22:09 PM »
Here is where the confusion came from.  Below is the code from the mcProbing.lua module Probing.SingleSurfY function.

Code: [Select]
local MeasPointABS = mc.mcCntlGetPoundVar(inst, 5062)
local MeasPointMACH = mc.mcCntlGetPoundVar(inst, 5072)

Here ABS would be absolute and I would think machine coordinates relative to machine zero.
I would expect MACH to be the coordinates relative to the fixture zero.

See the problem?  The plugin from Warp9 uses the terms Work Position and Machine Position.  The plugin uses ABS and MACH. which is just the opposite of what the G Code programming manual states.
The manual uses G31 User Position and G31 Machine Position.

G53 would be machine or absolute position from machine zero.  G54etc would be fixture or user or offset position not ABS.

I'm done for now...

96
Mach4 General Discussion / Re: Probing Question PoundVar 5062 amd 5072
« on: April 30, 2017, 04:14:01 PM »
I think I figured it out.

G53 is machine coordinates also known as absolute coordintes?  In other words no offsets have been applied and the positions are coordinates relative to machine zero.  These values will be stored during probing in the variables 5071-5076
Work or user fixture coordinates are offset according to the users fixtures indicated by G54-G59.  G52 would be another type of fixture offset that I have never used.  Thus the coordinates stored during probing to variables 5061-5066 would be relative to the zero of the fixture.

That helps me.  I hope it helps someone else out there too.   If this is wrong, please correct me!

Thanks

97
Mach4 General Discussion / Re: Probing Question PoundVar 5062 amd 5072
« on: April 30, 2017, 04:04:33 PM »
this from the Warp9 forum on having fixed the plugin for the ESS for multiple probes.
I assume both sets of positions are loaded for whatever probe is being used.

Quote
Probe Work Position X 5061
Probe Work Position Y 5062
Probe Work Position Z 5063
Probe Work Position A 5064
Probe Work Position B 5065
Probe Work Position C 5066

Probe Machine Position X 5071
Probe Machine Position Y 5072
Probe Machine Position Z 5073
Probe Machine Position A 5074
Probe Machine Position B 5075
Probe Machine Position C 5076

So does what does Work position mean?
What does Machine position mean?

Thanks

98
Mach4 General Discussion / Re: Probing Question PoundVar 5062 amd 5072
« on: April 30, 2017, 03:59:30 PM »
I agree on page 19 (newer Mill GCode Programming manual) than I was looking at)
G31 User Position 5061-5066
G31 Machine Position 5072-2076

First, the probing module "probing.lua" uses the terms Absolute and Machine position rather than User and Machine Position.  This is a bit confusing.  I am familiar with absolute, machine, and relative coordinates.
Am I confused?

Also, can we assume that G31.1, G31.2, G31.3, G31.4 will use the same variables?  Could this be a problem related to how the plugin is programmed?  I don't feel I can assume the plugin was written with coordinates in the proper variables.

Thanks

99
Mach4 General Discussion / Re: Probing Question PoundVar 5062 amd 5072
« on: April 30, 2017, 08:25:52 AM »
So I typed incorrectly, yes 5061-5063 and 5071-5073.

I will do a test to see what comes up for G31.1 on a second probe.  If the probing lua module is correctly written then  it looks like it will be machine and absolute positions for whatever probe is being used rather than reserving 5061-5063 for probe1 and 5071-5073 for probe 2.  I guess  the ESS plugin author is responsible for what actually happens.  Therefor it might differ from control to control!

100
Mach4 General Discussion / Probing Question PoundVar 5062 amd 5072
« on: April 29, 2017, 07:14:24 PM »
The G code documentation for Mach4 mill says variable 5062 is loaded with a position during a G31 move and 5072 is the same data for a second probe during a G31.1 move.
However the mcProbing.lua program on lines 683 and 684 returns absolute position and machine position for 5062 and 5092 respectively.  This is also what was listed in a document of variable values.
I will do some testing to see what is true now that I can run multiple probes in my system using ESS controller.  Has anyone else looked into this?

Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 »