Advanced Search

This is the result for the 7i92t unplugged from the 7i77.

~$ mesaflash --addr 10.10.10.10 --device=ETHER --rpo 0x1000
0001FFFF

I tried something different here with the following result.

~$ mesaflash --addr 10.10.10.10 --device=ETHER --rpo 0x1000
000192FF

Hello,

I have an Amazon 4th axis that features a 6:1 reduction drive.

I found the thread here where you adjust the SCALE so that a G0 A360 will turn the axis a proper 360°. 

However, the drive spins too slowly. 

I can double the SCALE, which gives me the speed I want, but then I have to do something like G0 A180 for a full turn.

Is there a way I can speed the drive up, while maintaining proper scale? 

In that case

mesaflash --addr 10.10.10.10 --device=ETHER --rpo 0x1000

should work

(with 7I77 disconnected)

I also bought lm331 to convert current from a dc spindle... I made a small circuit, but I haven't tried it for almost a year because my brother had serious health problems. I'll try in a few days, maybe we can help each other.
regards
Mauro

~$ mesaflash --addr 10.10.10.10 --device=ETHER --readhmid
Configuration Name: HOSTMOT2

General configuration information:

BoardName : MESA7I92
FPGA Size: 20 KGates
FPGA Pins: 256
Number of IO Ports: 2
Width of one I/O port: 17
Clock Low frequency: 100.0000 MHz
Clock High frequency: 180.0000 MHz
IDROM Type: 3
Instance Stride 0: 4
Instance Stride 1: 64
Register Stride 0: 256
Register Stride 1: 256

Modules in configuration:

Module: DPLL
There are 1 of DPLL in configuration
Version: 0
Registers: 7
BaseAddress: 7000
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes

Module: WatchDog
There are 1 of WatchDog in configuration
Version: 0
Registers: 3
BaseAddress: 0C00
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes

Module: IOPort
There are 2 of IOPort in configuration
Version: 0
Registers: 5
BaseAddress: 1000
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes

Module: MuxedQCount
There are 12 of MuxedQCount in configuration
Version: 4
Registers: 5
BaseAddress: 3600
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes

Module: MuxedQCountSel
There are 1 of MuxedQCountSel in configuration
Version: 0
Registers: 0
BaseAddress: 0000
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes

Module: SSerial
There are 1 of SSerial in configuration
Version: 0
Registers: 6
BaseAddress: 5B00
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 64 bytes

Module: LED
There are 1 of LED in configuration
Version: 0
Registers: 1
BaseAddress: 0200
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes

Configuration pin-out:

IO Connections for P2
DB25 pin# I/O Pri. func Sec. func Chan Sec. Pin func Sec. Pin Dir

1 0 IOPort SSerial 0 TXEn2 (Out)
14 1 IOPort SSerial 0 TXData2 (Out)
2 2 IOPort SSerial 0 RXData2 (In)
15 3 IOPort SSerial 0 TXData1 (Out)
3 4 IOPort SSerial 0 RXData1 (In)
16 5 IOPort SSerial 0 TXData0 (Out)
4 6 IOPort SSerial 0 RXData0 (In)
17 7 IOPort MuxedQCountSel 0 MuxSel0 (Out)
5 8 IOPort MuxedQCount 0 MuxQ-A (In)
6 9 IOPort MuxedQCount 0 MuxQ-B (In)
7 10 IOPort MuxedQCount 0 MuxQ-IDX (In)
8 11 IOPort MuxedQCount 1 MuxQ-A (In)
9 12 IOPort MuxedQCount 1 MuxQ-B (In)
10 13 IOPort MuxedQCount 1 MuxQ-IDX (In)
11 14 IOPort MuxedQCount 2 MuxQ-A (In)
12 15 IOPort MuxedQCount 2 MuxQ-B (In)
13 16 IOPort MuxedQCount 2 MuxQ-IDX (In)

IO Connections for P1
DB25 pin# I/O Pri. func Sec. func Chan Sec. Pin func Sec. Pin Dir

1 17 IOPort SSerial 0 TXEn5 (Out)
14 18 IOPort SSerial 0 TXData5 (Out)
2 19 IOPort SSerial 0 RXData5 (In)
15 20 IOPort SSerial 0 TXData4 (Out)
3 21 IOPort SSerial 0 RXData4 (In)
16 22 IOPort SSerial 0 TXData3 (Out)
4 23 IOPort SSerial 0 RXData3 (In)
17 24 IOPort MuxedQCountSel 6 MuxSel0 (Out)
5 25 IOPort MuxedQCount 3 MuxQ-A (In)
6 26 IOPort MuxedQCount 3 MuxQ-B (In)
7 27 IOPort MuxedQCount 3 MuxQ-IDX (In)
8 28 IOPort MuxedQCount 4 MuxQ-A (In)
9 29 IOPort MuxedQCount 4 MuxQ-B (In)
10 30 IOPort MuxedQCount 4 MuxQ-IDX (In)
11 31 IOPort MuxedQCount 5 MuxQ-A (In)
12 32 IOPort MuxedQCount 5 MuxQ-B (In)
13 33 IOPort MuxedQCount 5 MuxQ-IDX (In)

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?