Remora - ethernet NVEM / EC300 / EC500 cnc board

More
18 Sep 2024 20:40 #310413 by scotta
Hi, unfortunately no. The QEI is for the STM32 based boards, the QDC for the RT1052. These refer to the decoding circuits integrated into the MCUs. The QDC has the capability to count a single channel, but the current software implementation cannot take advantage it.

Please Log in or Create an account to join the conversation.

More
18 Sep 2024 20:53 #310415 by Murphy
How hard is it to get the single A pulse and Z index working for the spindle? Is it going to be future update ?
​​​​​​
​​​​​​

Please Log in or Create an account to join the conversation.

More
18 Sep 2024 23:09 #310419 by cakeslob
for user xaxexa, when you say one pulse output , are you referring to it as only an A channel (x pulse/revolution) or do you mean it is a single pulse like an index channel where 1 pulse/revolution ?
if it is the index channel, you could probably implement it.

Echo to Murphy, we could benefit from having the option for only A/Z as it seems common for lathe users, , Myself and other users are finding increasing need for a non quadratic option so the encoder module can be used for MPG. Using Encoder module vs DIgitial IO for an MPG is a cleaner hal file, but also using digital IO for MPG uses 12% of the available inputs on the SPI version
The following user(s) said Thank You: Murphy

Please Log in or Create an account to join the conversation.

More
20 Sep 2024 03:06 #310486 by xaxexa
look, the square encoder gives us the direction and frequency, you can also calculate the angle and so on, depending on the accuracy of the encoder, the Z channel allows you to refer to the position of something, for the MPG Z is not needed, for stepper motor feedback, I would choose a diver with encoder support, and now I want feedback of the spindle speed, in theory it can be implemented using A encoder channel, or the Z channel theoretically could also give such functionality, I don’t need to cut threads, just feedback of revolutions per minute

Please Log in or Create an account to join the conversation.

More
20 Sep 2024 14:31 #310517 by xaxexa
Today I was sitting with a frequency generator :)
my notes, if you enter only channel A in txt, the counter counts 0,1,0,1,0,1 instead of 0,1,2,3,4,5, there is no acceleration, and velocity = 0
if you connect A and B to the same pin, then at a low frequency the counter is 0, apparently the board understands that the pulse comes at the same time, if you increase the frequency above 1 kHz, errors begin, and the counter begins to increase or decrease non-linearly, well, it seems the simplest thing is to exclude channel B from the calculation, but I don't have the knowledge at all to write such a commit... :)

and I also need to use the PRU encoder module, not just an encoder, right?

Please Log in or Create an account to join the conversation.

More
29 Sep 2024 19:32 #311041 by aDm1N
The fact that I couldn't flash the board is because it is defective for whatever reason. Is on the way back now. Now I'm wondering what happens next. Of course, getting a new NVEM would work. or would an EC300 or EC500 be a better choice? A standard MPG should be connected with individual cables, so an NVEM is probably easier at first. Mesa cards are hard to come by right now, or much more expensive. If you were faced with a choice right now, what would your decision be?

Please Log in or Create an account to join the conversation.

More
02 Oct 2024 15:22 - 02 Oct 2024 15:24 #311181 by xaxexa
help me figure it out, I'm still trying to make a frequency counter on one wire, with a QDC module, I found a solution, now in the variable pv0 I see a growing counter, with an adequate frequency exactly the same as on the frequency generator, I took the Linux module "counter", removed everything unnecessary from it, connected pv0 with raw_counts I see the value velocity, but it is with an accuracy of 1 kilohertz, how to reduce it to 1 hertz??? is this related to the servo thread refresh rate?

Warning: Spoiler!
Last edit: 02 Oct 2024 15:24 by xaxexa.

Please Log in or Create an account to join the conversation.

More
02 Oct 2024 16:10 #311187 by xaxexa
figured it out, yes it is connected with the servo thread speed... I will continue to do it...
The following user(s) said Thank You: Murphy

Please Log in or Create an account to join the conversation.

More
07 Oct 2024 08:50 #311475 by xaxexa
Check github pls :-) remora cpp

Please Log in or Create an account to join the conversation.

More
08 Oct 2024 21:04 #311611 by aDm1N
So, the new board has arrived (NVEM). Soldered the cable and tried it quickly with Windows. It worked and I get an answer from 10.10.10.10

Now let's move on.
C:\Users\adm1n\Nextcloud\LinuxCNC_Minidrehbank\Remora-RT1052-cpp\Firmware>pyocd list
  #   Probe/Board             Unique ID                                          Target
------------------------------------------------------------------------------------------------
  0   ARM DAPLink CMSIS-DAP   070000811a5a5bb50000000001ef41eca5a5a5a597969908   ✔︎ stm32f103rb
      NUCLEO-F103RB

C:\Users\adm1n\Nextcloud\LinuxCNC_Minidrehbank\Remora-RT1052-cpp\Firmware>pyocd flash remora-rt1052-3.1.3.bin --target mimxrt1050_quadspi -v
0005355 W STLink, CMSIS-DAPv2 and PicoProbe probes are not supported because no libusb library was found. [common]
0007141 I Target type is mimxrt1050_quadspi [board]
0007232 I DP IDR = 0x0bd11477 (v1 MINDP rev0) [dap]
0007310 I AHB-AP#0 IDR = 0x04770041 (AHB-AP var4 rev0) [discovery]
0007357 I AHB-AP#0 Class 0x1 ROM table #0 @ 0xe00fd000 (designer=00e:NXP part=88c) [rom_table]
0007373 I [0]<e00fe000:ROM class=1 designer=43b:Arm part=4c8> [rom_table]
0007373 I   AHB-AP#0 Class 0x1 ROM table #1 @ 0xe00fe000 (designer=43b:Arm part=4c8) [rom_table]
0007404 I   [0]<e00ff000:ROM class=1 designer=43b:Arm part=4c7> [rom_table]
0007404 I     AHB-AP#0 Class 0x1 ROM table #2 @ 0xe00ff000 (designer=43b:Arm part=4c7) [rom_table]
0007433 I     [0]<e000e000:SCS v7-M class=14 designer=43b:Arm part=00c> [rom_table]
0007436 I     [1]<e0001000:DWT v7-M class=14 designer=43b:Arm part=002> [rom_table]
0007436 I     [2]<e0002000:FPB v7-M class=14 designer=43b:Arm part=00e> [rom_table]
0007452 I     [3]<e0000000:ITM v7-M class=14 designer=43b:Arm part=001> [rom_table]
0007468 I   [1]<e0041000:ETM M7 class=9 designer=43b:Arm part=975 devtype=13 archid=4a13 devid=0:0:0> [rom_table]
0007484 I   [2]<e0042000:CTI CS-400 class=9 designer=43b:Arm part=906 devtype=14 archid=0000 devid=40800:0:0>
 [rom_table]
0007499 I [1]<e0040000:TPIU M7 class=9 designer=43b:Arm part=9a9 devtype=11 archid=0000 devid=ca1:0:0> [rom_table]
0007499 I [2]<e0043000:TSGEN class=15 designer=43b:Arm part=101> [rom_table]
0007515 I IMXRT Boot Mode: Internal Boot [target_imxrt]
0007531 I CPU core #0: Cortex-M7 r1p1, v7.0-M architecture [cortex_m]
0007547 I   Extensions: [DSP, FPU, FPU_DP, FPU_V5, MPU] [cortex_m]
0007547 I   FPU present: FPv5-D16-M [cortex_m]
0007574 I 4 hardware watchpoints [dwt]
0007579 I 8 hardware breakpoints, 1 literal comparators [fpb]
0007642 I Loading C:\Users\adm1n\Nextcloud\LinuxCNC_Minidrehbank\Remora-RT1052-cpp\Firmware\remora-rt1052-3.1.3.bin [load_cmd]
0007816 I IMXRT Boot Mode: Internal Boot [target_imxrt]
0007831 I IMXRT Boot Device: 0 [target_imxrt]
[==================================================] 100%
0083752 I IMXRT Boot Mode: Internal Boot [target_imxrt]
0083763 I IMXRT Boot Device: 0 [target_imxrt]
0083889 I Erased 393216 bytes (6 sectors), programmed 358656 bytes (1401 pages), skipped 0 bytes (0 pages) at 4.60 kB/s [loader]

Please Log in or Create an account to join the conversation.

Time to create page: 0.252 seconds
Powered by Kunena Forum