Advanced Search

OK that's curious. How did you get the pinout information if not via mesaflash?

PING 10.10.10.10 (10.10.10.10) 56(84) bytes of data.
64 bytes from 10.10.10.10: icmp_seq=1 ttl=64 time=0.129 ms
64 bytes from 10.10.10.10: icmp_seq=2 ttl=64 time=0.165 ms
64 bytes from 10.10.10.10: icmp_seq=3 ttl=64 time=0.534 ms
64 bytes from 10.10.10.10: icmp_seq=4 ttl=64 time=0.144 ms
64 bytes from 10.10.10.10: icmp_seq=5 ttl=64 time=0.564 ms
64 bytes from 10.10.10.10: icmp_seq=6 ttl=64 time=0.583 ms
64 bytes from 10.10.10.10: icmp_seq=7 ttl=64 time=0.570 ms
64 bytes from 10.10.10.10: icmp_seq=8 ttl=64 time=0.544 ms
64 bytes from 10.10.10.10: icmp_seq=9 ttl=64 time=0.549 ms
64 bytes from 10.10.10.10: icmp_seq=10 ttl=64 time=0.542 ms
64 bytes from 10.10.10.10: icmp_seq=11 ttl=64 time=0.161 ms
64 bytes from 10.10.10.10: icmp_seq=12 ttl=64 time=0.543 ms
64 bytes from 10.10.10.10: icmp_seq=13 ttl=64 time=0.401 ms
64 bytes from 10.10.10.10: icmp_seq=14 ttl=64 time=0.439 ms
64 bytes from 10.10.10.10: icmp_seq=15 ttl=64 time=0.547 ms
64 bytes from 10.10.10.10: icmp_seq=16 ttl=64 time=0.153 ms
64 bytes from 10.10.10.10: icmp_seq=17 ttl=64 time=0.175 ms
^C
--- 10.10.10.10 ping statistics ---
17 packets transmitted, 17 received, 0% packet loss, time 16378ms
rtt min/avg/max/mdev = 0.129/0.396/0.583/0.184 ms

Yes I can ping.
Also linuxcnc works fine except for the missing axis's.

Can you ping the card 7I92T?

( ping 10.10.10.10 )
 

ip address is set to 10.10.10.10

just says "no ethernet board found"

ip a shows the following:

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 88:05:69:25:27:36 brd ff:ff:ff:ff:ff:ff
altname enp0s31f6
inet 10.10.10.11/8 brd 10.255.255.255 scope global noprefixroute eno1
valid_lft forever preferred_lft forever
inet6 fe80::5d1b:283a:369d:3bfe/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: wlp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 5a:d9:05:7b:e7:38 brd ff:ff:ff:ff:ff:ff permaddr f4:7b:09:ca:e0:9a

After six weeks of doing everything wrong a few times and being graciously corrected by everyone in the community my franken-build Pi 5 debian is working very well.

I'm about to start clean and do everything as has been documented in this thread without my own improvisations which I think got me little except the motivation to learn everything necessary to fix all the things I broke.

I wanted to make sure I'm starting with the latest of Rod's builds and I think it is this from the Google-Driver:

   rpi-5-debian-bookworm-6.6.54-rt39-arm64-ext4-2024-11-06-2037_qtpyvcp_stable_networkmanager.img.xz

The one on the Downloads page is still:

   rpi-5-debian-bookworm-6.1.61-rt15-arm64-ext4-2023-11-17-1520.img.xz

I'm pretty sure I want the one from Nov 2024 instead of Nov 2023.

Is there an even newer one?


 

Maybe you have a old copy of mesaflash
try this

mesaflash --device ethernet --addr [ip_addr] --rpo 0x1000


What IP address is the 7I92t card set for and what does:

ip a

report?

It just says board not found.

TLDR: get the largest harmonic reducer you can afford and build a 4th axis around it.

The two (basic) issues with rotary axes are backlash and compliance.  Eliminating both gets very expensive.

A planetary reducer - especially a low-cost one - will have backlash, and so will a worm drive.  Both mechanisms are generally suitable for uni-directional indexing, but bi-directional movement will result in artifacts or dimensional errors.  Features machined from multiple orientations will not line up.

Worse still, if off-centerline cutting forces are applied, the part can rotate even with no commanded movement.  Imagine drilling straight down along the centerline - there's no rotational force on the rotary axis so all goes fine.  However, if you try to drill holes offset from the rotational axis the cutting forces will cause the rotary axis to move as the force takes up the mechanical backlash.  Same thing happens when side-milling above the centerline.

This problem can be reduced or eliminated by adding a brake to the rotary axis directly on the output shaft (platter).  A motor brake (stepper or servo) will stop back-driving, but not eliminate cutting forces taking up the backlash.

The above may not be an issue for light machining close to the centerline... but even very low-load engraving will result in artifacts due to backlash.  My mill came with a worm drive 4th axis and I quickly abandoned it due to the backlash issue.

Harmonic reducers eliminate backlash (more or less), and have come down in price dramatically in the past 4-5 years.  The downside with harmonic reducers is compliance.  Due to the nature of the flexible strain wave gear/cup, machining which imposes a high rotational force can cause the flex gear to twist under load.  Once the force is removed the reducer 'springs back' in to the desired position, but this flex can cause tool chatter or dimensional errors.  Generally speaking, a bigger reducer will flex less than a smaller one under the same rotational force since the larger flex cup/gear is stiffer.

As with planetary or worm drives, a suitable brake will stop chatter or flex in a harmonic reducer.  But a brake cant work during continuous rotational machining.

For light(ish) machining that isn't really far off the centerline, harmonic reducers are an easy solution to the backlash problem.  I now have a 32mm (through-bore) harmonic drive in a 6" diameter rotary axis and it works quite well.  But if I had wanted a 8" or larger mechanism - or I had a more powerful mill using larger tools - I would probably have gone up to a 40mm (or larger) reducer to increase the off-centerline stiffness.

At the upper end of rotary axis mechanisms are cam-roller drives and direct drives (torque motors).  Cam-roller mechanisms, especially preloaded versions, have zero backlash and are extremely stiff, fast, and accurate.  Direct drive motors are also excellent, but may not be as fast as cam-roller drives unless wound for higher speed (at the potential loss of holding torque).

Both are eye-wateringly expensive and are not as common on the surplus market as harmonic reducers.

Hey Scotta,I saw that you recommended flashing the ST-Link with CMSIS-DAP firmware. Just out of curiosity, I tried flashing it using the ST-Link, and it worked! In fact, it was smoother than the CMSIS-DAP probe I bought. The reason is, the CMSIS-DAP probe needed some extra configuration to work on Windows, while the ST-Link just worked out of the box. So, for anyone thinking of flashing the firmware, I’d suggest using the ST-Link V2 with PyOCD directly.

The 7I85 has built in 120 Ohm termination when used is RS-422 (line driver) mode.
no additional termination is needed.

1. Should be OK, just get a good quality one like MeanWell or Delta
2. TTL encoders should work as is with 7i85, so should glass scales rated at 5V, incremental types that is, and both differential and single ended also work on most Mesa cards.

Hmm, possibly damaged 7I92T  or 7I77?

If you unplug the 7I92 and 7I77 (with all power off), re-power the 7I92T, what does:

mesaflash --device 7i92t --addr [ip_addr] --rpo 0x1000

report?

(ip_addr = 192.168.1.121 or 10.10.10.10 depending on 7I92T jumpering)

Ok thank you.

I think I am gonna look into precise switch because I know nothing about encoder...

I don't even know if my stepper have an encoder in them, I think it is optional (?).

I run closed loop 48v stepper with CL57T drivers on a Mesa 7ixx.

Thank you for the info.

I am trying a piece ATM with skewkins (linked above), it look to work fine too.

Less skewing options than matrixkins (I think) but I only needed X/Y skew.