Mesa hm2/hm2_7i96s.0: error finishing read

tommylight wrote:

spumco wrote:

Getting the Odroid sorted out last year was 3 or 4 months.
Hence my insisting on not using any type of SBC for machine control.
I was there once, still have 3 of RPI3 collecting dust. Never again.
 

I may stick the G1 that's on it's way in the mill and pull the Odroid.  These HP's have pretty good latency.

I would recommend you  get a decent  power supply for the 7i96s. Something like a Meanwell MDR-20-5 @ 3 amps. 2 amps might do it too.
Many people have come to grief with USB power supplies too.

spumco wrote:

UPDATE

The HP Elitedesk 800 G2 mini has been running Deb 12.2 w/rt6.1. No significant changes to config other than typical intel NIC grub stuff.

No read finishing errors for an hour while running YT in background.

 

Very interesting, what ping times are you seeing to the Mesa card?

I've found that if I leave my Elitedesk 800 G2 mini running a day or two the communication to the Mesa card breaks down totally and won't resume until I reboot the machine (service networking restart doesn't help). There are also some PCIE related errors periodically in the syslog which seems to be common with these Intel network cards when things aren't fully working as they should.

rodw wrote:

I would recommend you  get a decent  power supply for the 7i96s. Something like a Meanwell MDR-20-5 @ 3 amps. 2 amps might do it too.
Many people have come to grief with USB power supplies too.
 

Indeed.
Meanwell and Rhino (from Automation Direct) are all I use for both personal and customer builds.

The hacked USB wart was all I could find laying around the shop for testing.  I ordered an HDR-15-5 about halfway through the hour-long first test.

Unlogic wrote:

Very interesting, what ping times are you seeing to the Mesa card?
I've found that if I leave my Elitedesk 800 G2 mini running a day or two the communication to the Mesa card breaks down totally and won't resume until I reboot the machine (service networking restart doesn't help). There are also some PCIE related errors periodically in the syslog which seems to be common with these Intel network cards when things aren't fully working as they should.

800 G2 Ping times were as I posted a few days ago in this thread:
forum.linuxcnc.org/27-driver-boards/4691...ead?start=220#285449

Decent, but nothing to write home about.  Latency was a bit better than on the MeLE Q3, but ping times not as good.

After running LCNC on the G2 for a while last night I decided to have a look at the read-time pin.  While LCNC never threw a read finishing error, I did notice a regular read time spike.  Not enough to accumulate any packet losses, but there was a spike every 1.5 seconds - looked like a heartbeat in halscope.

The MeLE shows none of these spikes.  I don't know if that's because I've got Deb 13 & rt6.6 on it vs Deb 12.2 & rt6.1 on the G2... but I've lost interest in fiddling.

For that reason I've decided to set the G2 aside and use the MeLE for this build.  Based on your (@Unlogic) experience and the read time 'heartbeat' spikes, I don't feel like dealing with yet another power supply and PC mounting fandango.  The PC and PSU are inside my operator console and it's non-trivial to switch between a 12v and 19v PC.

I'll be very interested to see the results of PCW's testing when his G2 shows up.

Finally tested my Elite 800 G2 and its seems perfect so far.
(45 minutes running LinuxCNC with YouTube videos running
and servo thread tmax is ~250 usec)

I basically did nothing but install the 2.9.1 ISO, disabled IRQ
coalescing and launched LinuxCNC.

When I said nothing, I mean nothing, I made no BIOS changes,
no isolcpus, no IRQ pinning. Looks to be nearly the best of the
HP Elites I have tried so far. The model I have has 8G RAM and
a I5- 6500 3.2 GHz CPU.

I do see PCIE errors in the kernel log but these are from device
8086:a115 which is not the Ethernet controller


I will let it run for a week or so and see if any problems show up
 

Thanks for looking into this PCW, your findings are very interesting.

Are you running the box in UEFI or BIOS mode?

UEFI

Based on Rorarysmp's experiences in the thread linked below I went straight to legacy mode and didn't even bother with UEFI mode.

forum.linuxcnc.org/26-turning/41498-scha...fit?start=260#227063

I wonder what makes your setup work while the rest of us ran into so many problems. Could it be a hardware revision or BIOS version maybe?