- Posts: 2203
- Thank you received: 486
Jog speed is very slow
10 years 7 months ago #72323
by Amedee
Thank you!
I scratched my head the whole evening yesterday with that -- beyond the speed it now sets the FERROR accordingly.
The 'Imperial FERROR' was generating strange moves in pncconf (axis going backwards after a jog move) and also gave 'Joint 0 following error' while homing in LinuxCNC.
I pulled the latest version this morning and it now works as expected.
Note that there is a typo in the comments , it should be 360, not 380
Also, as I was wondering why the maximum values in the UI didn't change proportionally, I realized they where hard-coded in screen.glade, and by cranking up the values for the metric folks, we get very big ranges in the imperial system.
Shouldn't we set the range dynamically based on the system chosen? -- something like:
(Also instead of maintaining 2 sets of values imperial/metric, we could just extrapolate the metric ones from imperial)
Replied by Amedee on topic Jog speed is very slow
cmorley wrote: well I pushed fixes to pncconf to set more reasonable defaults for metric and angular jogs.
will be included in 2.7.5
Thank you!
I scratched my head the whole evening yesterday with that -- beyond the speed it now sets the FERROR accordingly.
The 'Imperial FERROR' was generating strange moves in pncconf (axis going backwards after a jog move) and also gave 'Joint 0 following error' while homing in LinuxCNC.
I pulled the latest version this morning and it now works as expected.
Note that there is a typo in the comments , it should be 360, not 380
Also, as I was wondering why the maximum values in the UI didn't change proportionally, I realized they where hard-coded in screen.glade, and by cranking up the values for the metric folks, we get very big ranges in the imperial system.
Shouldn't we set the range dynamically based on the system chosen? -- something like:
Code:
--- bin/pncconf.orig 2016-03-29 10:43:24.506867501 +0200
+++ bin/pncconf 2016-03-29 13:21:50.975355007 +0200
@@ -797,6 +797,7 @@
if units: # imperial
# set GUI defaults
self.max_linear_velocity = 1 # 60 inches per min
+ self.max_linear_velocity_range = (0, 100)
self.default_linear_velocity = .25 # 15 inches per min
self.min_linear_velocity = .01667
@@ -818,7 +819,8 @@
else: # metric
# set gui defaults
self.max_linear_velocity = 25 # 1500 mm per min
- self.default_linear_velocity = 6 # 380 mm per min
+ self.max_linear_velocity_range = (0, 2500)
+ self.default_linear_velocity = 6 # 360 mm per min
self.min_linear_velocity = .5
# axes defaults
--- lib/python/pncconf/pages.py.orig 2016-03-29 12:16:23.136734626 +0200
+++ lib/python/pncconf/pages.py 2016-03-29 13:25:24.296673195 +0200
@@ -408,6 +408,7 @@
self.w.max_spindle_override.set_value( self.d.max_spindle_override*100)
self.w.min_spindle_override.set_value( self.d.min_spindle_override*100)
self.w.max_linear_velocity.set_value( self.d.max_linear_velocity*60)
+ self.w.max_linear_velocity.set_range(self.d.max_linear_velocity_range[0],self.d.max_linear_velocity_range[1])
self.w.min_linear_velocity.set_value( self.d.min_linear_velocity*60)
self.w.default_angular_velocity.set_value( self.d.default_angular_velocity*60)
self.w.max_angular_velocity.set_value( self.d.max_angular_velocity*60)
(Also instead of maintaining 2 sets of values imperial/metric, we could just extrapolate the metric ones from imperial)
Please Log in or Create an account to join the conversation.
Moderators: cmorley
Time to create page: 0.265 seconds