Advanced Search

What about the other question that I had? Not sure if you noticed that?

"Do I need both lines 41 and 46?"

The original error is a watchdog bite.
This means you have a latency issue
(or the watchdog timeout is set way too fast)

I would do a ping test:

ping -c 4 [card_ip_address]
sudo ping -c 30000 -i .001 -q [card_ip_address]

Where [card_ip_address] is the IP address of the 7I92 card
(probably 10.10.10.10 or 192.168.1.121)

The last command will take 30 seconds to complete

how did you get the ECR moving in the first place? did you add the lcec_rtec.c to the lcec_main.c ? I'm a bit stuck and out of ideas

1. I can't really tell you as I generally use the newer .comp method for kinematics:
linuxcnc.org/docs/devel/html/motion/kine...erkins_comp_template

2. If I need to use the classic C file method I modify one of the built in kinematic files.

3. If I really wanted to figure it all out then I would look for an installed kinematic file (eg 'scarakins.c') and look where that pops up in the source code and copy the lines in the relevant files and replace 'scarakins.c' with my .c file (likely '/src/emc/kinematic/meson.build' and '/src/Makefile'):

 
 

I think in .hal there should be:
setp cia402.0.csp-mode 1
setp cia402.0.pos-scale 800

 


setp cia402.1.csp-mode 1
setp cia402.1.pos-scale 800

 

 

Hello community, I have tried github.com/jzolee/HAL2UDP, an external step generator: ESP32 for 3-axis in a single ESP32. But, I want to use individual ESP32 for individual motors to have extra I/O pins that can be used for other purposes.
See the image attached below for your understanding.
  
Please let me know if anyone has any idea.

Thankyou

The problem with `ethercat slaves` is presumably because your kernel is running a different version of the EtherCAT code than the one that the `ethercat` command-line tool expects. If you'd recently installed an update without rebooting, then I'd expect to see the kernel version lower than the command-line version, but that's not what I see here. So that's kind of odd. The best fix would be to update and reboot. But...

IIRC they recently changed the keys for the OpenSUSE build server. I *think* the instructions in forum.linuxcnc.org/ethercat/45336-etherc...ep-by-step?start=290 should fix this. Try that, and if it runs successfully then reboot and see if everything works?

2.9.3 is a branch inside the git tree that you cloned to your local machine. Default branch is 'master' ie currently 2.10.xx.
To compile 2.9.3 you need to switch to the '2.9' branchand then recompile

I had to ask because I don't understand the core of electronics at all, my level is that I know how to connect the wires, set the pid and so on.. I thought that maybe by chance there is some limitation related to the 7i96s in terms of the digital signals it would give to this driver.

Why do you think it won't be compatible? I don't see anything to worry about. You can just buy an extra board for the encoders and you will be able to close the loop in LinuxCNC

sry my question was ambigous.

I have already built linuxcnc to RIP

the question was how to put this extra kinematic into the build process so that it is recompiled linked and put in the right place with make

Hi Aciera,
I could not do with halcompile, so I tried build from sources.
Building from source is faster than my expect. But it is LCNC version 2.10.xxx
I checked all branches on github, could not find stable version 2.9.3
Please advise. Thank you.

Yes it is used/owned by a business (my employer). (Yes I get to "play" with Linuxcnc as part of my day-job.) We also have 3 other cnc routers here that I converted to running Linuxcnc. I would consider the machine's we have running Linuxcnc to be "light duty" and they are mainly used for carving and engraving, and they can do that much faster than our large heavy duty routers that we use for milling out parts. The big heavy machines, are mostly all Fanuc controlled.

The CAD/CAM software I use is called Enroute. It's a package geared more toward the woodworking/sign making industries. I also use FreeCAD a little to do some things that Enroute can't.

yes, they work great on mach3, but linukcnc is safer for me because it won't ``continue working'' if something bad happens, even though these drivers have a certain encoder error tracking protection. maybe it's easiest for me to try, because I already have the 7i96s and the configuration on that earlier lathe, so let me try. I would be able to connect, what worried me the most was that maybe the frequency step/dir signals or whatever with the 7i96s are not compatible with this driver.

Masiwood123 wrote:

I think in that case it will cost me the same as the combination of 7i96s+7i77.

See:
7i97T
7i92TM+7i77
7i92TM+7i85+7i83