Remora - ethernet NVEM / EC300 / EC500 cnc board

Would 200 - 250khz be a reasonable step rate? I discoverd that clearing of the buffers (memset) was consuming more time than the step calculations for the 6 axes. So if we can use DMA to clear the buffers the step calculations take less than half a servo period, so still time to do Ethernet communications etc.

I would think yes, most good quality stepper drives have 200kHz as the maximum rate.
At some point/speed the cabling becomes an issue, but since the drives are on the same board, not an issue in this use case.

Please Yes..

scotta wrote:

Thanks for the photo, you have the later board which is great. Also great to hear the serial communication with the NVPMG is working correctly. I think I need to put some jumpers over some of the additional components on my board to get it to work.

The config and nvmpg hal file on github need to be updated with the correct pinout for the EC500. Not sure if this is what is causing it but it's the first step in solving the issue. I'll look to update over the coming days, but you can check your config with the following pinout.

 

Attachment not found

 

Hi Scott, 
Can you please explain to me again how and where I should change the config.txt so that the EC500 runs smoothly with the nvmpg?

Thanks in advance

Christian
 

Hi Christian,

I've check the EC500-full-config.txt and found an error that my (or may not) be the cause. In the AIN input, the pin was wrongly set as PC_1 where it should be PD_1. This has been corrected in the repo now.

PC_1 is actually used for the Ethernet, not sure if this was the cause. I still need to get my serial working to test further.

I would like to thank Scott for his great contribution giving us the Remora Nvem .. for me it is working at a rate of 48khz perfectly.
Attached are the machine settings..
With some changes  (I don't know if they are valid) , the realtime problem has been solved.
I would like if one of you could evaluate attached files because I don't know if I've done right.

Hi, thanks but how are your setting the Base Thread frequency? From the HAL file or by compiling?

Note that PRU_BASEFREQ must be the same in both the LinuxCNC component (or from the loadrt command) AND in the firmware otherwise your frequency scaling / speeds will be wrong.

I just have recompiled the component not the firmware.. that's why I've asked if what I have done is ok.

I will try to recompile de firmware.. with 100khz at least or 80khz .. and try .

thank you

scotta wrote:

Hi, thanks but how are your setting the Base Thread frequency? From the HAL file or by compiling?

Note that PRU_BASEFREQ must be the same in both the LinuxCNC component (or from the loadrt command) AND in the firmware otherwise your frequency scaling / speeds will be wrong.


 

scotta wrote:

Hi Christian,

I've check the EC500-full-config.txt and found an error that my (or may not) be the cause. In the AIN input, the pin was wrongly set as PC_1 where it should be PD_1. This has been corrected in the repo now.

PC_1 is actually used for the Ethernet, not sure if this was the cause. I still need to get my serial working to test further.
 

Hi Scott, still the same. Without nvmpg it works. With nvmpg on it shows the coordinates but goes in estop as soon as i push any button. After this the terminal says the connetction to the card is lost. Any idea?

Hi Scott, 
After cloning Remora-novusum from  github.com/scottalford75/Remora-Novusun
and compiled the project without any modification in all 3 platforms (Mac, Linux, Windows11) the result is a file greater in size than the same file in the Firmware Folder.. 
After the compilation the file was uploaded to the Novusun NVEM and in all 3 files from each OS ( Mac, windows and linux) neither one worked, the Novusun has no IP-Address  and and for that, impossible to ping the board
Is there any trick or anything that I'm not seeing?
 

scotta wrote:

Hi, thanks but how are your setting the Base Thread frequency? From the HAL file or by compiling?

Note that PRU_BASEFREQ must be the same in both the LinuxCNC component (or from the loadrt command) AND in the firmware otherwise your frequency scaling / speeds will be wrong.