Remora - ethernet NVEM / EC300 / EC500 cnc board

Yes, add your end stops etc to the hal file e.g.:

net X-home remora.input.00 => joint.0.home-sw-in
net Y-home remora.input.01 => joint.1.home-sw-in
net Y-home remora.input.02 => joint.2.home-sw-in

This links the remora input hal pins to other hal pins. It's the basis of any LinuxCNC configuration. You can build quite complex logic by linking hal pins from different components.

michaelvdberghe wrote:

so i dont understand how these correspond to physical pins on the remora board itself, do you still have to add those manualy in the code.


espacialy for the x-axis i dont see where the enable pin is or where the xp+, xp-, xd+,xd- are refferencd in the code here. i realy dot get it, the documentaion is not making sence.

forum.linuxcnc.org/18-computer/44828-rem...rd?start=2200#327803

here is how the pins correspond to the physical pins. the xp and xd pins are defined in the config.txt and are turned into stepgen1,2,whatever

Hi,

I somehow have troubles with my Linuxcnc setup. I use linuxcnc together with a NVEM Board with a RT1052 on it and the Remora-RT1052-cpp. When I do normal milling I usually don't see any problems. But with complex 3D surfaces all of the axis somehow drift away. It's not much but after 15 minutes of milling it's about 0.1mm. I'm quite sure that the problem are not the motors or the drivers. I also have the correct setup (setup and hold times) for my motordrivers, I even checked them with an oscilloscope and they are fine. With the oscilloscope I could also see, that the problem is not an EMI Problem, the signals (STEP/DIR) are not noisy at all.
Is it possible, that there is a problem with the Stepgenerator? I use the (almost) latest firmware 3.13 but from what I've seen the changes after 3.13 where not related to the Stepgenerator.
If not what else could cause this problem?

Thanks Clemens

Hi Clemens,

When you say "drift away" do you mean actual measured physical position or the position reported by LinuxCNC?

The Remora firmware feeds back the steps generated to LinuxCNC, so the axis position feedback can be calculated.

Hi Scotta,

it's the actual measured position. I use e.g. G0 Z0 and measure the position with a dial gauge. The value on the dial gauge drifts away

Maybe it helps if I give you more information about my machine.
I have a 4 Axis Mill with 1X 2Y 1Z 

In the attachment I added the configuration of the machine and the configuration of the NVEM. I also added the g-code file where I can reproduce the problem

I hope this helps.
Let me know if you need something else

Thanks

Clemens

I have my Denford Triac PC running on remora and an EC500 , DM556t drivers, Probe Basic UI.Amazon cheap 23" touch screen.
I'll post my ini and hal later in the week if anyone is looking to do the same.

I'm trying to get the nvpmg to work. In halshow the inputs 1 to 9 are switching. But when the counts for the mpg are not working. Encoder.0. does not count when the mpg is moved. I have tried both input.19 -- input 25 and input 27 and 28 in the nv-mpg.hal but still nothing , should the switch be set the nv or std ? 

^^^^^
Have it sorted encoder inputs were on 20 and 21

Anyone know how to setup two inputs to trigger the motion-probe.input? 
I have a tool height setter and probe. I can only link one at a time it won't allow two input pins to trigger the motion-probe-input. I tried or2 but neither will trigger when I use or2 

My tool setter in NC , probe is NO.
So I'm using the remora.input11.not to invert the pin. But that dosnt seem to work with or 2.0.
When I use the normal remora.input.11 pin the prob works as it should triggering the motion.probe signal. Tool setter when pressed triggers only the or2 in. 

Addf or2.0 servo-thread
Net toolsetter remora.input.11.not or2.0.in0
Net Probe_tool remora.input.12 
or2.0.in1
Net probes or 2.0.out motion.probe-input

Is there a way to get this to work other than a relay

^^^^ I got this to work with classic ladder