Advanced Search

github.com/geerlingguy/raspberry-pi-pcie-devices/issues/54

Not sure if this helps?

cnc@raspberrypi:~$ sudo lspci -v
0000:00:00.0 PCI bridge: Broadcom Inc. and subsidiaries BCM2712 PCIe Bridge (rev 21) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0, IRQ 39
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
Memory behind bridge: 80000000-800fffff [size=1M] [32-bit]
Prefetchable memory behind bridge: [disabled] [64-bit]
Capabilities: [48] Power Management version 3
Capabilities: [ac] Express Root Port (Slot-), MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [160] Virtual Channel
Capabilities: [180] Vendor Specific Information: ID=0000 Rev=0 Len=028 <?>
Capabilities: [240] L1 PM Substates
Capabilities: [300] Secondary PCI Express
Kernel driver in use: pcieport

0000:01:00.0 Parallel controller: MosChip Semiconductor Technology Ltd. MCS9900 Multi-I/O Controller (prog-if 03 [IEEE1284])
Subsystem: Asix Electronics Corporation (Wrong ID) MCS9900 Multi-I/O Controller
Flags: fast devsel
Memory at 1b80000000 (32-bit, non-prefetchable) [disabled] [size=4K]
Memory at 1b80001000 (32-bit, non-prefetchable) [disabled] [size=4K]
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: [78] Power Management version 3
Capabilities: [80] Express Legacy Endpoint, MSI 00
Capabilities: [100] Virtual Channel
Capabilities: [800] Advanced Error Reporting

0001:00:00.0 PCI bridge: Broadcom Inc. and subsi

I've been gone from LinuxCNC for about 10 yrs. Thought I'd give a try again. And with that I have been working with pi5 GPIOs work fine but thought I might attempt a waveshare pcie adapter and that to the MosChip parallel port card which works in my old PC to run my plasma table.
Where I am at is, LinuxCNC recognizes the MosChip card but shows this error below. Any help would be appreciated.

Note the pcie adapter is from Amazoncnc@raspberrypi:~$ lspci -vv
0000:00:00.0 PCI bridge: Broadcom Inc. and subsidiaries BCM2712 PCIe Bridge (rev 21) (prog-if 00 [Normal decode])
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSELhttps://www.amazon.com/Waveshare-PCIe-x1-Board-Compatible/dp/B0DYCHPBL3/ref=sr_1_9?crid=33VGWMUG0BYP3&dib=eyJ2IjoiMSJ9.ypQynbq41MCoeL4QGbABJHPTLsXcsupt4y410Y7-ojV6fTZ0l1M0KgsBg1J-yDKzsnJKpEpvTI-4IPJQlz7VGpzcEdx4HVRXnVcwc6LUxmMsNXybT09m7bEUKP-XrAHi_aLbnWLF7A4PnWWFlLrgbw_c4POs6tvwYKhloFUVozBtrmY_6VMjehxaNp7EqRCznyaAfjPxqCbt5p75su5ewqCcAUu9DFlwG6k9lVeqdqE.BDsiMCAAEEQHMEl5wAkZVBy3hYMhbq_P1rJMjNTIVSc&dib_tag=se&sprefix=waveshare+pcie%2Caps%2C95

 =fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 39
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
Memory behind bridge: 80000000-800fffff [size=1M] [32-bit]
Prefetchable memory behind bridge: [disabled] [64-bit]
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA- VGA- VGA16- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: <access denied>
Kernel driver in use: pcieport

0000:01:00.0 Parallel controller: MosChip Semiconductor Technology Ltd. MCS9900 Multi-I/O Controller (prog-if 03 [IEEE1284])
Subsystem: Asix Electronics Corporation (Wrong ID) MCS9900 Multi-I/O Controller
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Interrupt: pin A routed to IRQ 0
Region 2: Memory at 1b80000000 (32-bit, non-prefetchable) [disabled] [size=4K]
Region 5: Memory at 1b80001000 (32-bit, non-prefetchable) [disabled] [size=4K]
Capabilities: <access denied>

0001:00:00.0 PCI bridge: Broadcom Inc. and subsidiaries BCM2712 PCIe Bridge (rev 21) (prog-if 00 [Normal decode])
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 40
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
Memory behind bridge: 00000000-005fffff [size=6M] [32-bit]
Prefetchable memory behind bridge: [disabled] [64-bit]
Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
BridgeCtl: Parity- SERR- NoISA- VGA- VGA16- MAbort- >Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: <access denied>
Kernel driver in use: pcieport

0001:01:00.0 Ethernet controller: Raspberry Pi Ltd RP1 PCIe 2.0 South Bridge
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 40
Region 0: Memory at 1f00410000 (32-bit, non-prefetchable) [size=16K]
Region 1: Memory at 1f00000000 (32-bit, non-prefetchable) [virtual] [size=4M]
Region 2: Memory at 1f00400000 (32-bit, non-prefetchable) [size=64K]
Capabilities: <access denied>
Kernel driver in use: rp1

You _probably_ don't need to take the tachos to LinuxCNC.

Typically the tachos connect only to the servo drives to feed back velocity, and the analogue voltage input from the controller sends a velocity command based on position feedback from the glass scales.

The Leinien FM1 looks like a lovely little thing.

An all-in-one solution from Mesa would be: store.mesanet.com/index.php?route=produc...id=397&search=analog
But there might be cheaper options (for example 6i24 + 7i33TA) but the 7i97T ethernet option will work with just about any supported computer, including the Raspberry Pi.

Other options exist. EtherCAT, Pico PPMC for example.

One of the LinuxCNC developers lives in Münster, I think.

halcmd (and hal)  are fine with true/false for bit types:

pcw@pcw-HP-Compaq-Elite-8300-USDT:~/linuxcnc-dev/src/hal/components$ halcmd setp hm2_7i96s.0.ssr.00.out-00 true
pcw@pcw-HP-Compaq-Elite-8300-USDT:~/linuxcnc-dev/src/hal/components$ halcmd getp hm2_7i96s.0.ssr.00.out-00 TRUE

pi@raspberrypi5:~/linuxcnc/nc_files $ ./M101
bash: ./M101: cannot execute: required file not found

Likely means that bash was not found.



 

 Sorry, I really didn't comment out these lines in Hal when I tested it from the command line. Here are the error messages.

pi@raspberrypi5:~/linuxcnc/nc_files $ bash M101
' invalid for bitvalue 'True
<commandline>:0: setp failed
: numeric argument required
pi@raspberrypi5:~/linuxcnc/nc_files $ 
 

Tried it two ways, still doesn't work. In the first case it gives an error.

pi@raspberrypi5:~/linuxcnc/nc_files $ ./M101
bash: ./M101: cannot execute: required file not found
pi@raspberrypi5:~/linuxcnc/nc_files $ bash M101
<commandline>:0: pin 'hm2_7i95.0.ssr.00.out-01' is connected to a signal
: numeric argument required

Hello everyone! This is my first post on the forum. I have a problem with setting up custom M codes on Raspberry + 7i95. I need additional outputs to control the equipment. Just turn on and off some outputs on the 7i95.
In principle, nothing complicated, but when executing custom M code, linuxcnc does not display error messages and the pin states on the 7i95 outputs do not change.
There are no changes in halshow either.

I use this image www.linuxcnc.org/iso/rpi-5-debian-bookwo...25-01-27-0140.img.xz

Here is one of the commands (M101)
#!/bin/bash
halcmd setp hm2_7i95.0.ssr.00.out-01 True
exit 0

Even if you intentionally make a mistake in the M command file, linuxcnc still does not give any error messages.
Has anyone encountered this problem on Rasberry Pi?

I had bought a mini pc from Amazon and I’m not sure if it’s causing latency issues or not ? I’m using a mesa 7i96s .   This is the mini pc I bought.
www.amazon.com/gp/aw/d/B0DNT28BV1?psc=1&...pop_mob_b_asin_title 
i shut every thing i could off in the bios including WiFi. 

I was using probe basic but I get a latency error and random disconnects . 
Could I just switch to a raspberry pi5 16gih version? 

you are right, it was quite simple indeed.

i opened the file interfaces file with
$ sudo open /etc/network/interfaces

commented out every line under #wireless

(managed to save the file this time since i was with sudo previlages.. unlike previously where i opened the file manually through the file manager)

$ sudo reboot

now wifi shows up under network manager gui, and it can be turned on and off easy.

thank you!

Ok once again.

For the interfaces you want to configure via Network Manager make sure the interface does not have an entry in the network file.

It is quite simple.

forum.linuxcnc.org/39-pncconf/50843-loca...ng-on-raspberry-pi-4

ahh.. as explained in this thread, you have to press spacebar to actually select the locale in the sudo menu-config (ha ha)

by typing locale in the terminale, the newly set locale can be confirmed. I have fixed the locale issue now.

so back to the interface settings and network manager.. i still need help there. Thanks again to all!

for the locale issue? something needs to be manually set here or? 

unknown wrote:

Once you have networking setup you can configure your Mesa card as you would for a normal PC, there are plenty of threadson the forum regarding this subject, there is nothing particular to the RPi platform in this respect.
 

i have run into a locale issue. what should be my locale set to? i am based in Germany. 
from Locales by Behai, i set up my locale as en US.UTF-8 UTF8
but the issue persists. 

and as i understand, you suggest to comment out the following lines in the interface file? correct? or will i also have to edit something in the Wpa supplicant? (once again i would prefer doing it through the menu-config)