Search Results (Searched for: )
- PCW
24 Feb 2026 16:11 - 24 Feb 2026 16:17
Replied by PCW on topic 7i76EU+7i85+7i84U
Is sserial channel 2 enabled in the hal file?
(something like : "sserial_port_0=000xxxxx" in the driver command line)
Also
mesaflash --device 7i76eu --addr 10.10.10.10 --dbname2 7i85 --readhmid
would list the 7I85 pins, not DB25 pins
(something like : "sserial_port_0=000xxxxx" in the driver command line)
Also
mesaflash --device 7i76eu --addr 10.10.10.10 --dbname2 7i85 --readhmid
would list the 7I85 pins, not DB25 pins
- Dudelbert
24 Feb 2026 16:10
Replied by Dudelbert on topic Considering a Full Rewire on a Working Schaublin 125 CNC
I tried again today.
At this point, I believe that at least some of the hardware is broken. The Smart Serial channels 0 to 3 of the 7i92t/7i85 combo do not work. I was able to get 4 of the 5 Smart Serial boards to be detected if I connect them to channel 4 of the 7i85, but on all other channels I get nothing. I don’t know if the fact that this is exactly the channel used by the bitfile I used to get a working config is a coincidence, or if I somehow managed to damage something.
I also don’t really understand how the process described in this topic works:
forum.linuxcnc.org/39-pncconf/52554-disc...ted-mesa-fpga#299687
With the described setup, there is no way to set the X and Z axes. When I try to go that route, I always get an error window in PnCconf telling me I have to set stepgen or pwmgen for the axes. So the statement “The rest of the setup in PnCconf should proceed in a more normal manner.” seems strange to me.
Regarding the 7i84U, I can get one to be detected, but I get an undervoltage error. Measuring the outputs, they do not seem to work when I set or reset them, and when I inject +24V or GND into an input, it does not change state in HAL Show either.
The second 7i84U is not detected at all, and LED CR6 does not come on.
So are both broken somehow? I don’t know.
At this point, I think my 7i73 and 7i83 are probably fine. Both 7i84Us are likely faulty, but in different ways, and either the 7i92T or the 7i85 may also have some problems.
I really don’t know how to proceed from here. Honestly, I am considering getting a 7i97T and more or less replicating the setup I use on my mill.
At this point, I believe that at least some of the hardware is broken. The Smart Serial channels 0 to 3 of the 7i92t/7i85 combo do not work. I was able to get 4 of the 5 Smart Serial boards to be detected if I connect them to channel 4 of the 7i85, but on all other channels I get nothing. I don’t know if the fact that this is exactly the channel used by the bitfile I used to get a working config is a coincidence, or if I somehow managed to damage something.
I also don’t really understand how the process described in this topic works:
forum.linuxcnc.org/39-pncconf/52554-disc...ted-mesa-fpga#299687
With the described setup, there is no way to set the X and Z axes. When I try to go that route, I always get an error window in PnCconf telling me I have to set stepgen or pwmgen for the axes. So the statement “The rest of the setup in PnCconf should proceed in a more normal manner.” seems strange to me.
Regarding the 7i84U, I can get one to be detected, but I get an undervoltage error. Measuring the outputs, they do not seem to work when I set or reset them, and when I inject +24V or GND into an input, it does not change state in HAL Show either.
The second 7i84U is not detected at all, and LED CR6 does not come on.
So are both broken somehow? I don’t know.
At this point, I think my 7i73 and 7i83 are probably fine. Both 7i84Us are likely faulty, but in different ways, and either the 7i92T or the 7i85 may also have some problems.
I really don’t know how to proceed from here. Honestly, I am considering getting a 7i97T and more or less replicating the setup I use on my mill.
- tommylight
-
24 Feb 2026 16:09
Replied by tommylight on topic 7i76EU+7i85+7i84U
7i84 requires having field power on both section for all IO to show up, not sure about the 7i84U.
Is the field power applied to the 7i84U?
Is the field power applied to the 7i84U?
- tommylight
-
24 Feb 2026 16:06
Replied by tommylight on topic Enabling multi-touch (pinch-to-zoom) in QtDragon HD with Touchscreen
Does QtVCP zoom with mouse wheel?
Multitouch should at least emulate mouse buttons and wheel, but i never tried it... there is something for Linux enabling multitouch but i forgot the name, comes preinstalled with System 76 laptops and their Linux distro, see if you can find any info about it. I did test it on a touchscreen laptop quite a while back and pinch to zoom worked for most stuff, i do not recall testing LinuxCNC with it.
Multitouch should at least emulate mouse buttons and wheel, but i never tried it... there is something for Linux enabling multitouch but i forgot the name, comes preinstalled with System 76 laptops and their Linux distro, see if you can find any info about it. I did test it on a touchscreen laptop quite a while back and pinch to zoom worked for most stuff, i do not recall testing LinuxCNC with it.
- Todd Zuercher
24 Feb 2026 16:02
7i76EU+7i85+7i84U was created by Todd Zuercher
First time using a Mesa Ethernet board and I'm trying to set up a new install. I think I've flashed the right firmware to the 7i76eu. But I can't seem to see the 7i84u card that I have plugged into the first serial connector on the 7i85. The encoders seem to be working on the 7i85, but I can't seem to make the 7i84u work. On the 7i85u CR2 and CR7 are on yellow and CR5 is on red. Not sure what I'm doing/have done wrong.
Here's the output of mesaflash --device 7i76eu --addr 10.10.10.10 --readhmid
Here's the output of mesaflash --device 7i76eu --addr 10.10.10.10 --readhmid
Code:
twincnc@twincnc:~$ mesaflash --device 7i76eu --addr 10.10.10.10 --readhmid
Configuration Name: HOSTMOT2
General configuration information:
BoardName : MESA7I76
FPGA Size: 20 KGates
FPGA Pins: 256
Number of IO Ports: 3
Width of one I/O port: 17
Clock Low frequency: 100.0000 MHz
Clock High frequency: 160.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 3 of IOPort in configuration
Version: 0
Registers: 5
BaseAddress: 1000
ClockFrequency: 100.000 MHz
Register Stride: 256 bytes
Instance Stride: 4 bytes
Module: StepGen
There are 5 of StepGen in configuration
Version: 2
Registers: 10
BaseAddress: 2000
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: 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 on-card -> 7I76
Pin# I/O Pri. func Sec. func Chan Sec. Pin func Sec. Pin Dir
TB2-4,5 0 IOPort StepGen 0 Dir/Table2 (Out)
TB2-2,3 1 IOPort StepGen 0 Step/Table1 (Out)
TB2-10,11 2 IOPort StepGen 1 Dir/Table2 (Out)
TB2-8,9 3 IOPort StepGen 1 Step/Table1 (Out)
TB2-16,17 4 IOPort StepGen 2 Dir/Table2 (Out)
TB2-14,15 5 IOPort StepGen 2 Step/Table1 (Out)
TB2-22,23 6 IOPort StepGen 3 Dir/Table2 (Out)
TB2-20,21 7 IOPort StepGen 3 Step/Table1 (Out)
TB3-4,5 8 IOPort StepGen 4 Dir/Table2 (Out)
TB3-2,3 9 IOPort StepGen 4 Step/Table1 (Out)
Internal-Field-IO 10 IOPort SSerial 0 TXData0 (Out)
Internal-Field-IO 11 IOPort SSerial 0 RXData0 (In)
TB3-18,19 12 IOPort SSerial 0 TXData1 (Out)
TB3-16,17 13 IOPort SSerial 0 RXData1 (In)
TB3-13,14 14 IOPort MuxedQCount 2 MuxQ-IDX (In)
TB3-10,11 15 IOPort MuxedQCount 2 MuxQ-B (In)
TB3-7,8 16 IOPort MuxedQCount 2 MuxQ-A (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 RXData6 (In)
14 18 IOPort SSerial 0 TXData6 (Out)
2 19 IOPort SSerial 0 RXData5 (In)
15 20 IOPort SSerial 0 TXData5 (Out)
3 21 IOPort SSerial 0 RXData4 (In)
16 22 IOPort SSerial 0 TXData4 (Out)
4 23 IOPort SSerial 0 RXData3 (In)
17 24 IOPort SSerial 0 TXData3 (Out)
5 25 IOPort SSerial 0 RXData2 (In)
6 26 IOPort SSerial 0 TXData2 (Out)
7 27 IOPort MuxedQCountSel 0 MuxSel0 (Out)
8 28 IOPort MuxedQCount 0 MuxQ-A (In)
9 29 IOPort MuxedQCount 0 MuxQ-B (In)
10 30 IOPort MuxedQCount 0 MuxQ-IDX (In)
11 31 IOPort MuxedQCount 1 MuxQ-A (In)
12 32 IOPort MuxedQCount 1 MuxQ-B (In)
13 33 IOPort MuxedQCount 1 MuxQ-IDX (In)
IO Connections for P2
DB25 pin# I/O Pri. func Sec. func Chan Sec. Pin func Sec. Pin Dir
1 34 IOPort None
14 35 IOPort None
2 36 IOPort None
15 37 IOPort None
3 38 IOPort None
16 39 IOPort None
4 40 IOPort None
17 41 IOPort None
5 42 IOPort None
6 43 IOPort None
7 44 IOPort None
8 45 IOPort None
9 46 IOPort None
10 47 IOPort None
11 48 IOPort None
12 49 IOPort None
13 50 IOPort None
- PCW
24 Feb 2026 15:46
Replied by PCW on topic 7i92TM defect? How to verify?
A quick way to test is with mesaflash:
Disconnect the 7I92TM from breakouts/ G540 and make sure the
pullup option on P2 is enabled (W2 UP) Then in a terminal window:
mesaflash --device ethernet --addr 10.10.10.10 --rpo 0x1000
(replace 10.10.10.10 with 192.168.121 if you card is set that way)
This should respond with
0001FFFF
(all 17 I/O bits high)
Disconnect the 7I92TM from breakouts/ G540 and make sure the
pullup option on P2 is enabled (W2 UP) Then in a terminal window:
mesaflash --device ethernet --addr 10.10.10.10 --rpo 0x1000
(replace 10.10.10.10 with 192.168.121 if you card is set that way)
This should respond with
0001FFFF
(all 17 I/O bits high)
- Marco61
24 Feb 2026 15:36
Replied by Marco61 on topic Bouttons du Custom Panel ne fonctionnent pas
Resolu
Codes disponibles
Merci
Codes disponibles
Merci
- Marco61
24 Feb 2026 15:33
Replied by Marco61 on topic Buttons in cutom panel look conected but did not work
SOLVED !
Codes available.
Thxs
Codes available.
Thxs
- Marco61
24 Feb 2026 15:28
Jog speed was created by Marco61
Hi evryone,
My buttons jog xyz +- in the custom panel are working ! Yéhhhhhhhh
Home button as well.
Slider for speed control as well.
Last problem is the speed max in this pannel.
Very slow @ max more slow @50%
Can someone tell me where and in whitch files I can increase the max speed in pyVCP.
Thanks
Marco
My buttons jog xyz +- in the custom panel are working ! Yéhhhhhhhh
Home button as well.
Slider for speed control as well.
Last problem is the speed max in this pannel.
Very slow @ max more slow @50%
Can someone tell me where and in whitch files I can increase the max speed in pyVCP.
Thanks
Marco
- cmorley
24 Feb 2026 14:45
Replied by cmorley on topic Enabling multi-touch (pinch-to-zoom) in QtDragon HD with Touchscreen
Qtvcp does not know about multitouch.
I don't have a multitouch to test with and QtPy5 had very little examples the last time I looked.
If you would like to try...
Somewhere around here is where you would add the code:
github.com/LinuxCNC/linuxcnc/blob/master...mlin/qt5_graphics.py
I don't have a multitouch to test with and QtPy5 had very little examples the last time I looked.
If you would like to try...
Somewhere around here is where you would add the code:
github.com/LinuxCNC/linuxcnc/blob/master...mlin/qt5_graphics.py
- Jensner
24 Feb 2026 14:21
Replied by Jensner on topic Aufschaukeln mit JMC iHSS60-36-30-21-38 in Verbindung mit Linear Encodern
After nearly 3 Month i have to thank all of you.
Last November I startet these upgrade with linear encoders on all axis and after view days with try and error i just solved the problems and i can`t tell what a gamechanger this upgrade was to my mill.
Before this upgrade I allways had the problem, that on long programs with many moves i often had some losses of steps and the result never was perfect. (mostly on my 2m long X-axle) After the upgrade to the encoder its a dream to work. No more losses of steps and i can work on a level i never dreamd of.
Next project will be an upgrade to an ATC Spindle with a cabinet.
So i think th next thead is coming soon ...
Thanks a lot at all
Jens
Last November I startet these upgrade with linear encoders on all axis and after view days with try and error i just solved the problems and i can`t tell what a gamechanger this upgrade was to my mill.
Before this upgrade I allways had the problem, that on long programs with many moves i often had some losses of steps and the result never was perfect. (mostly on my 2m long X-axle) After the upgrade to the encoder its a dream to work. No more losses of steps and i can work on a level i never dreamd of.
Next project will be an upgrade to an ATC Spindle with a cabinet.
So i think th next thead is coming soon ...
Thanks a lot at all
Jens
- stenly
24 Feb 2026 13:40
I haven't attempted to do anything like that. I'm not sure it is even possible for the brake control to be left to the axis driver itself. From what I see (on my untouched original DMU 50M too) the brake/release is nothing but an output signal from the controller to the drive. I don't think the drive itself is capable of handling such logic, or at least that wasn't the original machine manufacturer's intention. I will look into it, though.
Oh, also, my braking/release signal is a single one for all 3 XYZ drives. Is it possible to try and separate them electrically? Most likely. I'm not sure that's a good idea, though.
Replied by stenly on topic DMU 50M retrofit 99% done, Z axis falling on brake release
Thanks for the feedback.On my older MH400E, with Indramat drives, I made the mistake of adding a relay to give LinuxCNC co-control over the vertical axis brake. The original Maho design is that the Indramat axis driver solely controlled that brake. I had the opposite behaviour to you, where instead of dropping, the drive fought the brake during the period I had my finger on the machine start button.
Once I removed the 19K2 relay I added (second schematic in this post) the behavior worked correctly.
forum.linuxcnc.org/12-milling/33035-retr...0e?start=1740#340651
From the schematics you shared it I don't see the brake control circuit.Could it be that your brake control should be left to the axis driver alone?
Cheers,
Mark
I haven't attempted to do anything like that. I'm not sure it is even possible for the brake control to be left to the axis driver itself. From what I see (on my untouched original DMU 50M too) the brake/release is nothing but an output signal from the controller to the drive. I don't think the drive itself is capable of handling such logic, or at least that wasn't the original machine manufacturer's intention. I will look into it, though.
Oh, also, my braking/release signal is a single one for all 3 XYZ drives. Is it possible to try and separate them electrically? Most likely. I'm not sure that's a good idea, though.
- stenly
24 Feb 2026 13:36
It is probably worth noting that before we took out the original TNC 310 there was no such issue. So I would assume no parameters are corrupted or something of the sort.
Replied by stenly on topic DMU 50M retrofit 99% done, Z axis falling on brake release
Honestly, this sounds very reasonable and I've been trying to track such a parameter down for a while now. But my Simodrive is so old, it isn't supported by Simocom. I have to chug through manuals in the hopes of finding the correct one and the correct parameter. Been trying, but it's often conflicting information that I find, since Siemens don't publish specific manuals for a specific model, but general manuals for the entire product lineup... I will definitely keep searching, though.I just had a very similar issue with a Yaskawa servopack drive on the Z axis of a Morbidelli. I tried adding `z-brake release delays via hal and had no luck. What eventually worked was finding a parameter in the servo drive that had the same purpose, something about keeping the control loop active so many milliseconds after the servo-ON signal or brake-ON signal was received. Perhaps your drive has similar? good luck!
It is probably worth noting that before we took out the original TNC 310 there was no such issue. So I would assume no parameters are corrupted or something of the sort.
- stenly
24 Feb 2026 13:10
My AC power on button and circuit is separate from the Mesa entirely in an attempt not to have to reverse engineer the emergency stop, which is on the same board originally.
So my startup procedure is essentially:
LinuxCNC startup, LinuxCNC power on (F2), manually pushing the servo AC power on button, a signal returns to the Mesa board from the drive when AC power on is successful, that signal is linked in HAL to the brake release after a short timedelay.
In many cases, this works just fine. In many, Z falls through. Sometimes after a slight delay, so just when you think it's started up properly and the servo is holding the motor, it still falls through 10 seconds later.
Thanks for the suggestion, though!
How exactly is your servo AC power on handled? My Simodrive is sort of old, as you may see — the servos are 6SN1118-0AD11-0AA1 and the control board is 6SN1121-0BA11-0AA1.
Replied by stenly on topic DMU 50M retrofit 99% done, Z axis falling on brake release
I don't think this is the issue. I checked just now to make sure. With me pressing F2 (which is also linked to the CNC ready signal going from the Mesa to the drive), I can clearly see the PID enabled and also motion.motion-enabled.I release z axis brake 0.2s after motion.motion-enabled and it works with my simodrive,
when does this servo power on signal becomes true? are you sure you are not releasing the brake before pid is working?
My AC power on button and circuit is separate from the Mesa entirely in an attempt not to have to reverse engineer the emergency stop, which is on the same board originally.
So my startup procedure is essentially:
LinuxCNC startup, LinuxCNC power on (F2), manually pushing the servo AC power on button, a signal returns to the Mesa board from the drive when AC power on is successful, that signal is linked in HAL to the brake release after a short timedelay.
In many cases, this works just fine. In many, Z falls through. Sometimes after a slight delay, so just when you think it's started up properly and the servo is holding the motor, it still falls through 10 seconds later.
Thanks for the suggestion, though!
How exactly is your servo AC power on handled? My Simodrive is sort of old, as you may see — the servos are 6SN1118-0AD11-0AA1 and the control board is 6SN1121-0BA11-0AA1.
- Finngineering
24 Feb 2026 12:38
Replied by Finngineering on topic XHC WHB04B development?
Thank you for testing. The output indicate that the program was working as expected. The firmware is not exactly the same as mine, but it looks similar. How big differences/similarities there are would require disassembly comparing those. I can see that at least memory addresses are a bit different. Here is the output from mine (not the real dongle, I put the factory firmware on another device which has bootloader version 2.40):
The addresses and sizes are close to each other, but not exactly the same.
Because you have bootloader version 2.40, I believe we would be able to read out the firmware through the bootloader. But it requires creating a similar program for that as the one we just used. And to get to bootloader mode, a 10k resistor needs to be added to the pendant. So maybe better to wait until I have tested the new firmware a bit more. And then you could read out the firmware and flash the new one at the same time, if you are still interested at that point.
Code:
$ ./firmware_readout firmware.bin
1771943478.782 info: Read device descriptor with idVendor=0x10ce and idProduct=0xeb93
1771943478.783 info: Starting firmware readout process
1771943480.843 info: Read 5496 of 65535 bytes = 0.08%
1771943480.846 info: Found bootloader version 2.40 device descriptor after 5481 bytes
1771943480.846 info: Based on bootloader address, read firmware is from address 0x2925 to 0x37ff
1771943480.846 info: Wrote 5496 bytes to file firmware.bin
Because you have bootloader version 2.40, I believe we would be able to read out the firmware through the bootloader. But it requires creating a similar program for that as the one we just used. And to get to bootloader mode, a 10k resistor needs to be added to the pendant. So maybe better to wait until I have tested the new firmware a bit more. And then you could read out the firmware and flash the new one at the same time, if you are still interested at that point.
Time to create page: 0.346 seconds