Remora - ethernet NVEM / EC300 / EC500 cnc board
On the picture you reposted there is no indication which remora.input is which. That's why I've used the one I've attached. Over there it's clear that for example estop input is remora.input.04, probe is input.05 etc. So the INP3 (on your picture) is really input.06.
It is correct as I've check it.
Please Log in or Create an account to join the conversation.
The problem is that it is the wrong board, using those pins in the config will cause problems for other users who use them. If all you need is a reference to which remora pin goes where, you can use the config file you loaded to the board. The part you need may be correct, but the pin assignment is not for the same board. If you use the STM32 pin names on your rt1052 board it will cause issues.
github.com/scottalford75/Remora-RT1052-c...xCNC/nvem-rt1052.txt
Ill even do you one better, here is a trimmed down list of the inputs/outputs that you can use that wont cause problems for other users.
"Board": "NVEM",
------------------- INPUTS ---------------------------------------
--------------------------------------------------------------------
"Databit = 0" = remora.input.00
-------------------------------------------------------
"Pin": "P3_26" = RT1052 hardware pin number
-------------------------------------------------------
"Comment": "FHA" = Board Pin label
-------------------------------------------------------
"Comment": "FHA",
"Pin": "P3_26",
"Mode": "Input",
"Data Bit": 0,
"Comment": "FHB",
"Pin": "P4_30",
"Mode": "Input",
"Data Bit": 1,
"Comment": "SRO",
"Pin": "P3_19",
"Mode": "Input",
"Data Bit": 2,
"Comment": "SRJ",
"Pin": "P4_20",
"Mode": "Input",
"Data Bit": 3,
"Comment": "IN01",
"Pin": "P4_26",
"Mode": "Input",
"Data Bit": 4,
"Comment": "IN02",
"Pin": "P4_27",
"Mode": "Input",
"Data Bit": 5,
"Comment": "IN03",
"Pin": "P4_21",
"Mode": "Input",
"Data Bit": 6,
"Comment": "IN04",
"Pin": "P4_24",
"Mode": "Input",
"Data Bit": 7,
"Comment": "IN05",
"Pin": "P4_28",
"Mode": "Input",
"Data Bit": 8,
"Comment": "IN06",
"Pin": "P4_25",
"Mode": "Input",
"Data Bit": 9,
"IN07",
"Pin": "P4_29",
"Mode": "Input",
"Data Bit": 10,
"Comment": "IN08",
"Pin": "P4_23",
"Mode": "Input",
"Data Bit": 11,
"Comment": "IN09",
"Pin": "P4_31",
"Mode": "Input",
"Data Bit": 12,
"Comment": "IN10",
"Pin": "P3_18",
"Mode": "Input",
"Data Bit": 13,
"Comment": "IN11",
"Pin": "P3_21",
"Mode": "Input",
"Data Bit": 14,
"Comment": "IN12",
"Pin": "P3_20",
"Mode": "Input",
"Data Bit": 15,
"Comment": "CIN",
"Pin": "P4_18",
"Mode": "Input",
"Data Bit": 16,
"Comment": "XIN",
"Pin": "P4_17",
"Mode": "Input",
"Data Bit": 17,
"Comment": "YIN",
"Pin": "P4_16",
"Mode": "Input",
"Data Bit": 18,
"Comment": "ZIN",
"Pin": "P4_15",
"Mode": "Input",
"Data Bit": 19,
"Comment": "AIN",
"Pin": "P4_14",
"Mode": "Input",
"Data Bit": 20,
"Comment": "X100IN",
"Pin": "P4_13",
"Mode": "Input",
"Data Bit": 21,
"Comment": "X10IN",
"Pin": "P4_12",
"Mode": "Input",
"Data Bit": 22,
"Comment": "EP",
"Pin": "P4_11",
"Mode": "Input",
"Data Bit": 23,
"Comment": "INDEX",
"Pin": "P3_22",
"Mode": "Input",
"Data Bit": 24,
"Comment": "WHA",
"Pin": "P3_16",
"Mode": "Input",
"Data Bit": 25,
"Comment": "WHB",
"Pin": "P3_17",
"Mode": "Input",
"Data Bit": 26,
------------------------OUTPUTS--------------------------
---------------------------------------------------------
"Databit = 0" = remora.output.00
-------------------------------------------------------
"Pin": "P4_01" = RT1052 hardware pin number
-------------------------------------------------------
"Comment": "OT01" = Board Pin label
---------------------------------------------------------
"Comment": "OT01",
"Pin": "P4_01",
"Mode": "Output",
"Data Bit": 0
"Comment": "OT02",
"Pin": "P4_02",
"Mode": "Output",
"Data Bit": 1
"Comment": "OT03",
"Pin": "P4_03",
"Mode": "Output",
"Data Bit": 2
"Comment": "OT04",
"Pin": "P4_04",
"Mode": "Output",
"Data Bit": 3
"Comment": "OT05",
"Pin": "P4_05",
"Mode": "Output",
"Data Bit": 4
"Comment": "OT06",
"Pin": "P4_06",
"Mode": "Output",
"Data Bit": 5
"Comment": "OT07",
"Pin": "P4_07",
"Mode": "Output",
"Data Bit": 6
"Comment": "OT08",
"Pin": "P4_08",
"Mode": "Output",
"Data Bit": 7
"Comment": "OT09",
"Pin": "P4_09",
"Mode": "Output",
"Data Bit": 8
"Comment": "OT10",
"Pin": "P4_10",
"Mode": "Output",
"Data Bit": 9
Please Log in or Create an account to join the conversation.
- AlessandroEmm
- Offline
- New Member
- Posts: 18
- Thank you received: 0
Thanks again
Alessandro
Please Log in or Create an account to join the conversation.
Please Log in or Create an account to join the conversation.
- AlessandroEmm
- Offline
- New Member
- Posts: 18
- Thank you received: 0
net spindle-cw remora.output.09
loadrt pwmgen output_type=1
loadrt scale count=1
loadrt lowpass count=1
loadrt abs count=1
addf scale.0 servo-thread
addf lowpass.0 servo-thread
addf abs.0 servo-thread
setp scale.0.gain 0.00416666667
net spindle-cmd-rpm spindle.0.speed-out => scale.0.in
net spindle-cmd-rpm-abs scale.0.out => abs.0.in
net spindle-speed-DAC abs.0.out => remora.SP.0
net spindle-cw <= spindle.0.forward
Please Log in or Create an account to join the conversation.
I have an NVEM v5. The stlink is to be delivered tomorrow. I think after everything I've read here, I'll be able to flash the firmware. I am currently building a small lathe into CNC. The spindle drive becomes an AC servo. I still have to see that I get it connected with step/dir, should be feasible. Then the machine gets another MPG, no problem either. But I still have an encoder only with a/b without index. Do I have any connections left for this? Does thread cutting work with it?
Encoder:
de.aliexpress.com/item/1005006363767037....gatewayAdapt=glo2deu
Servo:
de.aliexpress.com/item/1005006659782702....gatewayAdapt=glo2deu
Please Log in or Create an account to join the conversation.
// calculate the output value
vel_cmd = pgain * error + data->cmd_d[i] * ff1gain;
Hey Scott, sorry to bother you with this, but can you explain this a bit more? Im wondering how we can just do a math to figure it out. Ive been bruteforcing pid stuff for a few days but i cant get my overshoot down to less than 5 steps, but this question comes up on discord a bunch also.
using a 1mm distance for the example to make it easier(?)
ff1 * cmd_d + error * pgain = velcmd
ff1 = number in ini file
cmd_d = old pos - new data? this is the D ?
error = ?
pgain = ini number
edit, holy shit it my issue was a typo this whole time.
my issue is typo related, but the question still stands, is there a math way to figure it out?
Please Log in or Create an account to join the conversation.
The stepgen "PID" was adopted from the PID component. There is some auto tuning code in there but I've not looked closely at it.
github.com/LinuxCNC/linuxcnc/blob/master...hal/components/pid.c
Please Log in or Create an account to join the conversation.
cnc@MiniDrehbank:~$ pyocd list
# Probe/Board Unique ID Target
--------------------------------------------------------
0 STM32 STLink 260046001033353739303541 n/a
cnc@MiniDrehbank:~$ pyocd list
# Probe/Board Unique ID Target
--------------------------------------------------------
0 STM32 STLink 40001400020000415246524E n/a
cnc@MiniDrehbank:~/linuxcnc/Remora-RT1052-cpp/Firmware$ pyocd flash remora-rt1052-3.1.3.bin --target mimxrt1050_quadspi
0001513 C STLink error (9): Get IDCODE error [__main__]
Please Log in or Create an account to join the conversation.
pyocd.io/docs/debug_probes.html
"Recent STLink firmware versions will only allow access to STM32 targets. If you are using a target from a silicon vendor other than ST Micro, please use a different debug probe."
If you have a couple of probes you can always flash one with the following firmware.
github.com/scottalford75/Remora-RT1052/tree/main/CMSIS-DAP
Please Log in or Create an account to join the conversation.