Advanced Search

Can you run this script:



and post the results here?

first make executable with:

chmod +x edrivers.txt

then

./edrivers.txt
 

Yes exactly like that! I tried looking for more information about that build specifically but couldn’t seem to find the right keyword to pull it up.

I would love more information on the design of that, the motor used, the way Linuxcnc is best incorporate to fit that, and all.

i don’t think I realized that was your video, is it?

That looks OK.
Did you use the Network Manager to set up the network?
If yes, you need to check the "use this connection for local ..... " not sure what exactly it says as i am on the phone.
That is for wired network only, IPV4 settings.
You also have a wireless network and if that connects before the Lan, it will send all trafic through wifi, if the above is not set for wired network.

Sounds like something has gone wrong with the Ethernet section of the 7I96S card.
It should be repaired/replaced under warranty, Contact Mesa or your dealer for instructions

Like this?
Also 3 axis only, X is rotating, made several configs for each pipe diameter/perimeter as there is no need for more than one revolition ever.
This made a huge border crossing "tent"? "Palapa"? Whatever that is called, it is all round pipes with 73 and 193mm diameters.

r8168-dkms drive is it installed ?

tommylight wrote:

On the PC, what does
ip a
in a terminal return?

 

---

xx@lxcnc-l540:~$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 3c:97:0e:d3:69:0e brd ff:ff:ff:ff:ff:ff
    inet 10.10.10.2/24 brd 10.10.10.255 scope global noprefixroute enp0s25
       valid_lft forever preferred_lft forever
3: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 5c:51:4f:8c:69:69 brd ff:ff:ff:ff:ff:ff
    inet 192.168.37.146/24 brd 192.168.37.255 scope global dynamic noprefixroute wlp2s0
       valid_lft 863940sec preferred_lft 863940sec

---

enp0s25 is the nic connected directly to the mesa card, wlp2s0 wifi to my home router

-
schnellmued
 

>>If you get the link LED (Yellow) on the RJ45, its not likely a firmware issue
>>but rather an Ethernet issue.
>>If you ping the card, do the green LEDs on the 7I96S count up?

no, the green LED stay off.

If i connect to the other card in my lathe and ping it the green LED start to blink

-
schnellmued

That's analog servo (7I77) setup
if you make a (different name!) pncconf configuration for a 7I76E
it will make a step/dir setup as an example

Sorry I may have explained it weirdly. It will only be a 3 axis machine. X is the pipe rolling, y is the fixed are torch holder moving, and z is the torch probing.

the torch will be fastened to fixed arm centered on the pipe. The arm itself will move the fixed torch on the y axis with a stepper motor.

I think the linear move causing the error is actually line 19, the G43 Z15 H7. I'm willing to bet your tool length + the 15 in Z is pushing you out of your envelope.

are you compiling with release or debug? idk which one but people report trouble with one

This is what my hal shows for one of my axis servos, should be stp/dir. Does this look like a step/dir or analog code.

#*******************
# AXIS X JOINT 0
#*******************

setp pid.x.Pgain [JOINT_0]P
setp pid.x.Igain [JOINT_0]I
setp pid.x.Dgain [JOINT_0]D
setp pid.x.bias [JOINT_0]BIAS
setp pid.x.FF0 [JOINT_0]FF0
setp pid.x.FF1 [JOINT_0]FF1
setp pid.x.FF2 [JOINT_0]FF2
setp pid.x.deadband [JOINT_0]DEADBAND
setp pid.x.maxoutput [JOINT_0]MAX_OUTPUT
setp pid.x.error-previous-target true
# This setting is to limit bogus stepgen
# velocity corrections caused by position
# feedback sample time jitter.
setp pid.x.maxerror 0.000500

net x-index-enable <=> pid.x.index-enable
net x-enable => pid.x.enable
net x-pos-cmd => pid.x.command
net x-pos-fb => pid.x.feedback
net x-output <= pid.x.output

# ---PWM Generator signals/setup---

setp hm2_7i76e.0.7i77.0.3.analogout1-scalemax [JOINT_0]OUTPUT_SCALE
setp hm2_7i76e.0.7i77.0.3.analogout1-minlim [JOINT_0]OUTPUT_MIN_LIMIT
setp hm2_7i76e.0.7i77.0.3.analogout1-maxlim [JOINT_0]OUTPUT_MAX_LIMIT

net x-output => hm2_7i76e.0.7i77.0.3.analogout0
net x-pos-cmd joint.0.motor-pos-cmd
net x-enable joint.0.amp-enable-out
# enable _all_ sserial pwmgens
net x-enable hm2_7i76e.0.7i77.0.3.analogena

# ---Encoder feedback signals/setup---

#setp hm2_7i76e.0.encoder.01.counter-mode 0
#setp hm2_7i76e.0.encoder.01.filter 1
#setp hm2_7i76e.0.encoder.01.index-invert 0
#setp hm2_7i76e.0.encoder.01.index-mask 0
#setp hm2_7i76e.0.encoder.01.index-mask-invert 0
#setp hm2_7i76e.0.encoder.01.scale [JOINT_0]ENCODER_SCALE

net x-pos-fb <= hm2_7i76e.0.encoder.01.position
net x-vel-fb <= hm2_7i76e.0.encoder.01.velocity
net x-pos-fb => joint.0.motor-pos-fb
net x-index-enable joint.0.index-enable <=> hm2_7i76e.0.encoder.01.index-enable
net x-pos-rawcounts <= hm2_7i76e.0.encoder.01.rawcounts

# ---setup home / limit switch signals---

net x-home-sw => joint.0.home-sw-in
net x-neg-limit => joint.0.neg-lim-sw-in
net x-pos-limit => joint.0.pos-lim-sw-in

You should be aware that Linuxcnc is limited to 3 axis look ahead. I’m not sure what that looks like for you, sounds like maybe you’re going to lock out the X axis or the design has it centered over the chuck permanently. But if you’re planning to have XYZA, then know that motion may be jerky (running similar to 3+1), and will not be coordinated with the smooth transitions you’re probably used to seeing out of a 4/5 axis plasma cutter. This will probably be problematic for cut quality.

Of course do your own simulation/testing but wanted you to be aware of the limitations software side.

Pipe:
-up to 4 feet but generally no longer than 1 foot
-up to 10” possibly
-2 roller supports bearing the weight of the pipe

The torch will move on the Y axis and the Z axis. The pipe will rotate on the X axis