Remora - ethernet NVEM / EC300 / EC500 cnc board

 

 
I'm very very suspicious that these random cases are due to how the DR_TOGGLE register is being used and in some cases the output pattern become inverted. The DR_TOGGLE register needs less computation to fill but if the reliability is not there then I'd rather move to using the DR register and spend more CPU time to generate the full step pattern, not just the step change locations. Most people are unlikely to have 6 axes running at 500khz at any one time so we'll still have enough CPU time to do the step buffer fill.

From what I could observe and this is just my experience, the directional changes happen only between restarts of linuxcnc . And in my case it happened only for one of the motors of the tandem y axis where one of the motors will start to spin ccw when they should both spin cw. This occurs withbought power cycling the board. For me, the directional switch never happened during the same session of linuxcnc.

Couple that with the fact that outputs of joints will jump from one slot of the board to another if the machine configuration is modified in the ini file. Ex going from XYZ to XYYZ . Could this problem be on the linuxcnc side and not on  the board firmware side?

I could not find a reliable sequence of steps to reproduce the directional change other than observing that it happens at random between restarts of LCNC.

Did anyone experienced directional switches during the same session of linuxcnc operation using the dma branch?

Murphy wrote:

I have the 5v turret tool position signal on input 3 and index on input 4.
Input 1 and 2 are the 24v Prox sensor. Pulses every stepper rotation. For homing. Works perfect.

When driving the turret you can see the LEDs lighting on the optocoupler and on the EC500 but they are a lot dimmer than input 1 and 2. The inputs for the turret are not registering in hal. Am I right in thinking the 5v input isn't enough to drive the optocouplers? Even it says it will work with 3.3v and 5v.

Have you tried displaying all the input pins in the hal window? For example, for me input7 on the board corresponds to input9 in hal. Perhaps you are just reading the wrong pin in hal. From what was explained to me, the pin numbering is governed  in the .txt configuration file that is loaded on the board so, in my case i should modify that in order to have an exact numbering corespondence.

I did. When I ground the pin straight to ground the led on the EC500 gets brighter and registers in hal

After A LOT of trial and error, thanks to the absolute hero GeramyL I was able to get LinuxCNC running with the NVEM board. Turns out the fault was that I wrote the nvem-basic-config.txt to the board instead of the nvem-full-config.txt. I'm still not sure why it didn't work or why there is a basic config if there is no reason to not use the full config. Either way I'm super happy to finally be at the point where I get to learn how LinuxCNC works!

I've set up tandem Y and limit switches, and now I'm trying to get the spindle configured. The issue that I'm facing is that the analog out pin, VSO, is normally high, so 10 v with no spindle speed request or when LinuxCNC is off. When requesting half speed the voltage goes down to 5 v, and at full speed 0 v. So completely reverse of what it should be.
Is there an easy fix for this? I did some testing with lincurve, but haven't been able to figure out how to invert the signal.

Edit: Never mind! I figured out how to map it correctly using lincurve

I observe the same behavior with the NVEM board. The opposite direction always has only one Y motor in the XYYZ configuration. I don't use fw. DMA. My fw. emora-rt1052-NVEM-0.2.1.bin

Hello everyone, I've been having a problem for days that I can't resolve.
joint 2 following error
emc/task/taskintf.cc 942: Error on joint 2, command number 104
The NVEM card communicates perfectly with linuxcnc, but when I ask it to start gcode I always get this error.
Could someone please help me.