Advanced Search

I just realize I didn’t quote the original question so of course my question didn’t make sense. It is about this realtime error. I installed ethtools and the error disappeared. After upgrading from LinuxCNC 2.8 to 2.9.3 the error came back.

 

 

Sorry, yes, you are right.
Though it is mainly intended for MPGs so that the machine doesn't shake to bits responding to each MPG pulse individually

What was limiting the accel previously? I am not sure what has changed to affect this. Is the behaviour the same for both joint and axis jogging (ie, before and after homing)

No, sadly not.
I looked into the possibility of making the Mesa UART appear in /dev/ but gave up and wrote the mesa_modbus framework instead.

The Huang Yang VFDs don't use "real" modbus, though it might be close enough to be able to get the mesa_modbus thing to work.

It might be easier just to use a USB dongle. It's not realtime, but for milling machines that isn't necessarily a problem. For a lathe realtime ought to be better for CSS.

I run my high-speed spindle using one of these (with the aligators snipped off) www.amazon.co.uk/gp/product/B082KKG55T

All the lines that mention jogging are commented out in the provided HAL file (but don't look to be enough)

What type of jogging are you trying to use? The HAL mentions a joystick.

I have a probe and tool setter and have set up my M6 remap according to  forum.linuxcnc.org/forum/10-advanced-con...h-off?start=30#48235.

Is it possible to get rid of the indicated travel moves to tool change and tool setter positions in the path preview window? As well as the strange indicated travel to 0;0, during operation the spindle is not moving to this position.

The indicated moves messes with the work envelope, making setup harder. Also pressing the "Z" button in qtdragon now zooms out to like the whole machine, instead of the actual work envelope. 

If anyone is interested, here is my config:  github.com/hmunktell/printNC/tree/probe

List of tools can be helpful before run the program:
 

Place for it:
 

Wheezy is older, hence better for older PC's, and uses the RTAI kernel that has better latency on older PC so you get more speed from the machine.
Download the ISO, boot from the USb, see if it works for you, usually takes 20-30 minutes total.

Hi Andy,

accel-fraction is intended to be used for external_offsets

Does it? Isn't the eoffset movement acceleration controlled by ini setting for each respective axis with OFFSET_AV_RATIO?
I thought that accel-fraction is used for limiting jog acceleration only. 

axis.L.jog-accel-fraction IN FLOATSets acceleration for wheel jogging to a fraction of the INI max_acceleration for the axis. Values greater than 1 or less than zero are ignored.

I don't want to limit velocity but acceleration. My servo motors are powerful and go to max velocity instantly because acceleration is not limited. Limiting the acceleration during keyboard jogs will limit jerk and rapid grow of jog movement speed. 
I think there should be a user friendly way of limiting acceleration for keyboard jogs.
 

What error?

If it is real modbus (The HuangYang ones are not, which is why they have a dedicated driver) then you should be able to run it with one of the generic-modbus components, or from Classic Ladder.

linuxcnc.org/docs/stable/html/drivers/mb2hal.html
linuxcnc.org/docs/stable/html/ladder/ladder-intro.html (there are more detailed sections, look on the main LinuxCNC docs page)
And if you are running the development version of LinuxCNC: linuxcnc.org/docs/devel/html/drivers/mesa_modbus.html

The builder in question was out of disk space. This has been fixed.

This sounds like the machine is not in "Manual" mode when you start up. (which is a bit odd, actually)

You shouldn't have to do anything in the MDI window, just switching to MDI and back should but you in MANUAL. But you shouldn't need to do anything anyway of it's the "manual" tab at the front in Axis.

It might be instructive to monitor halui.mode.is_manual.

I have looked through your HAL files and haven't spotted where the pushbuttons connect to the axis/joint jog pins. Maybe these are connected in your postgui.hal?

accel-fraction is intended to be used for external_offsets. If you are not using those then I don't think you should set a value to that.

The Axis GUI has a jog-speed slider. You should be able to limit jog speed there? (But I think that rapid shift-jog probably still goes at full speed)

It looks like you should be able to set a MAX_LINEAR_VELOCITY in the [DISPLAY] section that will limit max jog speed.

github.com/LinuxCNC/linuxcnc/blob/master...cripts/axis.py#L3443

(This should not affect the overall machine max speed which is [TRAJ]MAX_LINEAR_VELOCITY

So I upgraded to linuxcnc 2.9 and the error message is back? What can cause this?

USB devices in general do not work with LinuxCNC for motion control as they do
not support real time communications.

The most basic starting system is probably a PC with a parallel port (and perhaps a simple
breakout board like the common "Mach3 5 Axis CNC" breakout)

Nest step would probably be an LinuxCNC specific Ethernet connected card or EtherCAT