On 7/1/22 12:54, Chris Albertson wrote:
The problem was using the Pi4 as a *development system*. This means
continuous code changes, use of Git and text edits every day for hours.
Simply using LCNC is nothing like that.
I've reduced that to a handful of scripts pointed at in crontab, and 3
or 4 per
Linux version to do the builds. When I build, I normally use the
buildbots output.
That said. I don't see the point of using a Pi4 as an LCNC controller?
The Pi4 is great and hard to beat if you need a computer to take up
little space and use little power or even run on battery power. I have a
Pi4 right here on my desk inside a robot as the robot has very limited
space and power available. But in the shop, next to the mill and 3D
printer is an Intel i5 with 16GB RAM and an actual spinning disk drive (it
also happens to be connected to the same file server as the pi4).
After my experience with spinning rust last year, there are no
spinning rust drives left in service here, all are SSD's some as small
as 40GB. The pi has two, a 120G and a 240G for workspace away
from the u-sd, but it still boots from a 64G u-sd.
Lightning fast, only problem was a single BBLB usb3 to sata-ii
adapter that wasn't Startech, replaced the adapter with a Star tech,
the drive was fine. That speed on a usb3 interface, makes a kernel
a half hour job on the pi, and linuxcnc if the buildbot is down, about
a 3 hour job from git pull to install-able debs. Used to be around an
hour but the new docs format and recently added languages takes
longer.
The pi's don't do isolcpu's like intel does, but I get latency figures
in the 12 u-sec area, plenty fast enough for linuxcnc, but don't run
Firefox with linuxcnc, Firefox is as big a pig with irq lockouts as NVIDIA
ever thought of doing. The machine won't fault, but it sure will stutter.
On Fri, Jul 1, 2022 at 9:04 AM John Dammeyer <[email protected]> wrote:
Hi Chris,
I like that idea but the if you are using an Ethernet Based MESA 7i92 then
the Ethernet port should not really be shared with the rest of the system.
Ideally then for the rest of the system there should be a USB 3.0 to
Ethernet Dongle. Or perhaps a SPI bus to Ethernet dongle since none of
the standard pins on the Pi4 are being used.
Any suggestions on which would be best?
Thanks
John
-----Original Message-----
From: Chris Albertson [mailto:[email protected]]
I solved this problem (using Pi4 as a development system) by placing all
my
files on a file server. Development systems see near constant
re-compiles
and write to log files, source code edits and backups and so on. The
networking on the Pi4 is pretty fast, or "fast" compared to an SD card.
The File Server is connected to a backup system that does a
continuous real-time sync. This means that if the server explodes I
lose only a few minutes of work.
_______________________________________________
Emc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users
Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>
_______________________________________________
Emc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-users
