Advanced Search

Hopefully I am using the correct terminology, by config I just mean associated hal / ini files

so my taig (config 2) represents the second machine using (mesa2) and my MODLATHE (config 1) was paired with my mesa1 board


Typing halcmd show param hm2*packet* only brings up error-decrement (value 1), error-increment (value 2), error-limit (value 10) and read-timeout (value 80), I do not see a total packet error parameter

Can you post the two configurations?

Are you dropping packets?

That is, what is:

hm2_7i96s.0.packet-error-total

Sounds like something very basic is broken
 

langdons wrote:

What axes does your setup have?

Perhaps having unlimited "WRAPPED_ROTARY" axes on any axis letter is a feature should be added to the source code.

I'm using XYZACW.  It's a router with an CA style head.  The W axis is an additional "C" axis rotary table, but I didn't want to use B because the kinematics file I'm using for TCP has a B axis and I don't know how to mess with the kinematic enough to make it ignore the B axis commands.  

sorry not super tech savvy, I think so though?

All of this is on a single computer with a single ethernet port (computer1)

1. I started with my mesa1 (mesa1, config1) board set at 10.10.10.10, which was working all correctly for machine1 on computer1
2. Purchased second mesa 7i96s for a second machine (mesa2, config2) for computer1, and gpio and steppers work in pncconf for config2 but when running config2, none of my GPIO work, but steppers work
3. When I run config1 on mesa2 on computer1, the GPIO works as normal
4. I tried changing mesa2 to 10.10.10.11 per my above code, and ran config2, but it did not fix the issue
5. when I run a custom halrun (per above post) with mesa2, the GPIO does work, but still doesnt work when i run config2

I never ran ip command at all except for the related code in my above post

I have thus far never had success with config2 and mesa2 gpio working under any circumstance

Hi everyone! I’m new to Linux and Orange Pi, but I’m really eager to learn and figure things out. I would be incredibly grateful for your help. Could someone write a simple, step-by-step guide—from a fresh Armbian installation to a fully working setup, including using files from a disk? I’m really trying to understand everything and I’ve already exhausted ChatGPT! Please, I would deeply appreciate any guidance you can give

Oops!

Though unlikely, it is technically possible the ISO file for your installation was (is?) corrupt.

Did you verify the SHA256 hash? (I asssume you did not, I don't verify the hash for files I download)

I once tried to install GhostBSD and it just wouldn't work.

I re-downloaded the ISO, and it worked (well, not really, but that's just because the OS itself is inherently bad IMO).

The ISO file was corrupt.

So LinuxCNC setup (2.9.4) with 7i96S initially set at IP address 10.10.10.10:

mesaflash --device  7i96s --addr 10.10.10.10 --readhmid
(works)
LinuxCNC with 10.10.10.10 IP address works and inputs work
mesaflash --device  7i96s --addr 10.10.10.10 --set ip=10.10.10.11
mesaflash --device  7i96s --addr 10.10.10.10 --reset
mesaflash --device  7i96s --addr 10.10.10.11 --readhmid
(works)
LinuxCNC with 10.10.10.11 IP address works and inputs work
mesaflash --device  7i96s --addr 10.10.10.11 --set ip=10.10.10.10
mesaflash --device  7i96s --addr 10.10.10.11 --reset
mesaflash --device  7i96s --addr 10.10.10.10 --readhmid
(works)
LinuxCNC with 10.10.10.10 IP address works and inputs work

Did nothing else (never ran ip command at all)


 

What axes does your setup have?

Perhaps having unlimited "WRAPPED_ROTARY" axes on any axis letter is a feature should be added to the source code.

I do power cycle the card each time, this is what it outputs with 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: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether 34:17:eb:c5:16:36 brd ff:ff:ff:ff:ff:ff
altname enp0s25
inet 10.10.10.1/24 scope global eno1
valid_lft forever preferred_lft forever


Keep in mind after using mesa flash to change my card's ip to 10.10.10.11, I can ping it but linuxcnc wont connect to it until I do:

sudo ip addr flush dev eno1
sudo ip addr add 10.10.10.1/24 dev eno1
sudo ip link set eno1 up
sudo ip neigh flush dev eno1

ping -c2 10.10.10.10
mesaflash --device 7i96s --addr 10.10.10.10 --readhmid

and if i restart my computer I have to redo that code, but I imagine I just need to set it as permanent, but nontheless it does not fix my issue even when linuxcnc and pncconf can communicate with the board on its new ip address


EDIT:  when I run a temporary hal instance via 
halrun
loadrt hostmot2
loadrt hm2_eth board_ip=10.10.10.11
loadrt threads name1=servo-thread period1=1000000
addf hm2_7i96s.0.read  servo-thread
addf hm2_7i96s.0.write servo-thread
start

and use getp to get the value of the pin, the limit switch DOES work

 

I've got Leadshine EL8 servo drives talking over ethercat and am trying to get sensorless homing to work.

With the help of the forums, specifically this post , I've found a way to request a specific homing mode. In the EL8 drive documentation, all the torque based sensorless homing modes are a negative number.

setp lcec.0.0.home-mode -6

is what I'm after. Other modes such as mode 35 which homes in place, works just fine so everything appears to be in order. As far as I can tell, the positive number homing modes work fine, but not the negative ones. I can't tell if this is a drive problem or a linuxcnc problem.

Would there be any reason why I can't pass a negative number? Syntax maybe?

Edit3: I have successfully changed the IP address to 10.10.10.11 and connected it back to my computer and it STILL only works in pncconf but NOT when i run my linuxcnc!!!!!

What is the host IP address set to?

The command:

ip a

will report this.

Also note that when you change the 7I96S EEPROM IP address, you must power cycle the card
or issue a reset command before the new EEPROM information is applied.
 

Most probably from the ini file and the respective values for each axis/joint and in correlation to kinematics used.
That is just off the top of my very tired head, so might want to wait for someone to confirm or deny that.
And i would not call it "virtual", it is an actual representation of the machine, but i am sure it can be argued both ways.

If you somehow find yourself here, do not use 2.9.5, use 2.9.6. More info here:
forum.linuxcnc.org/29-forum-announcement...xcnc-v2-9-6-released

Bump to remove it from "no replies" list.