Advanced Search

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.