Mesa Configuration Tool
- AirRacer
- Offline
- New Member
-
Less
More
- Posts: 14
- Thank you received: 3
09 Jul 2025 06:30 - 09 Jul 2025 15:12 #331557
by AirRacer
Replied by AirRacer on topic Mesa Configuration Tool
I’ve just discovered that the Mesa Configuration Tool (at least the version available prior to 8/19/2024) does not configure the manual tool change section correctly. I recently discovered this when my file did not stop at the M6 command and continued on to the next set of code. I was able to look at a .hal file set up with pncconfig and copy the manual tool change section from there and now everything works correctly (I get the manual tool change pop up window when the M6 command is encountered). This is a Mill setup that uses the AXIS GUI.
Here are the two configurations:
Pncconfig version that works:
# ---manual tool change signals---
net tool-change-request <= iocontrol.0.tool-change
net tool-change-confirmed => iocontrol.0.tool-changed
net tool-number <= iocontrol.0.tool-prep-number
# ---Use external manual tool change dialog---
loadusr -W hal_manualtoolchange
net tool-change-request => hal_manualtoolchange.change
net tool-change-confirmed <= hal_manualtoolchange.changed
net tool-number => hal_manualtoolchange.number
# ---ignore tool prepare requests---
net tool-prepare-loopback iocontrol.0.tool-prepare => iocontrol.0.tool-prepared
Mesa Configuration Tool version that doesn’t invoke the manual tool change pop-up or pause the code at M6:
# Manual Tool Change Dialog
loadusr -W hal_manualtoolchange
net tool-change-request => hal_manualtoolchange.change
net tool-change-confirmed <= hal_manualtoolchange.changed
net tool-number => hal_manualtoolchange.number
# create signals for tool loading loopback
net tool-prep-loop iocontrol.0.tool-prepare => iocontrol.0.tool-prepared
net tool-change-loop iocontrol.0.tool-change => iocontrol.0.tool-changed
Regards,
Skylor
Here are the two configurations:
Pncconfig version that works:
# ---manual tool change signals---
net tool-change-request <= iocontrol.0.tool-change
net tool-change-confirmed => iocontrol.0.tool-changed
net tool-number <= iocontrol.0.tool-prep-number
# ---Use external manual tool change dialog---
loadusr -W hal_manualtoolchange
net tool-change-request => hal_manualtoolchange.change
net tool-change-confirmed <= hal_manualtoolchange.changed
net tool-number => hal_manualtoolchange.number
# ---ignore tool prepare requests---
net tool-prepare-loopback iocontrol.0.tool-prepare => iocontrol.0.tool-prepared
Mesa Configuration Tool version that doesn’t invoke the manual tool change pop-up or pause the code at M6:
# Manual Tool Change Dialog
loadusr -W hal_manualtoolchange
net tool-change-request => hal_manualtoolchange.change
net tool-change-confirmed <= hal_manualtoolchange.changed
net tool-number => hal_manualtoolchange.number
# create signals for tool loading loopback
net tool-prep-loop iocontrol.0.tool-prepare => iocontrol.0.tool-prepared
net tool-change-loop iocontrol.0.tool-change => iocontrol.0.tool-changed
Regards,
Skylor
Last edit: 09 Jul 2025 15:12 by AirRacer.
The following user(s) said Thank You: JT
Please Log in or Create an account to join the conversation.
- JT
-
Topic Author
- Away
- Administrator
-
Less
More
- Posts: 992
- Thank you received: 514
15 Jul 2025 14:09 #331855
by JT
Replied by JT on topic Mesa Configuration Tool
Thanks for the report, this has been fixed.
JT
JT
The following user(s) said Thank You: AirRacer
Please Log in or Create an account to join the conversation.
- ZXT
- Offline
- New Member
-
Less
More
- Posts: 12
- Thank you received: 0
20 Jul 2025 13:17 - 20 Jul 2025 14:49 #332056
by ZXT
Replied by ZXT on topic Mesa Configuration Tool
Hello guys! I've just noticed that I/O map for 7i95T from Mesa Configuration tool 2.1.7 is not complete.
The I/O map is missing connector TB5 and TB6 or am i just looking at it wrong?
Or is it because I'll have to configure inputs & outputs under the 7i95t tab to get pin names in my I/O.hal?
The I/O map is missing connector TB5 and TB6 or am i just looking at it wrong?
Or is it because I'll have to configure inputs & outputs under the 7i95t tab to get pin names in my I/O.hal?
Firmware: 7i95t_1pwmd.bin
Configuration Name: HOSTMOT2
General configuration information:
BoardName : MESA7I95
FPGA Size: 20 KGates
FPGA Pins: 256
Number of IO Ports: 2
Width of one I/O port: 29
Clock Low frequency: 100.0000 MHz
Clock High frequency: 200.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 6 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: PWM
There are 1 of PWM in configuration
Version: 0
Registers: 5
BaseAddress: 4100
ClockFrequency: 200.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: StepGen
There are 6 of StepGen in configuration
Version: 2
Registers: 10
BaseAddress: 2000
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes
Module: SSR
There are 1 of SSR in configuration
Version: 0
Registers: 2
BaseAddress: 7D00
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes
Module: InMux
There are 1 of InMux in configuration
Version: 0
Registers: 5
BaseAddress: 8000
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 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 Step/DIR+Serial+Encoders -> 7I95_0
Pin# I/O Pri. func Sec. func Chan Sec. Pin func Sec. Pin Dir
TB3-2,3 0 IOPort StepGen 0 Step/Table1 (Out)
TB3-4,5 1 IOPort StepGen 0 Dir/Table2 (Out)
TB3-8,9 2 IOPort StepGen 1 Step/Table1 (Out)
TB3-10,11 3 IOPort StepGen 1 Dir/Table2 (Out)
TB3-14,15 4 IOPort StepGen 2 Step/Table1 (Out)
TB3-16,17 5 IOPort StepGen 2 Dir/Table2 (Out)
TB3-20,21 6 IOPort StepGen 3 Step/Table1 (Out)
TB3-22,23 7 IOPort StepGen 3 Dir/Table2 (Out)
TB4-2,3 8 IOPort StepGen 4 Step/Table1 (Out)
TB4-4,5 9 IOPort StepGen 4 Dir/Table2 (Out)
TB4-8,9 10 IOPort PWM 0 PWM (Out)
TB4-10,11 11 IOPort PWM 0 Dir (Out)
TB2-14,15 12 IOPort SSerial 0 RXData0 (In)
TB4-16,17 13 IOPort SSerial 0 TXData0 (Out)
Internal 14 IOPort SSerial 0 TXEn0 (Out)
TB4-20,21 15 IOPort SSerial 0 RXData1 (In)
TB4-22,23 16 IOPort SSerial 0 TXData1 (Out)
Internal 17 IOPort SSerial 0 TXEn1 (Out)
TB1-1,2,9,10 18 IOPort MuxedQCount 0 MuxQ-A (In)
TB1-4,5,12,13 19 IOPort MuxedQCount 0 MuxQ-B (In)
TB1-7,8,15,16 20 IOPort MuxedQCount 0 MuxQ-IDX (In)
TB1-17,18 TB2-1,2 21 IOPort MuxedQCount 1 MuxQ-A (In)
TB1-20,21 TB2-4,5 22 IOPort MuxedQCount 1 MuxQ-B (In)
TB1-23,24,TB2-7,8 23 IOPort MuxedQCount 1 MuxQ-IDX (In)
TB2-9,10,17,18 24 IOPort MuxedQCount 2 MuxQ-A (In)
TB2-11,12,20,21 25 IOPort MuxedQCount 2 MuxQ-B (In)
TB2-15,16,23,24 26 IOPort MuxedQCount 2 MuxQ-IDX (In)
Internal 27 IOPort MuxedQCountSel 0 MuxSel0 (Out)
Internal 28 IOPort InMux 0 Addr0 (Out)
IO Connections for I/O+Expansion -> 7I95_1
Pin# I/O Pri. func Sec. func Chan Sec. Pin func Sec. Pin Dir
Internal 29 IOPort InMux 0 Addr1 (Out)
Internal 30 IOPort InMux 0 Addr2 (Out)
Internal 31 IOPort InMux 0 Addr3 (Out)
Internal 32 IOPort InMux 0 Addr4 (Out)
Internal 33 IOPort InMux 0 Data0 (In)
TB3-13,14 34 IOPort SSR 0 Out-00 (Out)
TB3-15,16 35 IOPort SSR 0 Out-01 (Out)
TB3-17,18 36 IOPort SSR 0 Out-02 (Out)
TB3-19,20 37 IOPort SSR 0 Out-03 (Out)
TB3-21,22 38 IOPort SSR 0 Out-04 (Out)
TB3-23,24 39 IOPort SSR 0 Out-05 (Out)
Internal 40 IOPort SSR 0 AC Ref (Out)
P1-01/DB25-01 41 IOPort None
P1-02/DB25-14 42 IOPort None
P1-03/DB25-02 43 IOPort None
P1-04/DB25-15 44 IOPort None
P1-05/DB25-03 45 IOPort None
P1-06/DB25-16 46 IOPort None
P1-07/DB25-04 47 IOPort None
P1-08/DB25-17 48 IOPort None
P1-09/DB25-05 49 IOPort None
P1-11/DB25-06 50 IOPort None
P1-13/DB25-07 51 IOPort None
P1-15/DB25-08 52 IOPort None
P1-17/DB25-09 53 IOPort None
P1-19/DB25-10 54 IOPort None
P1-21/DB25-11 55 IOPort None
P1-23/DB25-12 56 IOPort None
P1-25/DB25-13 57 IOPort None
Last edit: 20 Jul 2025 14:49 by JT. Reason: add code tags
Please Log in or Create an account to join the conversation.
- JT
-
Topic Author
- Away
- Administrator
-
Less
More
- Posts: 992
- Thank you received: 514
20 Jul 2025 14:47 #332062
by JT
Replied by JT on topic Mesa Configuration Tool
It's a mystery to me, that's what the mesaflash command returns
Maybe PCW can shed some light on that?
JT
mesaflash --addr 10.10.10.10 --device 7i95t --readhmid
Maybe PCW can shed some light on that?
JT
Please Log in or Create an account to join the conversation.
- PCW
-
- Away
- Moderator
-
Less
More
- Posts: 19097
- Thank you received: 5271
20 Jul 2025 15:05 - 20 Jul 2025 15:57 #332063
by PCW
Replied by PCW on topic Mesa Configuration Tool
The 24 isolated inputs are all controlled by the inmux pins.
I guess they could be named "TB5-1,12, TB6-1,24" rather than "internal"
in mesaflash...
Edit: pushed a change to mesaflash to rename 7I95/7I97/7C80 "internal"
pins to more informative names.
I guess they could be named "TB5-1,12, TB6-1,24" rather than "internal"
in mesaflash...
Edit: pushed a change to mesaflash to rename 7I95/7I97/7C80 "internal"
pins to more informative names.
Last edit: 20 Jul 2025 15:57 by PCW.
The following user(s) said Thank You: tommylight, JT
Please Log in or Create an account to join the conversation.
- ZXT
- Offline
- New Member
-
Less
More
- Posts: 12
- Thank you received: 0
20 Jul 2025 19:50 #332080
by ZXT
Replied by ZXT on topic Mesa Configuration Tool
Managed to get info by making a test config in MesaCT and then look in I/O.hal
Input 16, TB5
hm2_7i95.0.inmux.00.input-16
Input 16, TB5
hm2_7i95.0.inmux.00.input-16
Please Log in or Create an account to join the conversation.
- PCW
-
- Away
- Moderator
-
Less
More
- Posts: 19097
- Thank you received: 5271
20 Jul 2025 23:32 #332090
by PCW
Replied by PCW on topic Mesa Configuration Tool
You can also get a list of all enabled hardware pins with:
halcmd show all | grep hm2
When LinuxCNC is running.
halcmd show all | grep hm2
When LinuxCNC is running.
The following user(s) said Thank You: JT, ZXT
Please Log in or Create an account to join the conversation.
Time to create page: 0.109 seconds