Advanced Search

1 linux image
2 linux headers
3 linuxcnc
4 rtai modules
OR
3 rtai modules
4 linuxcnc
-
Gdebi will tell you if there is something that needs to be installed.

Cant do this anymore bye all wrote:

forum.linuxcnc.org/9-installing-linuxcnc...r-2-9?start=0#304599

Start with the kernel packages, then I think there are some modules then finally the Linuxcnc packages. Best thing is to read completely read through both threads linked in the previous threads.

Your avatar is scary, but you look like a good person!

I'm able to understand things
 

tommylight wrote:

Do a new full install and start over.
Never use root or SU to install stuff as everything will be installed in the root folder and nothing will work as a normal user, always use sudo.
LinuxCNC will refuse to run as root due to having full hardware control and stopping misuse.



Before seeing your post, that's what I did, so I was right to do a new installation
Thank you, now I need to know something, are there 4 files, should you install all 4 or just one?

linux-headers-5.4.279-rtai-amd64_5.4.279-rtai-amd64-1_amd64.deb
Arquivolinux-image-5.4.279-rtai-amd64_5.4.279-rtai-amd64-1_amd64.deb
Arquivolinuxcnc_2.9.2_amd64.deb
Arquivortai-modules-5.4.279_5.3.3-linuxcnc-delta_amd64.deb
   
 

NOT my stuff!!!
-
Several videos of building a strange 5 axis machine with hand tools, he does a great job of explaining every step in detail:

Thank you very much, I will test it as soon as possible, get back to you if everything goes well

hmm, ok fair enough. I'm no expert and so glad you are. I'm quite grateful I can actually get step pulses out to the oscope and comm with Lcnc already. Pretty cool. Guess fine-tuning this comm reliably will require some significant effort (knowledge?). I'll have a look at the RMII and Esp32 solutions when time allows, and see what comes out. Expect stupid/clueless questions coming your way soon enough though!!

Do a new full install and start over.
Never use root or SU to install stuff as everything will be installed in the root folder and nothing will work as a normal user, always use sudo.
LinuxCNC will refuse to run as root due to having full hardware control and stopping misuse.

MIN_FERROR = 0.010 - This is the value in machine units by which the joint is permitted to deviate from commanded position at very low speeds. If MIN_FERROR is smaller than FERROR, the two produce a ramp of error trip points. You could think of this as a graph where one dimension is speed and the other is permitted following error. As speed increases the amount of following error also increases toward the FERROR value.

FERROR = 1.0 - FERROR is the maximum allowable following error, in machine units. If the difference between commanded and sensed position exceeds this amount, the controller disables servo calculations, sets all the outputs to 0.0, and disables the amplifiers. If MIN_FERROR is present in the INI file, velocity-proportional following errors are used. Here, the maximum allowable following error is proportional to the speed, with FERROR applying to the rapid rate set by

If you are on the factory settings of the PID regulator. They are almost always very soft. They must be set up.
When the driver is activated, the motor axis must be locked - by hand, the axis must not move.

the rmii code is not mine, unfortunately my knowledge of verilog is not sufficient for that, i have only adapted it to rio

github.com/sipeed/TangPrimer-20K-example...Ethernet/verilog_UDP

you can run the rio-test tool to see the timeouts:
all in all, it works quite well with the w5500, but with the esp32 I get no timeouts at all

EDIT: the ping is completely handled inside the W5500, so it's not a good test

Comparison added for the sake of having something to compare too. Nothing scientific ofc, however goes to show. Here's me brutalizing the gateway the same way, yet here we are talking, lket alone streaming 4k vids, dwloading gigabytes of data from int'l servers. 

I'm not an network expert but, this W5500-over-RIO seems to be bullet proof!! Fairly impressed already. 

I can now say what condition I am in

Save this as 'feed_zero.py', mark as executable and save to a folder called 'python' inside your machine config:



Then add this line to the [HAL] section of your ini file:
This should then zero the feedrate and rapid-feedrate when the machine is first enabled and also whenever a new gcode file is loaded.
Note this will not zero the feedrates if the same file is loaded/reloaded.

meister wrote:

i am not yet satisfied with the W5500, better not to plan for it, there are packet losses and i have no idea why, it can't be because of the cables as i have test setups without them.

I also have a working RMII interface, but so far I have only been able to get it to run on a TangPrimer20K (with gowin toolchain) and even there I still have a few problems.

Are you sure about that w5500 pkts losses issue? Perhaps my silly jumper leads are less inductive/destructive than anticipated, I don't know. To me the losses are within 'functional specs' when a brutal ping beat-up is applied (see visual). Not 0% perfect ofc, but then no interfaces are perfect under that stress, to my limited knowledge mind you. 

The RMII reference design is an excellent one indeed. Not easy to implement though, you have my respect. 


 

How relevant is this option at the moment?

Not relevant, I was just wondering if I could run the output on a simulator.

thank you, you make me embarrassed

i am not yet satisfied with the W5500, better not to plan for it, there are packet losses and i have no idea why, it can't be because of the cables as i have test setups without them.

At the moment a UDP2SPI bridge (esp32) is still the best solution.

In principle, you could also programme the FPGA via an esp32 (JTAG or SPI flash), but you would have to adapt the firmware first.

I also have a working RMII interface, but so far I have only been able to get it to run on a TangPrimer20K (with gowin toolchain) and even there I still have a few problems.