punching machine
21 Jan 2011 10:36 #6789
by anpe
Replied by anpe on topic Re:punching machine
Another question
When I write in my hal file the string "setp wcomp.1.max 5.0" - it works ok, but when I try write "net LubeStrike => wcomp.1.max" emc says : wcomp.1.max does'n exist
Where am I wrong?
When I write in my hal file the string "setp wcomp.1.max 5.0" - it works ok, but when I try write "net LubeStrike => wcomp.1.max" emc says : wcomp.1.max does'n exist
Where am I wrong?
Please Log in or Create an account to join the conversation.
21 Jan 2011 11:24 #6790
by BigJohnT
Replied by BigJohnT on topic Re:punching machine
It's kinda hard to guess with just one line of code.
John
John
Please Log in or Create an account to join the conversation.
21 Jan 2011 12:14 #6792
by anpe
Replied by anpe on topic Re:punching machine
I can not post my code now because I'm not near my machine.
If I write "net LubeStrike => oneshot.1.width" it works.
as written in manual wcomp.max and oneshot.width are float both
If I write "net LubeStrike => oneshot.1.width" it works.
as written in manual wcomp.max and oneshot.width are float both
Please Log in or Create an account to join the conversation.
21 Jan 2011 12:18 #6793
by BigJohnT
Replied by BigJohnT on topic Re:punching machine
Open up Show Hal Configuration and view the pin to make sure your spelling is correct.
John
John
Please Log in or Create an account to join the conversation.
21 Jan 2011 14:26 #6797
by anpe
Replied by anpe on topic Re:punching machine
The problem solved by changing wcomp to comp
Please Log in or Create an account to join the conversation.
23 Jan 2011 16:51 #6810
by andypugh
Replied by andypugh on topic Re:punching machine
anpe wrote:
This might be only a partial solution, as the two components do different things.
The underlying problem is that wcomp.N.max is a parameter, not a pin.
A parameter is stored in the internal memory of the component. It can be set by setp, but is not available to other components.
A pin is stored in global shared memory, and its value can be read and/or written by other components. In fact what the "net" command does (I think) is simply arrange for all the components to use the exact same bit of memory to read/write the pin value.
I think that a solution in your case (if you do want to use wcomp) would be to run a "halcmd setp" command in a script, called by a custom M-code.
linuxcnc.org/docs/html/gcode_main.html#sec:M100-to-M199:
The problem solved by changing wcomp to comp
This might be only a partial solution, as the two components do different things.
The underlying problem is that wcomp.N.max is a parameter, not a pin.
A parameter is stored in the internal memory of the component. It can be set by setp, but is not available to other components.
A pin is stored in global shared memory, and its value can be read and/or written by other components. In fact what the "net" command does (I think) is simply arrange for all the components to use the exact same bit of memory to read/write the pin value.
I think that a solution in your case (if you do want to use wcomp) would be to run a "halcmd setp" command in a script, called by a custom M-code.
linuxcnc.org/docs/html/gcode_main.html#sec:M100-to-M199:
Please Log in or Create an account to join the conversation.
10 Feb 2011 06:45 #7102
by anpe
Replied by anpe on topic Re:punching machine
My machine is almost finished and it works.
Thanx to Rick G, BigJohnT, andypugh for your help.
I've uploaded some photos and video at det-sadik.com/info (sorry for quality)
Thanx to Rick G, BigJohnT, andypugh for your help.
I've uploaded some photos and video at det-sadik.com/info (sorry for quality)
Please Log in or Create an account to join the conversation.
10 Feb 2011 11:14 #7107
by Rick G
Replied by Rick G on topic Re:punching machine
Glad to hear you are up and running!
Rick G
Rick G
Please Log in or Create an account to join the conversation.
Time to create page: 0.113 seconds