Advanced Search

NOTE: Suffix 

[cli]

 required!
The suffix 

[cli]

 is required to install the command-line interface. Without this suffix the scripts referenced below will not work.

• GPIO
• Stepgen
• PWM / PDM
• Encoders

GeramyL wrote:

chrstrvs wrote:

I decided to try to install Raspberry Pi OS 64 bit, so Debian 12, and try to install the latest realtime kernel, which turned not to be that difficult when I found the correct resources.
All went well and I installed the Remora-nv component. Did a ping to the NVEM with the following result

64 bytes from 10.10.10.10: icmp_seq=35 ttl=255 time=0.169 ms
64 bytes from 10.10.10.10: icmp_seq=36 ttl=255 time=0.174 ms
64 bytes from 10.10.10.10: icmp_seq=37 ttl=255 time=0.160 ms
64 bytes from 10.10.10.10: icmp_seq=38 ttl=255 time=0.167 ms
64 bytes from 10.10.10.10: icmp_seq=39 ttl=255 time=0.185 ms
64 bytes from 10.10.10.10: icmp_seq=40 ttl=255 time=0.158 ms
64 bytes from 10.10.10.10: icmp_seq=41 ttl=255 time=0.173 ms
64 bytes from 10.10.10.10: icmp_seq=42 ttl=255 time=0.178 ms
64 bytes from 10.10.10.10: icmp_seq=43 ttl=255 time=0.151 ms
64 bytes from 10.10.10.10: icmp_seq=44 ttl=255 time=0.160 ms
64 bytes from 10.10.10.10: icmp_seq=45 ttl=255 time=0.164 ms
64 bytes from 10.10.10.10: icmp_seq=46 ttl=255 time=0.150 ms
64 bytes from 10.10.10.10: icmp_seq=47 ttl=255 time=0.208 ms
64 bytes from 10.10.10.10: icmp_seq=48 ttl=255 time=0.171 ms
64 bytes from 10.10.10.10: icmp_seq=49 ttl=255 time=0.164 ms
64 bytes from 10.10.10.10: icmp_seq=50 ttl=255 time=0.168 ms
64 bytes from 10.10.10.10: icmp_seq=51 ttl=255 time=0.183 ms
64 bytes from 10.10.10.10: icmp_seq=52 ttl=255 time=0.164 ms

So a lot better than before!

Started LinuxCNC. "Following error"...

I'm not the kind that gives up easily, but this is getting seriously annoying. I'm trying to read up on how to set up PID controller in LinuxCNC, but like everything else in Linux, it's all greek to me [img]/media/kunena/emoticons/dizzy.png[/img]

 

chrstrvs wrote:

I decided to try to install Raspberry Pi OS 64 bit, so Debian 12, and try to install the latest realtime kernel, which turned not to be that difficult when I found the correct resources.
All went well and I installed the Remora-nv component. Did a ping to the NVEM with the following result

64 bytes from 10.10.10.10: icmp_seq=35 ttl=255 time=0.169 ms
64 bytes from 10.10.10.10: icmp_seq=36 ttl=255 time=0.174 ms
64 bytes from 10.10.10.10: icmp_seq=37 ttl=255 time=0.160 ms
64 bytes from 10.10.10.10: icmp_seq=38 ttl=255 time=0.167 ms
64 bytes from 10.10.10.10: icmp_seq=39 ttl=255 time=0.185 ms
64 bytes from 10.10.10.10: icmp_seq=40 ttl=255 time=0.158 ms
64 bytes from 10.10.10.10: icmp_seq=41 ttl=255 time=0.173 ms
64 bytes from 10.10.10.10: icmp_seq=42 ttl=255 time=0.178 ms
64 bytes from 10.10.10.10: icmp_seq=43 ttl=255 time=0.151 ms
64 bytes from 10.10.10.10: icmp_seq=44 ttl=255 time=0.160 ms
64 bytes from 10.10.10.10: icmp_seq=45 ttl=255 time=0.164 ms
64 bytes from 10.10.10.10: icmp_seq=46 ttl=255 time=0.150 ms
64 bytes from 10.10.10.10: icmp_seq=47 ttl=255 time=0.208 ms
64 bytes from 10.10.10.10: icmp_seq=48 ttl=255 time=0.171 ms
64 bytes from 10.10.10.10: icmp_seq=49 ttl=255 time=0.164 ms
64 bytes from 10.10.10.10: icmp_seq=50 ttl=255 time=0.168 ms
64 bytes from 10.10.10.10: icmp_seq=51 ttl=255 time=0.183 ms
64 bytes from 10.10.10.10: icmp_seq=52 ttl=255 time=0.164 ms

So a lot better than before!

Started LinuxCNC. "Following error"...

I'm not the kind that gives up easily, but this is getting seriously annoying. I'm trying to read up on how to set up PID controller in LinuxCNC, but like everything else in Linux, it's all greek to me [img]/media/kunena/emoticons/dizzy.png[/img]

BrysonW wrote:

Hello, I'm hoping I can get some help here.  I'm beyond frustrated at this point trying to get my board flashed, Ive been at this for 8 hours at this point and am about to give up, a hammer to this ec500 I've got sitting here may be the best solution at this point.  I'm pretty sure I got my st link flashed using the CMSIS-DAP file from the repository.  But it seems no matter what I do I cannot get the pyocd command to flash the board I keep getting the Message, Import Error: No module named abc.  I know its referring to the collections library but have no idea how to fix it to move forward.  Google doesn't seem to have any idea either, other than its a default library that comes with python that seems to be missing something.  The computer I'm working on has a fresh install of linuxcnc on it, and this is the only linux machine I've got to work with here at home.  I've also tried doing all of this using my windows laptop thinking that may help.  Haven't gotten any further there, can't get the pyocd command to work on the command line there.  Im sure something is missing from the PATH variable on that machine.  There again trying to find anything useful online hasn't been much help.  I think I'm missing something simple.  I think I may have finally gotten it.  Downgrading the python version on the windows machine seemed to work.

 

python -m pip install -U pyocd
pyocd flash .\remora-rt1052.axf --target mimxrt1050_quadspi

GeramyL wrote:

chrstrvs wrote:

scotta wrote:

chrstrvs wrote:

Hey, Scott (or any volunteer)!

Have you had the time to look at my config files that are causing the following errors? I use the remora-nvem-basic config from github.com/scottalford75/Remora-NVEM/tree/main/LinuxCNC, also attached to this message.
Hi, I've had a look at your config files and they are identical to mine, and I can run with a 1000% feed override without following errors....

Now I'm really scratching my head to understand what could be going on. Do you have the serial debug output connected? It would be interesting to see if there are any issues on the board.
 

Let me explain exactly what I have done. Maybe you can spot something that I've done wrong.
- Full chip erase on NVEM using STM32 ST-LINK Utility
- Flash NVEM with Remora-NVEM-STM32-1.0.0.bin from github.com/scottalford75/Remora-NVEM/tree/main/Firmware using STM32 ST-LINK Utility
- Install Raspberry Pi OS (Legacy) 32 bit
- Install LinuxCNC and realtime Kernel according to forum.linuxcnc.org/9-installing-linuxcnc...n-raspberry-pi-3b-pi
- Copy github.com/scottalford75/Remora-NVEM/tre...es/remora-nvem-basic to /home/pi/linuxcnc/configs
- Copy github.com/scottalford75/Remora-NVEM/tre...Components/Remora-nv to /home/pi/linuxcnc/components
- Install remora-nv component using

sudo halcompile --install remora-nv.c
- Install pyocd using [code]pip3 install pyocd
- Write config to NVEM using [code]python3 upload_config.py config.txt

And that's it I think. Can you spot anything I might have done wrong?

I do not have the serial debug output connected, but I can do that if there is a guide I can follow. Do you happen to have one? [img]/media/kunena/emoticons/smile.png[/img]

[/code][/code]

scotta wrote:

[code][code][url=https://github.com/scottalford75/Remora-NVEM/tree/main/LinuxCNC/Components/Remora-nv][code][code][code]Ping response times are longer than I'm getting though, averaging around 0.17ms. Do you have a router in between the NVEM and computer?
 
No router. 2 meter cable directly from the Pi to the NVEM. Is the response time high enough to cause these errors you think?



As the response time becomes worse it changes the amount of pre-anticipation the linuxcnc software has to take in the algorithm hence PGain in order to make up for it. High ping time can cause ferror, but also can not having enough response time from the cpu on linuxcnc itself. I highly recommend you make sure your linuxcnc setup is correct and your following all recommendations by linuxcnc, also older kernels are slower and have worse response time in the real time kernel, so if linuxcnc has a timer thats supposed to go off every 1ms and the raspberrypi cpu timer goes off at 1.1ms and then the response time on the board is 0.3ms or up to 0.6ms now you are 1.13 to 1.16ms out of sync.

[/code][/code][/url][/code][/code][/code]
 

phomann wrote:

Hi Rod,
Thanks for creating the image. Last night I installed it and even managed to change the Linux GUI to Cinnamon. It’s easier for me to navigate with.
Over the weekend I’ll have a crack at configuring it for my Taig Mill.

Cheers
Peter

maghis wrote:

Ok, I'll do some reading before continuing.

As an update, it looks like I'm pretty close.
The only changes I applied so fare are to the cia402 component:
- I wait for the ECT60 to confirm homing

if (home) {
opmode = OPMODE_HOMING;
if (opmode_homing) {
controlword |= (home << 4);
}
}

- I lie with the current position to linuxcnc during homing

[code]//home states
if (opmode_homing) {
// hack
pos_fb = pos_cmd;
stat_homed = ((statusword >> 10) & 1) && ((statusword >> 12) & 1);
stat_homing = !stat_homed && !((statusword >> 10) & 1);
}


Current tested behavior is:
- I press "home all"
- joint sets cia402 home (joint.0.index-enable => cia402.0.home)
- the drive follows the homing sequence and finds the edge of the home sensor
- the drive exits the homing mode
- at that point, the next "write all" sends again the current pos_cmd and the drive moves back to the position before the homing started

I'll study homing.c - I was hoping to find a solution that didn't involve rebuilding linuxcnc (I'm running off of the 2.8.1 raspberry pi image right now).

[/code]
 

[code]pos_fb = pos_cmd;" and still noticed jumping. After looking at some Halscope traces it became apparent that the drive was being put back into cyclic position mode before the position register was cleared from homing. I made a small change in order of a few lines of code forcing the homing procedure in the drive to finish before setting the drive back to position mode. 

  // OP Mode
  // set to position mode
  if (stat_voltage_enabled && !home ) {
    opmode = OPMODE_CYCLIC_POSITION;
  }
  // set velo mode
  if (stat_voltage_enabled && !pos_mode && !home) {
    opmode = OPMODE_CYCLIC_VELOCITY;
  }
 
  // reset home command  
  if (home && (stat_homed && !stat_homed_old) && opmode_homing) {
    home = 0;  
  }

chrstrvs wrote:

scotta wrote:

chrstrvs wrote:

Hey, Scott (or any volunteer)!

Have you had the time to look at my config files that are causing the following errors? I use the remora-nvem-basic config from github.com/scottalford75/Remora-NVEM/tree/main/LinuxCNC, also attached to this message.
Hi, I've had a look at your config files and they are identical to mine, and I can run with a 1000% feed override without following errors....

Now I'm really scratching my head to understand what could be going on. Do you have the serial debug output connected? It would be interesting to see if there are any issues on the board.
 

Let me explain exactly what I have done. Maybe you can spot something that I've done wrong.
- Full chip erase on NVEM using STM32 ST-LINK Utility
- Flash NVEM with Remora-NVEM-STM32-1.0.0.bin from github.com/scottalford75/Remora-NVEM/tree/main/Firmware using STM32 ST-LINK Utility
- Install Raspberry Pi OS (Legacy) 32 bit
- Install LinuxCNC and realtime Kernel according to forum.linuxcnc.org/9-installing-linuxcnc...n-raspberry-pi-3b-pi
- Copy github.com/scottalford75/Remora-NVEM/tre...es/remora-nvem-basic to /home/pi/linuxcnc/configs
- Copy github.com/scottalford75/Remora-NVEM/tre...Components/Remora-nv to /home/pi/linuxcnc/components
- Install remora-nv component using

sudo halcompile --install remora-nv.c
- Install pyocd using [code]pip3 install pyocd
- Write config to NVEM using [code]python3 upload_config.py config.txt

And that's it I think. Can you spot anything I might have done wrong?

I do not have the serial debug output connected, but I can do that if there is a guide I can follow. Do you happen to have one? [img]/media/kunena/emoticons/smile.png[/img]

[/code][/code]

scotta wrote:

[code][code]Ping response times are longer than I'm getting though, averaging around 0.17ms. Do you have a router in between the NVEM and computer?
 
No router. 2 meter cable directly from the Pi to the NVEM. Is the response time high enough to cause these errors you think?

[/code][/code]