Advanced Search

What error does LinuxCNC show?

What GUI?
Does the machine have tandem axis/joints?

I have soft limits on my axis and absolute encoders. If I power off the machine when I am on the limit (max or min), the machine may move by a 10th (0.0001) or so, once the servos release on power off.  This will cause the machine to "move beyond" the soft limit, even if just 0.0001.  Once this occurs, I can't jog the axis at all.  I have to edit the limits in the ini, jog and reset the limits back. 

I would expect you can jog toward the soft limit and beyond to get back into the limits.  How can I jog into the limits is I am just slightly over (but over)

You need to set large min-ferror and ferror limits (an inch / 25mm or so) so you can see
the motor behavior (you have about a 50% chance of the wrong feedback direction and
runaway so of course this needs to be addressed first.)

Also make sure you have working drive enables or motors disconnected from linear axis
as a runaway linear axis can be dangerous/destructive.
 

I am trying to upgrade linuxcnc to 2.9.3 I was running 2.7.x I am using all the same hardware but when the parallel port tries to load it gets the I/O ports at e000 [disabled] error. On the old version is was running a port 0xe000 and irq 3


cat /proc/interrupts
          CPU0       CPU1       CPU2       CPU3       
  0:          9          0          0          0   IO-APIC   2-edge      timer
  1:          0          0          0          4   IO-APIC   1-edge      i8042
  3:          0          0          0          0   IO-APIC   3-edge      parport0
  8:          1          0          0          0   IO-APIC   8-edge      rtc0

sudo modinfo parport_pc
filename:       /lib/modules/6.1.0-23-rt-amd64/kernel/drivers/parport/parport_pc.ko
license:        GPL
description:    PC-style parallel port driver

sudo dmesg | grep par

[    8.549490] ppdev: user-space parallel port driver
[    8.761564] parport_pc: unknown parameter 'auto' ignored
[    8.761730] parport 0xe000 (WARNING): CTR: wrote 0x0c, read 0xff
[    8.761736] parport 0xe000 (WARNING): DATA: wrote 0xaa, read 0xff
[    8.761736] parport 0xe000: You gave this address, but there is probably no parallel port there!
[    8.761750] parport0: PC-style at 0xe000, irq 3 [PCSPP,TRISTATE]
[    8.860174] lp0: using parport0 (interrupt-driven).

lspci -vv
05:00.0 Parallel controller: Nanjing Qinheng Microelectronics Co., Ltd. CH351 PCIe Parallel Port Adapter (rev 0f) (prog-if 01 [BiDir])
    Subsystem: Nanjing Qinheng Microelectronics Co., Ltd. CH351 PCIe Parallel Port Adapter
    Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
    Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
    Interrupt: pin A routed to IRQ 3
    Region 0: I/O ports at e010 [disabled]
    Region 1: I/O ports at e000 [disabled]




 

I'm going to check into the belt tension. I know too tight howls, but too loose?

Is this a lot?

Yes that`s what I did - this was the solution: to add a cia402.2.read-all and one cia402.2.write-all for the third servo as well.

Sounds like the drive has a significant offset or there is some electrical issue
What RPM do you get from the drive at 0V?

I is not for tuning overshoot but to have a slow but unlimited feedback

You can try more I term ( until it oscillates then back off to say 25% ) but I think the
real problem is the offset.

(the P term by itself cannot bring the error to 0 because the P term needs
and error to have any effect)

All this to say, it sounds like there is an electrical issue or perhaps drive
parameter setup issue that needs to be addressed rather than patched
over in LinuxCNC.

 

Also are the drives enabled?

Typically servo drives would have an enable input that must be connected to operate
(with default setup parameters)

Note that if LinuxCNC cannot communicate with the 7I76EU, LinuxCNC will not start.

I've been trying to understand why the system isn't pulling the revs down to 300, but seems ok above, so played with the ini file OUTPUT_SCALE
ini           5000      4500    3600
s.rpm                 Actual
300          450         480      490
500          600         630      700    
1000      1000       1050    1200
2000      1800       1900    2300
3000      2700       2800    3300
To me the control isn't controlling. I think it looks like P needs to be bigger, but if I raise it enough to have an effect, I get significant oscillations.
My understanding was I should raise P until it just oscillates, and then back off a little to be safe,  and lastly tune for overshoot with I. But with this method is not working for me. Is there another method please?

dunnitagain wrote:

Great ! i have to figure out how to load the error files to a USB Stick .
 

It's not ideal, but we can work with photos of the error log on the screen. 

Is there any documentation available on setting up absolute encoders with Linux CNC?

I had to set my machine to a certain state, when a new gcode file is loaded, also reset saved last motion.program.line. I did  not find any example, suiting the requirements, so did it my own way. This pythoncode is creating a number from the current loaded filename. Unique enough for me.

e.g. 'rectangle_inside_helix_stepdown_no_stepover.ngc' returns  3724037, or 'HalfBallConc.ngc' returns 142356. A 'pin in s32' can handle those numbers

easy to make a comparaison oldfile/newfile and take action.

 

One option is to add a simple RS-422 driver/receiver (like a SP491) connected to the parallel expansion port

Also if you have a free stepgen and a free encoder input that gives you a RS-422 interface.