Remora - ethernet NVEM / EC300 / EC500 cnc board

Which pulse/rev is best for NVEM RT1052?  


 

At the risk of the blind leading the blind, to me that is not quite the right question. That chart is for your micro-stepping. Like the 800 is 4 microsteps, if you're using a 1.8 deg. stepper. I have always looked at it this way - What are you doing with the motor? If your opening a door or driving a ram, picking 800 would be fine, but using that on a belt or lead screw may very well end up leaving artifacts in the work due to the rougher movement between points. The downside is the more micro-steps you have the more torque you lose. 3200 (16 micro-steps) seams to be a reasonable middle ground that most use as standard. The controller will put out as many steps as directed by LinuxCNC to make a revolution, just a matter of how fast it can do it.

Whatever you chose, that gets figured out when you tell LinuxCNC in your .ini file how many pulses it takes to move one unit. That is set with the SCALE on each axis. Like for me, I have 16 micro-steps (3200) and a 5mm pitch screw, which works out to SCALE = 640 or -640 depending which way you need the motor to move.

Regarding my milling machine and setting up the EC500.
My denford mill is using 12v drivers 
​​that need to sink the 12v to ground to move the axis. 
​​​i tried a bc537 transistor to try and switch the 12v to ground. I originally had this working with a cheap bob. But it seems the ec500 outputs are to low to drive the gate. I'm measuring 3.8v on the ec500's outputs. 
I also tried a IRLZ44n mosfet but that's also the same I can't switch the gate. Both circuits had pull up and down resistors. If I connect 5v straight to the gate (330omh resistor) I can switch the gate and pulse the drive. So I'm thinking the outputs of the EC500 are just not strong enough. 
The IC in the ec500 is the am26ls31. If I connect the differential outputs to a am26ls32 will that restore a 5v stronger signal?

hey murph, i think scott said the outputs were just optocouplers or something like that, see if you can filter through his recent posts,

pheonix, like spyder said its based on application, but start with like 800-1600 and if you get following errors its too high

Spyderbreath wrote:

Warning: Spoiler!

At the risk of the blind leading the blind, to me that is not quite the right question. That chart is for your micro-stepping. Like the 800 is 4 microsteps, if you're using a 1.8 deg. stepper. I have always looked at it this way - What are you doing with the motor? If your opening a door or driving a ram, picking 800 would be fine, but using that on a belt or lead screw may very well end up leaving artifacts in the work due to the rougher movement between points. The downside is the more micro-steps you have the more torque you lose. 3200 (16 micro-steps) seams to be a reasonable middle ground that most use as standard. The controller will put out as many steps as directed by LinuxCNC to make a revolution, just a matter of how fast it can do it. Whatever you chose, that gets figured out when you tell LinuxCNC in your .ini file how many pulses it takes to move one unit. That is set with the SCALE on each axis. Like for me, I have 16 micro-steps (3200) and a 5mm pitch screw, which works out to SCALE = 640 or -640 depending which way you need the motor to move.

 

Thanks for reply,
I have set 12800 and testing some gcode only with Y working.
I don't want to cause problems when all the stepper and spindle are physically working.

Please, I've been trying for months without success. Everything seems to be fine, but I can't compile it onto the board. I'm using v5 of the cloud. I have no idea what it could be. I see that everyone follows the steps and it works. However, I even had a lot of trouble installing pyocd, but with a lot of effort I finally managed to do it. Please, can someone tell me what I'm doing wrong?

Try been in the directory where the file is located. Before you run pyocd. Are you able to ping the board. 10.10.10.10 ??

  Good afternoon, I think I managed to do what you asked me, but without results, still with the same error. Could it be my pyocd installation? I've tried with other versions of Debian, but always the same problem.

Hello dear EC500 users,

same as Thayloreing , I had a quite frustrating time trying to flash my EC500 over the last months. And there still is no success. So I am considering quitting the whole thing but I want to give it a last try by registering to this forum.

The problem is to get the firmware into the flash... and I did not find any solution that is working for me. I even can not reproduce the video from scotta with the reprogrammed STLink/V2 stick.

I tried:

• Modified STLink/V2
• DAP Link probe from Aliexpress
• JLink Edu mini

on

• pyOCD
• MCUExpressoIDE
• On Windows and Linux

I was not able to use the modified ST-link/V2 stick (as in the video from scotta) as a mass storage device under Windows for drag and drop usage. It simply does not show up in Explorer. I checked this with 3 different computers.

The DAP Link Probe is being detected under Linux and is attached to /dev/ttyACMx, but flashing with pyOCD leads only to the prompt: no ACK.

Using both probes under MCUExpressoIDE under Linux is useless, because they are not detected at all. JLink shows up, can be selected but stops programming by stating: can't stop CPU.

The EC500 seems to be a quite nice piece of hardware and I would like to use it in my projects.

Is there a working solution to flash this board available anywhere? I was not able to find any reliable solution what so ever.
Further on: Is the programming interface on the EC500 even usable? And what pins has to be used? There are:

• VCC
• GND
• SCK
• SWO
• Boot_MO
• Pro_B

Is this a sufficient pinout for a  working interface for SWD? SWO is for CPU output, not for data input. And what are Boot_MO and Pro_B good for?

I hope for any help on that topic. Programming a MCU should not be that complicated...

Cheers Julius

Hi Julius,

Very strange that one of those combinations don't work, especially MCUExpressoIDE.

For flashing
1. board is externally powered from 24v, so no VCC connection
2. GND, SCK and SWDIO is all the connections needed to the CMSIS-DAP probe

When I've experienced connection issues, powering on the board as the probe is trying to connect to the MCU has helped.