SPINBOX DATA to G-Code Variable
31 Jan 2015 12:08 #55498
by Askjerry
SPINBOX DATA to G-Code Variable was created by Askjerry
Ok... it isn't like I haven't been reading the forum, Google, etc. In fact it's been two days... and I'm no closer to getting a resolve.
So here is the deal... I create a SPINBOX on my panel... I call it spinbox-01 and I have a button under it which calls routine_01.
The routine is pretty simple... just a test program because Once I get the concept... I'll be able to continue...
So here is the test routine...
O <routine_01> sub
(MSG, Routine 01)
#1 = 2
G1 X #1 F20
G0 X0
O<routine_01> endsub
M2
Not much too it... it moves the spindle 2 inches then back... whoo.
What I WANT to do... is dial the SPINBOX to some number from 1 to 5 inches... click the button and have it run the routine with the data passed along... this is NOT the way to do it... but it will give you the idea of what I am TRYING to implement...
O <routine_01> sub
(MSG, Routine 01)
#1 = pyvcp.spinbox-01
G1 X #1 F20
G0 X0
O<routine_01> endsub
M2
I probably have to use net to point the pyvcp.spinbox-01 at some variable and call it... I know i can create custom variables like #<_spinbox01> in G-Code... so it may be something like... an edit to a .hal file to include something like...
net spinner01 #<_hal[pyvcp.spinbox-01]> <= pyvcp.spinbox-01
or that may not even be remotely close.
Can someone help?
If I can connect the pyvcp.spinbox-01 to the G-Code variable in this example... I should be able to then make something more complex and pass variables to it. Like... a peck drill cycle where you enter the depth, the peck distance, and click "DRILL"... that would be useful.
Anyway... I'll keep hacking at it... perhaps I'll get lucky...
Thanks in advance.
Jerry
So here is the deal... I create a SPINBOX on my panel... I call it spinbox-01 and I have a button under it which calls routine_01.
The routine is pretty simple... just a test program because Once I get the concept... I'll be able to continue...
So here is the test routine...
O <routine_01> sub
(MSG, Routine 01)
#1 = 2
G1 X #1 F20
G0 X0
O<routine_01> endsub
M2
Not much too it... it moves the spindle 2 inches then back... whoo.
What I WANT to do... is dial the SPINBOX to some number from 1 to 5 inches... click the button and have it run the routine with the data passed along... this is NOT the way to do it... but it will give you the idea of what I am TRYING to implement...
O <routine_01> sub
(MSG, Routine 01)
#1 = pyvcp.spinbox-01
G1 X #1 F20
G0 X0
O<routine_01> endsub
M2
I probably have to use net to point the pyvcp.spinbox-01 at some variable and call it... I know i can create custom variables like #<_spinbox01> in G-Code... so it may be something like... an edit to a .hal file to include something like...
net spinner01 #<_hal[pyvcp.spinbox-01]> <= pyvcp.spinbox-01
or that may not even be remotely close.
Can someone help?
If I can connect the pyvcp.spinbox-01 to the G-Code variable in this example... I should be able to then make something more complex and pass variables to it. Like... a peck drill cycle where you enter the depth, the peck distance, and click "DRILL"... that would be useful.
Anyway... I'll keep hacking at it... perhaps I'll get lucky...
Thanks in advance.
Jerry
Please Log in or Create an account to join the conversation.
01 Feb 2015 18:22 - 01 Feb 2015 20:52 #55546
by ArcEye
Replied by ArcEye on topic SPINBOX DATA to G-Code Variable
Hi
It is quite simple honest.
I created a xml panel with 2 spinboxes
Then I put it in the ini file
and also the line to enable hal pin examination.
The BIG thing is to ensure your version supports this, I am using a RIP of 2.7 for this demo
The spinboxes are not 'netted' to anything, there is no need, their value can be interogated directly in gcode
Then I started the sim and set HAL Configuration to monitor 2 existing params which had a value and the 2 spinboxes
Then I use the (DEBUG, ........) statements in the MDI window to show the value of the 2 parameters and the 2 spinboxes
voila
regards
It is quite simple honest.
I created a xml panel with 2 spinboxes
<?xml version='1.0' encoding='UTF-8'?>
<pyvcp>
<vbox>
<spinbox>
<halpin>"spinbox0"</halpin>
<min_>-12</min_>
<max_>33</max_>
<initval>10</initval>
<resolution>0.1</resolution>
<format>"2.3f"</format>
<font>("Arial",16)</font>
<param_pin>1</param_pin>
</spinbox>
<spinbox>
<halpin>"spinbox1"</halpin>
<min_>-12</min_>
<max_>33</max_>
<initval>20</initval>
<resolution>0.1</resolution>
<format>"2.3f"</format>
<font>("Arial",16)</font>
<param_pin>1</param_pin>
</spinbox>
</vbox>
</pyvcp>Then I put it in the ini file
[DISPLAY]
PYVCP = custompanel.xmland also the line to enable hal pin examination.
The BIG thing is to ensure your version supports this, I am using a RIP of 2.7 for this demo
[RS274NGC]
FEATURES = 12The spinboxes are not 'netted' to anything, there is no need, their value can be interogated directly in gcode
Then I started the sim and set HAL Configuration to monitor 2 existing params which had a value and the 2 spinboxes
Then I use the (DEBUG, ........) statements in the MDI window to show the value of the 2 parameters and the 2 spinboxes
voila
regards
Please Log in or Create an account to join the conversation.
02 Feb 2015 01:14 - 02 Feb 2015 01:15 #55558
by Askjerry
THAT GOT IT!!
I did the update as you suggested AXIS 2.6.5 and now it works perfectly.
I also tried a DIAL... same thing... works exactly as planned.
You have NO IDEA how crazy I was going yesterday... I was like, "But this SHOULD work!!!" Drove my poor wife crazy too... better take her out for lunch today...
Thank you SO much!
Jerry
Replied by Askjerry on topic SPINBOX DATA to G-Code Variable
THAT GOT IT!!
I did the update as you suggested AXIS 2.6.5 and now it works perfectly.
I also tried a DIAL... same thing... works exactly as planned.
You have NO IDEA how crazy I was going yesterday... I was like, "But this SHOULD work!!!" Drove my poor wife crazy too... better take her out for lunch today...
Thank you SO much!
Jerry
Please Log in or Create an account to join the conversation.
03 Feb 2015 22:34 - 03 Feb 2015 22:42 #55649
by Askjerry
Replied by Askjerry on topic SPINBOX DATA to G-Code Variable
I decided to try my first routine... I do quite a bit of Peck Drilling, G83. So I thought it might be nice to move the machine into position, then conversationally drill a hole... without needing to write G-Code each time. At first it wasn't working right... then I used your idea of running the HAL Configuration... it needed to have a "-f" appended to the HAL pin.
So here is the code...
And here is the interface I came up with...
Likely I'll modify it more... but it is working well. The pyVCP components are in a TABLE to get the format I have now... I may change the sliders to dials... not sure... still experimenting.
Thanks again ArcEye!
Jerry
So here is the code...
(G83 Peck Drilling Routine)
O <peck-drill-rtn> SUB
(MSG, PECK DRILLING)
G90
G20
M3
G83 Z #<_hal[pyvcp.peck-z-f]> R #<_hal[pyvcp.peck-r-f]> Q #<_hal[pyvcp.peck-q-f]> F 3
M5
(MSG, Completed OK.)
O <peck-drill-rtn> ENDSUBAnd here is the interface I came up with...
Likely I'll modify it more... but it is working well. The pyVCP components are in a TABLE to get the format I have now... I may change the sliders to dials... not sure... still experimenting.
Thanks again ArcEye!
Jerry
Please Log in or Create an account to join the conversation.
Time to create page: 0.202 seconds