- Posts: 1931
- Thank you received: 394
Gmoccapy - A new screen for linuxcnc
- newbynobi
- Offline
- Moderator
-
Less
More
13 years 5 months ago #34771
by newbynobi
Replied by newbynobi on topic Gmoccapy - A new screen for linuxcnc
Jorge,
did you enter exactly the code I mentioned?
If so, the machine should need more than 2 minutes to finish the move, but you will see it uses not even 30 seconds!
I believe you are mixing two things!
MAX Vel has nothing to do with the bug I mentioned.
Please explain with label is not showing the correct value?
Please add your INI File and your hidden preference file.
Norbert
did you enter exactly the code I mentioned?
If so, the machine should need more than 2 minutes to finish the move, but you will see it uses not even 30 seconds!
I believe you are mixing two things!
MAX Vel has nothing to do with the bug I mentioned.
Please explain with label is not showing the correct value?
Please add your INI File and your hidden preference file.
Norbert
- jlviloria
- Offline
- Elite Member
-
Less
More
- Posts: 161
- Thank you received: 9
13 years 5 months ago - 13 years 5 months ago #34774
by jlviloria
Replied by jlviloria on topic Gmoccapy - A new screen for linuxcnc
Norbert
None label shows the actual feed. show erroneous values.
The machine when running command G95, an alarm went out, I got to comment on these two lines and work.
def on_scl_feed_value_changed(self, widget, data=None):
feed_override = self.widgets.scl_feed.get_value() / 100
#real_feed = round(int(self.widgets.active_feed_label.get_text()) * feed_override)
#self.widgets.lbl_feed_act.set_text("F %d" %real_feed)
self.emc.feed_override(feed_override)
lbl_feed_act = disabled
lbl_current_vel = erroneous
but the machine moves well, at least as axis or industrial
I have my record the machining times have not changed.
attached my files.
Image Check the "tiempo ciclo" you see that just goes for 5 and takes more than 2 minutes
None label shows the actual feed. show erroneous values.
The machine when running command G95, an alarm went out, I got to comment on these two lines and work.
def on_scl_feed_value_changed(self, widget, data=None):
feed_override = self.widgets.scl_feed.get_value() / 100
#real_feed = round(int(self.widgets.active_feed_label.get_text()) * feed_override)
#self.widgets.lbl_feed_act.set_text("F %d" %real_feed)
self.emc.feed_override(feed_override)
lbl_feed_act = disabled
lbl_current_vel = erroneous
but the machine moves well, at least as axis or industrial
I have my record the machining times have not changed.
attached my files.
Image Check the "tiempo ciclo" you see that just goes for 5 and takes more than 2 minutes
Last edit: 13 years 5 months ago by jlviloria.
- newbynobi
- Offline
- Moderator
-
Less
More
- Posts: 1931
- Thank you received: 394
13 years 5 months ago #34782
by newbynobi
Replied by newbynobi on topic Gmoccapy - A new screen for linuxcnc
Jorge,
with the values you entered the cycle time must be about 10 minutes, but your cycle time is only 2 min 53 so IMHO the G95 cycle is not working correct.
By the way, I like the cycle time frame, can you mail me the corresponding code?
An about the max Vel , I could not find any error in your config, so if you jog both axis at ones with G0 the actual speed label should indicate something around 10000 mm/min and not only 6000.
I will check tomorow my code, may be I limited the values in some code snipped.
Norbert
with the values you entered the cycle time must be about 10 minutes, but your cycle time is only 2 min 53 so IMHO the G95 cycle is not working correct.
By the way, I like the cycle time frame, can you mail me the corresponding code?
An about the max Vel , I could not find any error in your config, so if you jog both axis at ones with G0 the actual speed label should indicate something around 10000 mm/min and not only 6000.
I will check tomorow my code, may be I limited the values in some code snipped.
Norbert
- jlviloria
- Offline
- Elite Member
-
Less
More
- Posts: 161
- Thank you received: 9
13 years 5 months ago - 13 years 5 months ago #34784
by jlviloria
Replied by jlviloria on topic Gmoccapy - A new screen for linuxcnc
as I mention, I always had "cycle time" and values not changed, I come from AXIS.
total time of 5:14 minutes.
cycle time is not a widgets is an component HAL :
linuxcnc.org/docs/2.5/html/man/man9/time.9.html
For me it is a problem of how to display the feed. as if he had the wrong scale. An error of those scales is reflected in the finished
Jorge Viloria
total time of 5:14 minutes.
cycle time is not a widgets is an component HAL :
linuxcnc.org/docs/2.5/html/man/man9/time.9.html
For me it is a problem of how to display the feed. as if he had the wrong scale. An error of those scales is reflected in the finished
Jorge Viloria
Last edit: 13 years 5 months ago by jlviloria.
- newbynobi
- Offline
- Moderator
-
Less
More
- Posts: 1931
- Thank you received: 394
13 years 5 months ago #34813
by newbynobi
Replied by newbynobi on topic Gmoccapy - A new screen for linuxcnc
@Jorge,
unfortunately I can not follow you.
On my machine speeds are shown as they should, but G 95 has a problem.
Norbert
unfortunately I can not follow you.
On my machine speeds are shown as they should, but G 95 has a problem.
Norbert
- newbynobi
- Offline
- Moderator
-
Less
More
- Posts: 1931
- Thank you received: 394
13 years 5 months ago #34814
by newbynobi
Replied by newbynobi on topic Gmoccapy - A new screen for linuxcnc
gmoccapy - ver. 0.9.3.1 has been pushed
- Changed the required screen size to fit on 979 x 750
- A message window will warn the user in case he try to use G95
Norbert
- Changed the required screen size to fit on 979 x 750
- A message window will warn the user in case he try to use G95
Norbert
Moderators: newbynobi, HansU
Time to create page: 6.768 seconds