Remora - ethernet NVEM / EC300 / EC500 cnc board

beauxnez wrote:

Thanks, I don't know if I did it right but I got an error message.
That's a warning, not an error. You can usually fix it by copying the

That's a warning, not an error. You can usually fix it by copying the libusb.dll (libusb dynamic link library) to the path of your Python installation.

Note: If you downloaded Python from the Windows Store, you should copy libusb.dll to the C:/windows/system32 directory.

M.De post=317431 identifiant utilisateur=41690

beauxnez post=317414 identifiant utilisateur=22230Merci, je ne sais pas si je l'ai bien fait mais j'ai reçu un message d'erreur.
C'est un avertissement, pas une erreur. Vous pouvez généralement le corriger
en copiant le fichier libusb.dll (bibliothèque de liens dynamiques libusb) dans le chemin de votre installation Python.

Remarque : si vous avez téléchargé Python depuis le Windows Store, vous devez copier libusb.dll dans le répertoire C:/windows/system32.

in the directories VS2013,VS2015,VS2017,VS2022 there is a libusb-1.0.dll in each folder

Hi, there's some additional config parameters that can be used to configure the DMA stepgen. "Step Length", "Step Space", "Dir Hold" and "Dir Setup".

From the HBS86H data sheet:

PUL: pulse width should be longer than 10μs
DIR: signal should be ahead of PUL signal by 5μs at least

Therefore I'd suggest these settings in your config.txt as a starting point.

"Step Length": 10
"Dir Setup": 5

The normal stepgen runs at 40Khz so most drivers are happy with the step form being generated.

Scott, thank you very much for pointing me in the right direction. I made changes to the configuration file "ec500-rt1052-DMA.txt" (JSON) according to your guidelines. I modified the parameters: "Step Length": 10, "Step Space": 5, but for now, I’m applying it only to one axis, X - JOINT_0, for testing purposes. I’m glad you helped me. Of course, in the *.ini file, I adjusted the SCALE parameter to match the settings from the HBS86H (microsteps) and to ensure movements are adapted to the lead of the ball screw. For now, everything is set up on the floor at home. In the future, I plan to install the Remora system on my new CNC machine, which I’ve been building for a long time (mainly because it’s very heavy, as it’s supposed to be, and requires a lot of work). I want it to be faster in its movements than my current one, which operates on a parallel port. If I have any questions, I’ll definitely ask you or others on the forum. It’s great that you’re all here and creating such amazing things. Take care for now.   Christopher - tu_koper.

EDIT:Weird, tried to make it working for 2 days. Today i shutdown everything and few hours later without any config change it started working...

I was able to successfully flash remora to ec500 rt1052 with nvmpg and display is working correctly.
Using basic config from repo I'm able to move axes but when I try DMA config i get "Error on joint X" error.

What i did:
- used linuxcnc 2.9.3
- flashed controller with 3.1.3 firmware - display works
- installed both components from: github.com/scottalford75/Remora-RT1052-c.../LinuxCNC/components
- uploaded DMA config to controller (did that multiple times across restarts): github.com/scottalford75/Remora-RT1052-c...ec500-rt1052-DMA.txt with below settings for each axis (I'm using DM556T drivers)
```
        "Step Length":        3, # (at least 2.5us pulse width)
        "Step Space":        3, # (at least 2.5us pulse width)
        "Dir Setup":        5,  # (at least 5us before step drive)
        "Dir Hold":        5 # (also tried without that but no difference in behaviour)
```
- used example config from repo for DMA from: github.com/scottalford75/Remora-RT1052-c...CNC/remora-ec500-DMA

Now when i start axis UI and try to move any axis i get error:
```
joint 0 following error
emc/task/taskintf.cc 976: Error on joint 0, command number 107
```

I have 4 stepper drivers wired, 3 axes configured and problem occurs on each of xyz.

Any ideas what may cause this behaviour?

 

Hello Zelo,I had a similar problem, and sometimes I even manage to encounter it again. I think the issue might be related to the slider settings for the speed scale in LinuxCNC.The error you mentioned is caused by an incorrect position for joint0. This phenomenon can likely be triggered in various ways. One possible cause might be the low value set for the parameterin thefile. Try increasing this value.During my experiments, I also encountered such situations, but they were caused by using a configuration file meant for the basic version and then mistakenly running LinuxCNC with a configuration describing a machine operating in DMA mode. I think this issue is independent of whether you have DM556T drivers connected, as these are drivers that do not operate in a feedback loop with LinuxCNC+EC500. Therefore, during testing, you can focus more on configuration settings rather than hardware.It’s possible that after these 2 days, you started LinuxCNC with the correctfile matching the configuration you uploaded to the EC500, namely.

I thought I would add something to this discussion. The SCALE parameter in thefile is closely dependent on how the DM556T driver (or another motor driver) is configured, specifically its micro-stepping settings, as well as the pitch of the leadscrew (ball screw). For errors of this type, related to critical timing during axis control, it might be beneficial to initially set the SCALE parameter to a low value when testing your configuration.In my case, thefile currently has, and my HBS86H driver is set with no micro-stepping and a screw pitch of 5 mm/rev. I figured that if the driver is not operating in micro-stepping mode, this means fewer pulses are required to control the driver (which is obvious). Consequently, this results in fewer output signals being sent by the EC500 within a given time frame compared to when micro-stepping is enabled. This might prevent the loss of some information that could occur during motor control.During my tests with the X-axis (as I am currently only controlling this axis), no errors as previously discussed have occurred with these parameters. However, when I reverted to settings with a higher SCALE parameter and micro-stepping enabled on the driver, the error reappeared.This is likely well-known information to most of you on this forum, but I am sharing it as a tip for others who might not be aware of it. If I am mistaken, please feel free to correct me. I simply want to share what I have observed. I am just beginning my journey with "LinuxCNC," and any lessons or feedback from you would also be valuable to me.

Hey Scotta,I saw that you recommended flashing the ST-Link with CMSIS-DAP firmware. Just out of curiosity, I tried flashing it using the ST-Link, and it worked! In fact, it was smoother than the CMSIS-DAP probe I bought. The reason is, the CMSIS-DAP probe needed some extra configuration to work on Windows, while the ST-Link just worked out of the box. So, for anyone thinking of flashing the firmware, I’d suggest using the ST-Link V2 with PyOCD directly.

I'm finally getting somewhere with the encoder. Used this diagram from the site below. Ordered the board from jcbway, the iso7740 and components from AliExpress. I finally get the PV counting in both directions. Next just figure out the spindle setup with it.

www.electronics-lab.com/project/4-channe...d-digital-isolators/

Hello everyone! First of all, I would like to thank Scott for the development and thank the contributors for their help!

I would like to convert my existing CNC using an EC300 controller. I thought the firmware installation would be the challenge, but in the end, the LinuxCNC configuration caught up with me. I have been using the machine for some time with LinuxCNC, with a parallel BOB.

I can control the spindle and its speed with the new controller.
With the EC300-rt1052.txt configuration, I managed to get the limit switches and e-stop working and I can move the axes to some extent, but the movement is choppy. (dm556 drives). I tried to adopt the DMA version of the EC500, but there is no movement at all.

Clearly I have something un - or - misconfigured. 

Can someone help by sharing an EC300 specific DMA config.txt, ini and hal-file? Is there any component other than config.txt that I might have overlooked for DMA stepgen?