"G93 is fine for me" means nothing.
It is one thing when someone uses CAM and is not at all interested in how the g-code is created, and it is enough that it works, and it is completely different when someone writes the program themselves using functions, loops and subroutines.

bentiggin wrote:

I want to use 2.10 for some of the plasmac updates 

2.10 only partially supports Debian 13.
I can't check everything, but it looks like any qtvcp based gui won't work.
Changes in Python traditionally cause the problem.
A new version of numpy, but maybe something else too.
You can work around the problem by installing LinuxCNC on Debian 12, or downgrading some Python packages on Debian 13.
This is of course not a solution to the problem, the solution will be to repair the LinuxCNC sources, but so far no one wants to do that...

In my opinion FF1 and FF2 should be delayed. If the PID output is the velocity setpoint, then FF2 is not used, FF1 should be equal 1.0, but it would produce spikes at acceleration change. It could be improved by adding a 1st order delay to the setpoint value, before it gets compared to the actual value.

2.10 is currently transitioning to the a new hal API, so mind that is still somewhat work in progress, there is no 2.10 finished release

There are installable artefacts in the GitHub actions, get a GitHub account, download those for your system, and install, I would reccomend to use a system for which the CI already builds, you'll have yourself way less headaches

Hi All,

Thank you everyone for the already great response. The 50% discount offer closes on 4th October, just a few more days to grab it.

We will be launching Takshak Turn for mill turn and Takshak Burn for Lasers, EDMs, Waterjets and Plasma Cutter between October and November. They will launch with a discount as well.

Thanks all for the support

Hi guys.
Just quickly. I recently somehow ruined the +-10v analogue output on my 7i97T.

I emailed Peter at Mesa and he was kind enough to send me schematics and provide a fair bit of trouble shooting advice.

I ended up buying a hot air station and the failed component (Chat GPT helped me with how to test each device) and now have a fully functioning board for about $30c worth of components (I'm not counting the smd related consumables and tools that i wanted anyway).

This was probably the single best interaction that I have ever had with a company - that type of support (and the support showing within the LCNC community in general) is absolutely priceless.

So: Thanks PCW, thanks Mesa, thanks everyone else, and if anyone ever wonders which route they should take when planning a build- I obviously recommend having a good look at their range of products.

 

The fact that the stepgen outputs work with  the test program
indicates that the hardware is likely OK.

The test program is this:

 

Which will slowly toggle all step/dir outputs on any Mesa Ethernet FPGA card.
You may need to edit the file to change the IP address or select a different rate.
The default rate is quite slow to allow a DVM settling time to read both low and
high voltage states.

Did you try jogging in either direction with LinuxCNC to see if the DIR state changes?

The hal/ini file you sent had quite short step times (1000 ns) so could be a reason
for no motion. (Starting step times should be at least double the drives minimum timing)

If nothing else works, Mesa can issue a RMA for analysis/repair/replacement of the card
but the symptoms are very odd and don't  look at all like typical hardware issues.


 

Aircraft Instrument panels are larger than most knee mill tables.
Bridgeport Series II Interact have larger tables. Older Series II units have steppers.

0.1 uF 25V 0603

1. Encoders do not increment counters - hm2/hm2_7i95.0:     IO Pin 018 (TB1-01/TB1-09): Muxed Encoder #0, pin Muxed A (Input)
hm2/hm2_7i95.0:     IO Pin 019 (TB1-04/TB1-12): Muxed Encoder #0, pin Muxed B (Input)
I have tried all encoder inputs using a stepper motor with attached encoder in differential mode. See signals clearly at TB1

2. Steps in Axis UI show movements from jogging in registers but do not show up on output pins TB3 or TB4 . 
Tech at Mesa sent me a code snippet that did produce very slow signals at TB3 but the commands are not clear to me and I don't think they help debug.

From startup: 
Machine configuration directory is '/home/bill/linuxcnc/configs/7i95t_xyz'
Machine configuration file is '7i95t_xyz.ini'
Starting LinuxCNC...
linuxcnc TPMOD=tpmod HOMEMOD=homemod EMCMOT=motmod
Note: Using POSIX realtime
Found file(REL): ./main.hal
hm2: loading Mesa HostMot2 driver version 0.15
hm2_eth: loading Mesa AnyIO HostMot2 ethernet driver version 0.2
hm2_eth: 192.168.1.121: INFO: Hardware address (MAC): 00:60:1b:15:82:8b
hm2_eth: discovered 7I95T Thanks for any help. I don't want to pull my hair out, but is is getting close.... 
Bill Witt