Advanced Search

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.

apt purge linuxcnc*

Reading package lists... Done
Building dependency tree... Done
Reading status information... Done
The package 'linuxcnc' is not installed, so it will not be removed
0 packages upgraded, 0 newly installed, 0 to be removed, 0 not upgraded.

the second option worked but the first one didn't


1To install from a fresh Debian 12 with NO LCNC installed yet, just use: sudo dpkg -i (package name here without brackets) for each deb and reboot. Choose the RTAI kernel in Grub, enjoy.

2To install on Debian 12 with linuxcnc-uspace already installed use : sudo apt purge linuxcnc* and wait for apt to completely remove every trace of LCNC.
Then follow the instructions for a fresh Debian 12 install above.

@MennilTossFlykune do you know if it's possible to zoom to the machine extents (the red box) with a pushbutton?

Note: Prolly not going to work, or be super-reliable with those inductive antena jumper leads lol. Good enough for testing anyway. If this all works out I'll amend the dev board and swing on a wiznet w5500 part with the magnetics, route cross-talk outta of it, add the highspeed opto and level shifters for ins & outs. Guessing the SPI is plenty sufficient for comm and so no need for the realteck gigabit, methink.

I'll keep you updated. Thanks again, meister.

So, "slave" has a fairly specific meaning in EtherCAT -- it's basically just an EtherCAT device that isn't the master device that's in charge of timing for the bus.

In this specific case, it looks like it's just a 3-axis CiA 402 device. The first axis uses objects in the 0x60XX address range, the second is at 0x68XX, then 0x70XX.

You can either take a single-axis CiA 402 XML file and duplicate things, or you can give the new-ish basic_cia402 driver a spin. Out of curiosity, what happens if you run lcec_configgen on the box? It should spit out a mostly-working config file and you can cut-and-paste into LinuxCNC's config, but I don't think I've ever seen a 3-axis CiA 402 device before. I have 1, 2, and 6 axis devices here, though, so 3 should probably work .

I am with you on the "i have hardware" so use that, see how it works for you.
I was in that position and the amount of stuff i learned is astonishing so when i got my first Mesa boards (5i25+7i77+7i74+7i70+7i71+7i71) took me half a day to have everything wired and working, on a 5 ton machine.
You can always order Mesa gradually, get the 7i96S as it is very versatile and has expansions for everything, or get the 7i92TM even cheaper, then add 7i83 for analog and 7i85 for encoder feedback, add 7i84 for 16 outputs and 32 inputs, 7i85S for step/dir, etc, etc there is a huge number of combinations and expansions options.
As for used ones, i got a 7i96 back during the pandemics, in total cost me 330 Euro here, the next day i got an offer to sell it for 1000 Euro, i did not sell it despite not needing it right then.
Luckily that time is over.

meister wrote:

[code][code]EDIT: the config i build is only for testing, serial port will not work for LinuxCNC,
if you want to run LinuxCNC you need SPI (raspberry) or UDP (W5500 / UDP2SPI-Bridge)

[/code][/code]

Everything set-up & synthetizing-wise is working flawlessly. Said it before and I'll say it again; pretty EPIC work you've done for us   

I took onto your advice and stopped by my local gizmo shop to pick a W5500 Lite. Inserting a visual of my benchtop hardware set-up for inspiration and good luck! 

Update :

I believe my stlink stopped working fine. I've used nanoDaplink and there was still no answer from the nvem. Finally I've pushed (and keep it pressed) reset button on nvem, then start flashing with pyocd. When I started pyocd I've released reset button and whole process went fine from there. It was flashed with remora 3.1.3. Later I've connected ethernet and tried to ping. One of the leds on nvem went off and my ping was succefull. Then I've used this config :

github.com/scottalford75/Remora-RT1052-c...NC%2Fnvem-rt1052.txt

And it was all good. Previously I've used by mistake basic and full config from here :

github.com/scottalford75/Remora-NVEM/blo...vem-basic-config.txt

Which I believe was not for RT1052 version of nvem board. DON'T USE THIS CONFIG. 


Quick install eth component and everything works perfectly. I can move 3 connected axis with this linuxcnc config :

github.com/scottalford75/Remora-RT1052-c...Fremora-rt1052-basic

But this Linux cnc config is only for 3 axes. Do I have to manually set my 4th axis? 

Next step will be adding limit switches, one for each axis (except 4th). Maybe this evening I will find some time. 

 

Hi Arciera,


Is this all happening in user-space so far (including the velocity planning)? If so does this output a GCODE file?
Yes, this is all done on a non realtime kernel at the moment. Including the velocity planning indeed.

Currently i have no logic to output a optimized gcode file, but it is certainly possible.
How relevant is this option at the moment?
We could also add a scurve path simulator to the user side.

Then the kernel motion code, can be centralized in a c++ class, then both the user side and kernel side can use
this code to run the program. This is just an idea.

This file has ~12500 lines of gcode.Used G64 P0.5 Q0.5
red=3d velocity profile
white=line
purple=clothoid fillet
cyan=spline fillet

 

It's now almost time to test the results on a realtime kernel.
Let's work on to that.

For a letter test:
Original input G64 P0 Q0.5
 
Input G64 P5 Q0.5
The spikes from the velocity profile are gone !

1. Mesa must be wired directly to PC
2. set up the networking using network-manager:
forum.linuxcnc.org/27-driver-boards/3559...ethernet-mesa-boards