Advanced Search

Now i want to expand my inputs and outputs in raspberry pi 5, can you suggest me how to expand my i/o and if there is any solution can you also tell me how to configure HAl. I do not want to use MESA board as it is expensive, can someone suggest something cheaper?

Cant do this anymore bye all wrote:

No don't use a hub.

Linuxcnc-rio is awesome, with a single WT32-ETH0 and a direct cable connection and inexpensive FPGA you can do 4 axis easily and way more.

i think he will use ethernet for wiring like with ethercat.


 

Sorry but i do not use RPI's at all,and that will not change untill their price drops back to under 50$.

Hi @tommylight, thankyou for your insight.
Now i want to expand my inputs and outputs in raspberry pi 5, can you suggest me how to expand my i/o and if there is any solution can you also tell me how to configure HAl

No don't use a hub.

Linuxcnc-rio is awesome, with a single WT32-ETH0 and a direct cable connection and inexpensive FPGA you can do 4 axis easily and way more.

Awesome used all of elovalo bits to setup an Rpi5 with Pineberry NVME hat, works great.

Can you tell me how to configure HAl and ESP32 if I have to build it for just 1 axis?

Using ethernet hub or switch will add a lot to network latency, so it might not work at all, even if everything else works.
Never tried with a hub, but i do have a switch that works with Mesa boards for days without issues.
Still, i never use a switch on production machines, the risk is to big.
-
Network hub = old, any packet sent to any pc wired to it will be sent to all connected PC's.
Network switch = new, any packet sent will be sent only to the PC with the IP address contained in that packet.

At 1ms tick time round trip for the ECAT bus, you can theoretically achieve .001mm granularity of position. At that rate one could also have 60000mm/m velocity or 2362 ipm. Very few machines in the CNC world can even handle such speeds and the acc/dec inertial demands this velocity creates. Any attempt to advance the bus cycle time aka tick time is a waste of time and energy especially for a hobby/light industrial machine.

I would recommend doing some study of basic physics before walking down a road to nowhere. No matter how faster your motor, bus, etc... you are limited by the physical construction of your machine. Period. End of discussion. Or you have a $1 million machine for the likes of DMG or Chiron. Or simply a million bucks you like throwing away fixing the scrap heap that speed would create of your machine.

Millions of motion control systems utilizing ECAT run using the standard tick cycle of 1ms. I will default to a proven theory put to practice any day. A theory I have proven over years of practice myself.

Have a nice day.

Are the stepper motors 0.9 degree per step?
Should be written on the back of the motors.

in principle, yes,
but you would have to build the hal component in such a way that the ethernet packets are sent and received in parallel,
otherwise it takes too long.

EDIT:
but since udp is used, this can lead to collisions.
maybe send with minimal delay and then wait for the responses

Hi Linuxcnc community, 
I have installed OS in raspberry 5 and Instead of using IO expander I want to use individual ESP32+W5500 for every motor and generate step pulses. If this is possible please help me with the steps in achiving it.
Refer the image below and get what I want to achieve
https://drive.google.com/file/d/1JCuLksqd7dcpAcJ44GajRwzOFmay_xuQ/view?usp=sharing 
Thankyou

AFAIK with parallel port breakout, you will be able to do only step/dir signals - if those servodrives do accept step/dir then you definitely can reuse them. The problem will be the parallel port. It is slow and limits your I/O and also has become ancient relic in PCs. That is why most of folks are using Mesa boards. But for that we need to know more about the drives

The figures (scale) is correct.
So that would point to a mechanical issue(s).
Usual suspects are.
Stepper motor mounts, are they secure.
Ballnut mounts, are they secure. Ie ballnut to bracket, bracket to saddle.
Coupler mount between stepper motor and ballscrew.
Are these measurements the same all along the axis ?
Does velocity/speed affect this ?
If you disconnect the steppers from the drivers and manually turn the steppers is the issue still there.
If you directly turn the ballscrew is the issue there ?
Are the ballscrews clean and straight ?
Is there any lateral movement of the ballscrews ?
Are the ballscrews bearings in good order ? Are the ballscrews bearings at the fixed end plain ball bearings, plain bearings or angular contact bearings ?
Does the saddle rack or twist when moved ?

Hallo zusammen,ich habe schon eine Weile die QtDragon GUI im Einsatz und meine Maschine nun um einen Werkzeugtaster erweitert. Der Werkzeugwechsel soll halbautomatisch ablaufen (kein ATC, ich habe Spannzangen). Ausserdem ist der Werkzeugtaster aus seiner Halterung herausnehmbar sodass ich diesen auch zum Antasten der Werkstückoberfläche benutzen kann.Ich habe nun die INI und die HAL Dateien entsprechend der Dokumentation angepasst, bekomme keine Fehler angezeigt und die Routinen laufen wohl wie gewünscht ab.Ich bin nun so vorgegangen (alles aus dem Versaprobe Tab):1. Antasten der Werkzeugtaster-Höhe2. Antasten der Werkstück-Oberfläche (auch mit dem Taster)-> Die Beiden Werte werden automatisch in Probe HT und Block HT übernommen.3. Start meines Programms-> Maschine fährt zu Wechselposition. Nach Bestätigung des Werkzeugwechsels wird das Werkzeug vermessen und auch ein Z-Offset in der Werkzeugtabelle eingetragen. Das sieht soweit erstmal nicht schlecht aus.Der Nullpunkt der Werkzeugoberfläche wird auch aktualisiert (Auto Zero aktiviert), ist jedoch weit weg von der echten Nullposition.Hat jemand eine Idee warum dieser so falsch liegt oder ist meine Vorgehensweise bei der Vermessung einfach falsch?Anbei meine HAL- und INI Dateien.Danke schon im Voraus für eure Hilfe!