Help needed to get my 7i76E + 7i85S + 7i73 on my mill going.

More
28 Aug 2017 18:17 #98102 by tecno

If the scale is correct, are your maximum velocities reasonable?

Have you read the LInuxCNC ini file documentation?


I have tried to read but not so clear for a bloody foreigner ;)

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

More
28 Aug 2017 18:43 #98105 by Todd Zuercher
The last ini file of yours I looked up had values much higher for max vel (250 for max_velocity, and 350 for stepgen_max_vel on the slowest axis and others were even higher)
You would need either slower max velocities or shorter step timings, or a combination of both.

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

More
28 Aug 2017 19:13 #98107 by Todd Zuercher
To meet your ini file's stepgen max velocity value you had for X of 350 (800 for Y-Z), the sum of the step length and step space values would have to be less than about 700ns (300ns).

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

More
29 Aug 2017 10:16 #98134 by tecno
Guys, first of all I have been way out with my numbers (mixed up with previous router I had) so my apologies.

1. Drivers where not set correctly = now they are in quad and work OK, well a bit too fast.

Still having the error message so I will be tweaking my numbers.

Original speeds with the Siemens system and DC servos was
Fast transport X/Y 5000mm/min = 83mm/s and 2500mm/min = 41mm/s for Z

Will report when have error cleared out.

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

More
29 Aug 2017 10:26 - 29 Aug 2017 10:39 #98135 by tecno
So now no error messages.

Q:
Where do I set max velocity = keyboard jogging + shift key >>>>>>> WAY TOO FAST

File Attachment:

File Name: combimill_...8-29.ini
File Size:5 KB
Attachments:
Last edit: 29 Aug 2017 10:39 by tecno.

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

More
29 Aug 2017 11:32 - 29 Aug 2017 11:33 #98137 by andypugh
Jogging velocities are generated by the GUI, so:
[DISPLAY]DEFAULT_LINEAR_VELOCITY
linuxcnc.org/docs/2.7/html/config/ini-co...tml#_display_section

But, you are holding the shift-key, and I think that means "jog at full rapid rate"
Last edit: 29 Aug 2017 11:33 by andypugh.

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

More
29 Aug 2017 11:42 #98138 by tecno
Questions embedded below

[DISPLAY]
DISPLAY = axis
POSITION_OFFSET = RELATIVE
POSITION_FEEDBACK = ACTUAL
MAX_FEED_OVERRIDE = 2.000000
MAX_SPINDLE_OVERRIDE = 1.000000
MIN_SPINDLE_OVERRIDE = 0.500000
INTRO_GRAPHIC = linuxcnc.gif
INTRO_TIME = 5
PROGRAM_PREFIX = /home/bengt/linuxcnc/nc_files
INCREMENTS = 5mm 1mm .5mm .1mm .05mm .01mm .005mm
POSITION_FEEDBACK = ACTUAL
DEFAULT_LINEAR_VELOCITY = 6.000000 >>>>>>>>>>>>>>>> Is this the speed for ARROW KEY? with no Shift?
MAX_LINEAR_VELOCITY = 25.000000
MIN_LINEAR_VELOCITY = 0.500000
DEFAULT_ANGULAR_VELOCITY = 12.000000
MAX_ANGULAR_VELOCITY = 180.000000
MIN_ANGULAR_VELOCITY = 1.666667
EDITOR = gedit
GEOMETRY = xyz

#********************
# Axis X
#********************
[AXIS_0]
TYPE = LINEAR
HOME = 0.0
FERROR = 10.0
MIN_FERROR = 1.0
MAX_VELOCITY = 85>>>>>>>>>>>>>>>>>>>>>>>> And this is what I get when Shift + Arrow Key?
MAX_ACCELERATION = 100
# The values below should be 25% larger than MAX_VELOCITY and MAX_ACCELERATION
# If using BACKLASH compensation STEPGEN_MAXACCEL should be 100% larger.
STEPGEN_MAXVEL = 110
STEPGEN_MAXACCEL = 200

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

More
29 Aug 2017 11:59 #98139 by andypugh
I _think_ that DEFAULT_LINEAR_VELOCITY is what you get with an unshifted arrow and the jog-speed slider at 100%
(And, yes, I think that shifted-arrow will use the 85mm/sec.)

It should be a fairly easy test to check it against the DRO numbers.
The following user(s) said Thank You: tecno

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

More
29 Aug 2017 12:14 #98140 by tecno

Question

I have a manual switch on my frontpanel and want to be able to run flood coolant manually.

Following in my hal file
# ---coolant signals---
net coolant-mist <= iocontrol.0.coolant-mist
net coolant-flood <= iocontrol.0.coolant-flood

# --- DIN-01 Coolant pump ---
net din-01 <= hm2_7i76e.0.7i73.0.1.input-20

# --- COOLANT-FLOOD ---
net coolant-flood hm2_7i76e.0.7i76.0.0.output-04
net din-01 hm2_7i76e.0.7i76.0.0.output-04

Is this the correct way to net functions wanted?


As I get no positive results testing above i wonder how this must be done.

Have 2 swithes I need to get working on my front panel.
1. Coolant Flood
2. Oiler pump

1 already has net to output, but I need to do this manually also = How to do this.
2. input on 7i73 > output on 7i76e but I also need to have this to be run via G-code (just for test = coolant-mist)

Is above to be done with some OR ?

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

More
29 Aug 2017 12:51 #98141 by rodw
Thats becasue nothing is connected anywhere. I think you need
# ---coolant signals---
net coolant-mist  <= hm2_7i76e.0.7i73.0.1.input-20
net coolant-mist => iocontrol.0.coolant-mist

so now the input is connected to the iocontrol signal. YOu had just created signals before and done nothing with them.

Never used coolant so I am not sure if this is perfect. I'm not sure if iocontrol.0.coolant-mist is an input for a switch or an output for a LED indicator.

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

Moderators: cmorley
Time to create page: 0.196 seconds
Powered by Kunena Forum