Advanced Search

Im glad you manage to fix it and is probably much better than any retrofit.
Can you share some details, I would like to do the same but am affraid it would cost too much.
I paid for whole machine and vacuum pump cheaper than it would be for them if they sold it to junk jard as steel waste.
But again am just starting this cnc thing and dont have any business running yet.

Yes, across the THCAD input side.

bonjour, je voudrais savoirsi la carte bonjour, je voudrai savoir si une carte d'adaptateur PCI Express vers parallèle DB25 peut etre utilisee pour linuxcnc? merci fr.aliexpress.com/item/1005007091741451....gatewayAdapt=glo2fra

You mean across positive and negative of the Thad?

Okay, so this is not reproducible for you. I also think it was working for a short while for me before I started getting the following errors.

The value position-fb jumps to is consistent across time and even if unloading all modules and starting over. But it has changed as well at some time, but I'm not quite sure what has been the trigger for that. Perhaps some change in the modbus .mod "config", but I'm not sure.

I actually was also thinking about narrowing it down by a ethernet capture, and already took one with Wireshark. I could see the LBP16 commands, but have not tried to decipher what is written/read yet (by the LBP16 commands). But just by looking at the source code, it appears the step rate is written and the position feedback (16.16 floating point accumulator) is read back. It shouldn't be too difficult to figure out if something strange happens with those. Hopefully

I would put at least two of those 5K resistors in parallel, in parallel with the input of THCAD.

Is it possible to make the random tool change faster searching for the next tool in the g-code and prepare it while the program runs?

5 volt Thad
24 volt power supply.

I tried that firmware on a 7I95T with the included relayboard.mod
and stepgens set to 5 with no issues (with or without a relay modbus
device connected).

I'll try your example on Monday. Worst case, may be debuggable with
tcpdump.

Yes, this is what I noticed as well. I believe that the linuxcnc.var file is incorrect and the later gets written to
with an acceptable value within range.

I followed the code during this time to confirm. I'm just not sure where the initial value is being set?

Thanks for chiming in, hopefully this can get remediated sooner rather than later.

Ok so the hardware is essentially no issue. I do have a secondary whole PC if need be.

So basically am i to interpret that MAX limits define the Working area of the machine? so in the case of my denford machine it can carve max A3 sized space.

And as for the 10 velocity , does it mean 10mm/sec ? or something like that?

aditionally, The machine i want it to use Metric units so i just left it as is.

I'll join in because I have the same problem.
When I touch the probe, the g54 z values ​​are correct.
When I start the program, insert the new tool and it then measures it, the numbers for g54 z are over 200. And the program stops because the z axis is exceeded.
But the strange thing is that in the linuxcnc.var, the correct value is under #5223 (e.g. -98.816)

Well if python3-distro is a required package and also in the readme so not sure where you went wrong... did you download and install the deb with gdebi?

JT

I just ran the live cd from Linuxcnc and they chose to not have the python3-distro package installed by default... you can install python3-distro from a terminal with

I'll add that to the requirements...

JT

Same subject has been answered on 2 other topics with similar tittle.