Upgraded to 2.7 and now it moves real slow

More
19 Mar 2015 11:42 #57000 by cmorley
can you post ini/hal files of both good and bad configs?

Chris M

Please Log in or Create an account to join the conversation.

More
20 Mar 2015 05:38 - 20 Mar 2015 06:16 #57026 by yoshimitsuspeed
What do you mean by config?
Are you talking about the specific machine config file? Or configs for linuxcnc it's self?
If you are talking about the machine config files I can take my 2.5/2.6 machine configuration and copy it onto 2.7 and I will have this problem. Or I can create a new stepconf in 2.7 and it will do the same thing.
Last edit: 20 Mar 2015 06:16 by yoshimitsuspeed.

Please Log in or Create an account to join the conversation.

More
21 Mar 2015 01:29 #57038 by Todd Zuercher
By config file, he means your .hal and .ini and any and all related files.

Posting this information lets us see exactly what's going on, and may developers an easy way to try to replicate your bug so they can fix it.

Please Log in or Create an account to join the conversation.

More
21 Mar 2015 04:23 #57043 by yoshimitsuspeed
like I said I can copy my old files from 2.5/2.6 or I can create a new config in 2.7 stepconf and either way I get the same behavior so I really don't think it has anything to do with that but here they are. These are my old 2.6 files copied into 2.7.

# Generated by stepconf 1.1 at Wed Mar  4 14:25:37 2015
# If you make changes to this file, they will be
# overwritten when you run stepconf again

[EMC]
MACHINE = XYZ
DEBUG = 0

[DISPLAY]
DISPLAY = axis
EDITOR = gedit
POSITION_OFFSET = RELATIVE
POSITION_FEEDBACK = ACTUAL
ARCDIVISION = 64
GRIDS = 10mm 20mm 50mm 100mm 1in 2in 5in 10in
MAX_FEED_OVERRIDE = 1.2
MIN_SPINDLE_OVERRIDE = 0.5
MAX_SPINDLE_OVERRIDE = 1.2
DEFAULT_LINEAR_VELOCITY = 3.60
MIN_LINEAR_VELOCITY = 0
MAX_LINEAR_VELOCITY = 36.00
INTRO_GRAPHIC = linuxcnc.gif
INTRO_TIME = 5
PROGRAM_PREFIX = /home/cnc/linuxcnc/nc_files
INCREMENTS = 5mm 1mm .5mm .1mm .05mm .01mm .005mm

[FILTER]
PROGRAM_EXTENSION = .png,.gif,.jpg Greyscale Depth Image
PROGRAM_EXTENSION = .py Python Script
png = image-to-gcode
gif = image-to-gcode
jpg = image-to-gcode
py = python

[TASK]
TASK = milltask
CYCLE_TIME = 0.010

[RS274NGC]
PARAMETER_FILE = linuxcnc.var

[EMCMOT]
EMCMOT = motmod
COMM_TIMEOUT = 1.0
COMM_WAIT = 0.010
BASE_PERIOD = 86805
SERVO_PERIOD = 1000000

[HAL]
HALFILE = XYZ.hal
HALFILE = custom.hal
POSTGUI_HALFILE = custom_postgui.hal

[TRAJ]
AXES = 3
COORDINATES = X Y Z
LINEAR_UNITS = mm
ANGULAR_UNITS = degree
CYCLE_TIME = 0.010
DEFAULT_VELOCITY = 3.60
MAX_VELOCITY = 36.00

[EMCIO]
EMCIO = io
CYCLE_TIME = 0.100
TOOL_TABLE = tool.tbl

[AXIS_0]
TYPE = LINEAR
HOME = 0.0
MAX_VELOCITY = 34.2002188814
MAX_ACCELERATION = 200.0
STEPGEN_MAXACCEL = 250.0
SCALE = -320.0
FERROR = 1
MIN_FERROR = .25
MIN_LIMIT = -0.001
MAX_LIMIT = 542.0
HOME_OFFSET = 0.0

[AXIS_1]
TYPE = LINEAR
HOME = 0.0
MAX_VELOCITY = 34.2002188814
MAX_ACCELERATION = 200.0
STEPGEN_MAXACCEL = 250.0
SCALE = -320.0
FERROR = 1
MIN_FERROR = .25
MIN_LIMIT = -0.001
MAX_LIMIT = 280.0
HOME_OFFSET = 0.0

[AXIS_2]
TYPE = LINEAR
HOME = 0.0
MAX_VELOCITY = 34.2002188814
MAX_ACCELERATION = 200.0
STEPGEN_MAXACCEL = 250.0
SCALE = -320.0
FERROR = 1
MIN_FERROR = .25
MIN_LIMIT = -160.0
MAX_LIMIT = 0.001
HOME_OFFSET = 0.0
# Generated by stepconf 1.1 at Wed Mar  4 14:25:37 2015
# If you make changes to this file, they will be
# overwritten when you run stepconf again
loadrt trivkins
loadrt [EMCMOT]EMCMOT base_period_nsec=[EMCMOT]BASE_PERIOD servo_period_nsec=[EMCMOT]SERVO_PERIOD num_joints=[TRAJ]AXES
loadrt hal_parport cfg="0 out"
setp parport.0.reset-time 5000
loadrt stepgen step_type=0,0,0
loadrt pwmgen output_type=1

addf parport.0.read base-thread
addf stepgen.make-pulses base-thread
addf pwmgen.make-pulses base-thread
addf parport.0.write base-thread
addf parport.0.reset base-thread

addf stepgen.capture-position servo-thread
addf motion-command-handler servo-thread
addf motion-controller servo-thread
addf stepgen.update-freq servo-thread
addf pwmgen.update servo-thread

net spindle-cmd-rpm => pwmgen.0.value
net spindle-on <= motion.spindle-on => pwmgen.0.enable
net spindle-pwm <= pwmgen.0.pwm
setp pwmgen.0.pwm-freq 10.0
setp pwmgen.0.scale 190000.0
setp pwmgen.0.offset 0.0947368421053
setp pwmgen.0.dither-pwm true
net spindle-cmd-rpm     <= motion.spindle-speed-out
net spindle-cmd-rpm-abs <= motion.spindle-speed-out-abs
net spindle-cmd-rps     <= motion.spindle-speed-out-rps
net spindle-cmd-rps-abs <= motion.spindle-speed-out-rps-abs
net spindle-at-speed    => motion.spindle-at-speed

net spindle-pwm     => parport.0.pin-01-out
setp parport.0.pin-02-out-invert 1
net xstep           => parport.0.pin-02-out
net xdir            => parport.0.pin-03-out
setp parport.0.pin-04-out-invert 1
net ystep           => parport.0.pin-04-out
setp parport.0.pin-05-out-invert 1
net ydir            => parport.0.pin-05-out
setp parport.0.pin-06-out-invert 1
net zstep           => parport.0.pin-06-out
setp parport.0.pin-07-out-invert 1
net zdir            => parport.0.pin-07-out
setp parport.0.pin-08-out-invert 1
net ystep           => parport.0.pin-08-out
setp parport.0.pin-09-out-invert 1
net ydir            => parport.0.pin-09-out
net estop-ext       <= parport.0.pin-10-in

setp stepgen.0.position-scale [AXIS_0]SCALE
setp stepgen.0.steplen 1
setp stepgen.0.stepspace 0
setp stepgen.0.dirhold 45000
setp stepgen.0.dirsetup 45000
setp stepgen.0.maxaccel [AXIS_0]STEPGEN_MAXACCEL
net xpos-cmd axis.0.motor-pos-cmd => stepgen.0.position-cmd
net xpos-fb stepgen.0.position-fb => axis.0.motor-pos-fb
net xstep <= stepgen.0.step
net xdir <= stepgen.0.dir
net xenable axis.0.amp-enable-out => stepgen.0.enable

setp stepgen.1.position-scale [AXIS_1]SCALE
setp stepgen.1.steplen 1
setp stepgen.1.stepspace 0
setp stepgen.1.dirhold 45000
setp stepgen.1.dirsetup 45000
setp stepgen.1.maxaccel [AXIS_1]STEPGEN_MAXACCEL
net ypos-cmd axis.1.motor-pos-cmd => stepgen.1.position-cmd
net ypos-fb stepgen.1.position-fb => axis.1.motor-pos-fb
net ystep <= stepgen.1.step
net ydir <= stepgen.1.dir
net yenable axis.1.amp-enable-out => stepgen.1.enable

setp stepgen.2.position-scale [AXIS_2]SCALE
setp stepgen.2.steplen 1
setp stepgen.2.stepspace 0
setp stepgen.2.dirhold 45000
setp stepgen.2.dirsetup 45000
setp stepgen.2.maxaccel [AXIS_2]STEPGEN_MAXACCEL
net zpos-cmd axis.2.motor-pos-cmd => stepgen.2.position-cmd
net zpos-fb stepgen.2.position-fb => axis.2.motor-pos-fb
net zstep <= stepgen.2.step
net zdir <= stepgen.2.dir
net zenable axis.2.amp-enable-out => stepgen.2.enable

net estop-out <= iocontrol.0.user-enable-out
net estop-ext => iocontrol.0.emc-enable-in

loadusr -W hal_manualtoolchange
net tool-change iocontrol.0.tool-change => hal_manualtoolchange.change
net tool-changed iocontrol.0.tool-changed <= hal_manualtoolchange.changed
net tool-number iocontrol.0.tool-prep-number => hal_manualtoolchange.number
net tool-prepare-loopback iocontrol.0.tool-prepare => iocontrol.0.tool-prepared

Please Log in or Create an account to join the conversation.

More
21 Mar 2015 19:57 #57066 by andypugh
When you talk about moving from 2.6 to 2.7 do you mean literally just changing the linuxCNC version, or are you changing between OS versions, Ubuntu / Wheezy etc at the same time.
Is this on identical PC hardware?

Please Log in or Create an account to join the conversation.

More
21 Mar 2015 21:58 #57068 by Todd Zuercher
You said that you are trying to set up a "new" pc with 2.7. So it is obviously not the exact same hardware. Did you do latency tests on the new PC? If you are software stepping, and the new pc is not configured properly (or is incapable) of adequate latency for your old config, the results your seeing could possibly be expected. Are you getting a latency alarm? (Linuxcnc only issues the alarm once, further latency excesses are then ignored.)

Please Log in or Create an account to join the conversation.

More
22 Mar 2015 02:44 #57073 by yoshimitsuspeed
I really appreciate you guys making an effort to help me but I do feel like I have covered these questions pretty well already.

I have two computers. I will call the first Old and Slow. This computer has been running my machine since I built it. It was successfully running 2.5 on Ubuntu 10.04 since then. It barely cuts it with Latency tests. It usually stays under 25000 but can jump over 40000 at times.

Then there is the new and fast computer. It tests more around 8000 to 15000. I was having trouble finding a PCI card that worked with linuxcnc but finally got one.

While I was waiting for the new card to come in I got impatient so I upgraded the old and slow computer from 2.5 to to 2.6 and then 2.7.
2.6 worked fine but 2.7 had this speed issue. I tried to revert to 2.6 but something went wrong and it got buggered up. I decided I would rather upgrade to 12.04 than fix it so I did and installed 2.6.
Now the old and slow machine is working properly with 12.04 and 2.6.

Once the new PCI card came in I installed 12.04 on the new and fast computer. I tested it on 2.6 and everything worked perfectly and then I upgraded to 2.7. On 2.7 the new and fast computer has the exact same behavior as the old and slow computer did on 2.7.

I have tested it with the old config files that were setup and worked in 2.5 and 2.6 and I have created a new stepconf config in 2.7. Both have the same behavior.
Under roughly 900 mm/m it goes fine. Much over that and the machine moves much slower than the DRO thinks it is.

Please Log in or Create an account to join the conversation.

More
22 Mar 2015 03:44 #57074 by andypugh

Much over that and the machine moves much slower than the DRO thinks it is.


If LinuxCNC didn't _think_ it was making the steps then it would trigger a following error.

I wonder if you are marginal on step length. Perhaps the new computer is so much faster that the reset time is actually being met and it wasn't before.
As an experiment try increasing the step length by 50% and see what happens.

Please Log in or Create an account to join the conversation.

More
22 Mar 2015 03:54 #57075 by yoshimitsuspeed

Much over that and the machine moves much slower than the DRO thinks it is.


If LinuxCNC didn't _think_ it was making the steps then it would trigger a following error.

I wonder if you are marginal on step length. Perhaps the new computer is so much faster that the reset time is actually being met and it wasn't before.
As an experiment try increasing the step length by 50% and see what happens.


Like I said though the behavior is the same on the old computer and the new computer. Both work great with 2.6 and both have this issue with 2.7. Is there something different with 2.7 that would make it behave differently in regards to step length?

Where do I change step length?

Please Log in or Create an account to join the conversation.

More
22 Mar 2015 05:17 - 22 Mar 2015 05:29 #57076 by PCW
Changing the reset time from 5000 to 7500 will increase the step time by 50 %

edit
When the uspace branch was added the parallel port I/O code was optimized
so depending on 2.6 version that might make timing very slightly different between 2.7 and 2.6.

If your parallel port timing was marginal for your step drives and so they were depending on
slow I/O operations (making the timings longer than specified) this could possibly account
for the difference.
Last edit: 22 Mar 2015 05:29 by PCW.

Please Log in or Create an account to join the conversation.

Time to create page: 0.095 seconds
Powered by Kunena Forum