- Posts: 26
- Thank you received: 0
Feed rate value for AXIS
11 years 3 months ago #60707
by FiliP
Feed rate value for AXIS was created by FiliP
I saw small widget on main screen gmoccapy, where feed rate is calculated and shown.
I want do the same for my AXIS and gladevcp widget, but i cant find anything about how it is done, on the web.
I looked into testing (sim) configuration, but get no luck.
There is no HAL pin with current FEED.
Any hints?
I want do the same for my AXIS and gladevcp widget, but i cant find anything about how it is done, on the web.
I looked into testing (sim) configuration, but get no luck.
There is no HAL pin with current FEED.
Any hints?
Please Log in to join the conversation.
- LearningLinuxCNC
- Offline
- Elite Member
-
Less
More
- Posts: 208
- Thank you received: 0
11 years 3 months ago #60711
by LearningLinuxCNC
Replied by LearningLinuxCNC on topic Feed rate value for AXIS
You can get the velocity of the cutter from the pin
motion.current-vel
This is in machine units per second so you would have to scale it to what you want to see.
motion.current-vel
This is in machine units per second so you would have to scale it to what you want to see.
Please Log in to join the conversation.
11 years 3 months ago #60715
by FiliP
Replied by FiliP on topic Feed rate value for AXIS
Thx, found it , and it works.
My mistake was searching something like "feed".
My mistake was searching something like "feed".
Please Log in to join the conversation.
10 years 7 months ago #71830
by FiliP
Replied by FiliP on topic Feed rate value for AXIS
Hi.
My feed rate slider dont work since i bought XHC HB04. Can anyone help me with this situation? :dry:
We have this:
Before HB04 i was using this:
Now i have this error:
rpanel.hal:14: Pin 'motion.current-vel' was already linked to signal 'pendant:feed-value'
I'v tryed using pendant:feed-value, pendant.feed-value or xhc-hb04.feed-value instead motion.current-vel, but this dont work. I cant get through this...
My feed rate slider dont work since i bought XHC HB04. Can anyone help me with this situation? :dry:
We have this:
Code:
pendant:feed-value
<== motion.current-vel
==> xhc-hb04.feed-value
Before HB04 i was using this:
Code:
loadrt mult2 count=2
addf mult2.0 servo-thread
addf mult2.1 servo-thread
setp mult2.0.in0 60
net ips-in1 mult2.0.in1 <= motion.current-vel
net ipm-out1 gladevcp.hal_feedspeedbarcurrent <= mult2.0.out
setp mult2.1.in0 60
net ips-in2 mult2.1.in1 <= motion.requested-vel
net ipm-out2 gladevcp.hal_feedspeedbarset <= mult2.1.out
Now i have this error:
rpanel.hal:14: Pin 'motion.current-vel' was already linked to signal 'pendant:feed-value'
I'v tryed using pendant:feed-value, pendant.feed-value or xhc-hb04.feed-value instead motion.current-vel, but this dont work. I cant get through this...
Please Log in to join the conversation.
10 years 7 months ago #71869
by andypugh
A pin can't connect to more than one signal.
But, that's OK, just use pendant.feed-value everywhere you want that pin value. In this case
Replied by andypugh on topic Feed rate value for AXIS
FiliP wrote: rpanel.hal:14: Pin 'motion.current-vel' was already linked to signal 'pendant:feed-value'
A pin can't connect to more than one signal.
But, that's OK, just use pendant.feed-value everywhere you want that pin value. In this case
Code:
net pendant.feed-value mult2.0.in1
Please Log in to join the conversation.
10 years 7 months ago #71877
by FiliP
Replied by FiliP on topic Feed rate value for AXIS
andypugh wrote:
FiliP wrote: rpanel.hal:14: Pin 'motion.current-vel' was already linked to signal 'pendant:feed-value'
Yes, i knew it but didnt know how to use this knowlegeandypugh wrote: A pin can't connect to more than one signal.
So i can have one pin to signal, but one signal to many pins... So i must know what is signal, what is pin... Thank you.
It didnt work but this work:andypugh wrote: But, that's OK, just use pendant.feed-value everywhere you want that pin value. In this case
Code:net pendant.feed-value mult2.0.in1Code:net pendant:feed-value mult2.0.in1
Thank you again andypugh
Please Log in to join the conversation.
Time to create page: 0.082 seconds
