I started developing software on a Busch 2090 4 bit computer. The external clock was 1Hz. The CPU could hold 256 assembler instructions of 3 nibbles each. 32 registers for calculations splitted in two banks. Eight “gpio” like ports, but just 4 in and 4 out. e.g. “C45” was a jump to memory address 45 if I remember correctly.
But in my text I ment that systems like a Pi2 or Pi3 are fast enough for 3D printers. The Pi4 is overpowered. Since you sometimes can pickup older RaspberryPis for less than 20 Euro, they are great components for updating printers.
OK, let’s not compete over how slow we can go I, too, used a cassette player/recorder with a TRS-80 Model I. I recall upgrading to a program that made reading/writing from/to the cassette much faster & more reliable. It was called B25 Bomber, or something like that. I also wrote a communications program in Z80 Assembler so I could remotely work on a college course I decided to take around 1981. I tried writing it in structured format but it proved too slow to handle the traffic. It ended up being spaghetti code, which was fast enough: ugly, but efficient.
Oh, I see. OctoPi supports up to 4GB, the physical limit of a 32-bit OS. The Pi 4 8GB would require a 64-bit version (which I assume has been created or is in works).
Of course, 32 bits just can’t address beyond 4GB – the numbers don’t lie :). At first, looking on amazon.com, it looked like the 8GB version is way more expensive than the 4GB, but I’ve since found some that are only moderately more $. And, all the reviews say the Pi 4 is way more powerful than the Pi 3. It should be able to run any & all addons you could ever want.
Only if OctoPrint would make use of all the power. I don´t think it is even using one core to its limits and the extra memory is for sure not required.
With a user logged in via HTTP it randomly spikes from 27% to 81%. That probably caused by the network traffic, which required much cpu load on the RaspberryPi1 due to some bad hardware design. That is why the Pi1 is not recommended to be used with OctoPrint.
But it is worth to mention that I even have the RaspiCAM running, so a picture every now and then appears in the web interface and it still prints fine.
So to summarize: The smallest RaspberryPi is using less than 1/5% of its available cpu power and a little over 4/5 with network stuff. I am not a linux shell expert, but depending on the source this should return the current overall cpu load on all cores.
But be reminded that I have no clue how the command above works.
OMG, that command brings back memories (well, that kind of command; not that 1 in particular). You have no idea how happy I was when GUI OS’ came around & I no longer had to deal with that kind of verbal diarrhea.
Well, that is the underlying OS. It would be nice to see the same graphs during print action. What did you use to get these? Do you have a full Raspian installed or is that just a Plugin for OctoPrint?
Well, I prefer the MorphOS shell over everything, too, as you have clear commands with clear arguments like
copy quick from blah.txt to newblah.txt
On linux even the command names are designed, so the function is well hidden.
On MorphOS the statements are so clear, that I even wrote a tool, that creates a desktop UI for any non linux shell command.
Yes, over the years I’ve run across many Unix/Linux weenies that took special delight in knowing an arcane “secret” language that most people have no clue about. They never understood how I could know that arcane language but be so happy that GUIs made the technology available to almost everyone. One of them even called people who don’t know the “secret” language minions. I told him that was elitest and small-minded. He stayed away from me after that
I, too, used a cassette player/recorder with a TRS-80 Model I. I recall upgrading to a program that made reading/writing from/to the cassette much faster & more reliable. It was called B25 Bomber, or something like that. I also wrote a communications program in Z80 Assembler so I could remotely work on a college course I decided to take around 1981. I tried writing it in structured format but it proved too slow to handle the traffic. It ended up being spaghetti code, which was fast enough: ugly, but efficient.
