Remora - ethernet NVEM cnc board

Hi, I am currently doing a project using EC500_V5 with remora firmware. Right now I am facing an issue. All my input pins are active low state. One of my sensor (proximity sensor) has an active high output. Is is possible to change the state of a particular input pin to active high?  -Aravind

Thanks for the response. 
Is there any method in which I can do some simple setting in the software/configuration file or on the controller board (EC500_V5) hardware for making some input pins as active high

- Aravind

assuming i understand what you mean, the input still works and changes state? but its just backwards?

you can invert the input in your config file, or you can use the hal pin remora.in.xx_not or something like that


are you saying the input doesnt change state? like an NPN/PNP thing? you probably need a resistor somewhere

assuming i understand what you mean, the input still works and changes state? but its just backwards?
you can invert the input in your config file, or you can use the hal pin remora.in.xx_not or something like that
are you saying the input doesnt change state? like an NPN/PNP thing? you probably need a resistor somewhere

Hi cakeslob,
Well the input state doesnot change. I am getting +24V at the input pins and when I connect it with the COM- that pin shows a high signal. So I assume that the pins are in active low state. For my pnp proximity sensor, I connect the COM+ to the positive (brown wire), COM- to the negative (blue wire) and I connect the black output wire to the input pin. When a metal piece comes near the sensor I get 24V at that black output wire.
In the actual schematic diagram of EC500_V5 shared by the supplier, it is given the same way to connect.

So, I thought that there will be any kind of adjustment that can be done on the board (like any jumper pins) or any setting in the files like ec500-rt1052.txt can make few pins to the active high state.

- Aravind

Aravind wrote:

For my pnp proximity sensor, I connect the COM+ to the positive (brown wire), COM- to the negative (blue wire) and I connect the black output wire to the input pin. When a metal piece comes near the sensor I get 24V at that black output wire.

You are right, but you not understand how input works.
There is serial resistor and LED diode (built in optocoupler) connected to +24V and input pin. If you connect input to GND, the circuit is closed, and optocoupler output changes state.
You must connect an resistor to input and GND, the value must be as low for optocoupler works and as high for protect proximity sensor output. Try 1k (1000 Ohm). Now, when sensor not works, the input is active, but when sensor works, it pulls input to +24V and input stay not active.

Thanks for the great work on Remora,

But I seem to have found a slightly strange bug. Using purely the example configs (as attached) I have an interesting behaviour.

If I move an axis (only tested with X so far as my 'machine' is currently just electronics, no motion assembly) beyond a certain point in either direction from 'home' (whatever it was at poweron), the axis completes its movement, stops for ~1s, then begins endlessly 'walking' in the negative direction.

I have verified this isn't noise. It is full-depth pulses on the step/dir pins. Scope capture attached for both.

The 'walking' stops if the 'machine power' button is off, or if in e-stop. However it will resume on reactivation of the machine. It only stops if you bring the axis back close to zero in LinuxCNC.

During this behaviour, the DRO in LinuxCNC is not moving, this is definitely happening within Remora rather than LCNC itself.
 

Hi, i have a new EC500 board (see attached picture from chip) and trying to use it with linuxcnc and remora.

After some troubles to flash it with a converted ST-Link-V2, it seems to be that i successfully flashed it to remora with the raspberry pico under windows. See output below: (Under Linux (standard LinuxCNC build), I cannot establish a connection with the Pico CMSIS-DAP und linux.

PS C:\Users\...\Desktop> pyocd flash ./remora-rt1052-3.1.2.bin --target mimxrt1050_quadspi -v
0000693 I Target type is mimxrt1050_quadspi [board]
0000726 I DP IDR = 0x0bd11477 (v1 MINDP rev0) [dap]
0000749 I AHB-AP#0 IDR = 0x04770041 (AHB-AP var4 rev0) [discovery]
0000760 I AHB-AP#0 Class 0x1 ROM table #0 @ 0xe00fd000 (designer=00e:NXP part=88c) [rom_table]
0000766 I [0]<e00fe000:ROM class=1 designer=43b:Arm part=4c8> [rom_table]
0000766 I   AHB-AP#0 Class 0x1 ROM table #1 @ 0xe00fe000 (designer=43b:Arm part=4c8) [rom_table]
0000771 I   [0]<e00ff000:ROM class=1 designer=43b:Arm part=4c7> [rom_table]
0000772 I     AHB-AP#0 Class 0x1 ROM table #2 @ 0xe00ff000 (designer=43b:Arm part=4c7) [rom_table]
0000780 I     [0]<e000e000:SCS v7-M class=14 designer=43b:Arm part=00c> [rom_table]
0000784 I     [1]<e0001000:DWT v7-M class=14 designer=43b:Arm part=002> [rom_table]
0000787 I     [2]<e0002000:FPB v7-M class=14 designer=43b:Arm part=00e> [rom_table]
0000790 I     [3]<e0000000:ITM v7-M class=14 designer=43b:Arm part=001> [rom_table]
0000794 I   [1]<e0041000:ETM M7 class=9 designer=43b:Arm part=975 devtype=13 archid=4a13 devid=0:0:0> [rom_table]
0000801 I   [2]<e0042000:CTI CS-400 class=9 designer=43b:Arm part=906 devtype=14 archid=0000 devid=40800:0:0> [rom_table]
0000805 I [1]<e0040000:TPIU M7 class=9 designer=43b:Arm part=9a9 devtype=11 archid=0000 devid=ca1:0:0> [rom_table]
0000807 I [2]<e0043000:TSGEN class=15 designer=43b:Arm part=101> [rom_table]
0000811 I IMXRT Boot Mode: Internal Boot [target_imxrt]
0000818 I CPU core #0: Cortex-M7 r1p1, v7.0-M architecture [cortex_m]
0000819 I   Extensions: [DSP, FPU, FPU_DP, FPU_V5, MPU] [cortex_m]
0000819 I   FPU present: FPv5-D16-M [cortex_m]
0000827 I 4 hardware watchpoints [dwt]
0000831 I 8 hardware breakpoints, 1 literal comparators [fpb]
0000846 I Loading C:\Users\...\Desktop\remora-rt1052-3.1.2.bin [load_cmd]
0000982 I IMXRT Boot Mode: Internal Boot [target_imxrt]
0001028 I IMXRT Boot Device: 0 [target_imxrt]
100%
0031426 I IMXRT Boot Mode: Internal Boot [target_imxrt]
0031428 I IMXRT Boot Device: 0 [target_imxrt]
0031545 I Erased 196608 bytes (3 sectors), programmed 147968 bytes (578 pages), skipped 0 bytes (0 pages) at 4.72 kB/s [loader]
PS C:\Users\...\Desktop>

---

My problem is that although it looks like the flashing worked, I can't establish a connection over the network. Ping 10.10.10.10, no response. I have already tried different ways to configure the manual IP on the linuxCNC pc.Can you please help me? What else can I do? Thank you in advance.    

I think it will not work because it is a MIMXRT1052CVL5B board, right? Is there a way that i can flash it correctly? With "pyocd list --targets" i can only find "MIMXRT1052xxxxB_quadspi", but this will not work.

Now I tried to flash the NON-CPP version "remora-rt1052-EC500-beta.bin" and now I get an network connection. Why is it then not possible to flash the newer C++ version? 

Not too sure why you can't establish connection with the CPP version. I haven't had issues with that before.

When I did have issues with the board I found doing a full chip erase and then reflash solved my problems.
Using pyocd in linux

pyocd erase --chip --target mimxrt1050_quadspi

If you want to use your pico probe in linux there is a step in the guide I wrote to get it working. I have tested Pico CMSIS-DAP and had no issues.

I also did a full chip erase before. Where can I find your guide? Thanks a lot in advance.

Top of page 165