I'm guessing your previous install was a version prior to Python 3. The py2 versions worked with a pip install as run in place where apt installs in root. Your custom py file should still work though. It may be a py2 file needed updating to py3?

Thanks for the svg -> bitmap conversion into the thread. When I get a chance, I will try running a script to process all the sim configs.

OK, these errors should be resolved with this  forum.linuxcnc.org/42-deutsch/55509-inst...bleme?start=0#323051

Thnks a lot

A reinstall unfortunately does not solve the issue. I am also not sure that this is a new problem. It looks like the running version is probe-basic_0.5.3-216. We never tried using the probing part of the interface until a few days ago. After the probing routine completes, the ui stays in the busy state indefinitely if I had it set to update the WCO. If it is only set to measure, it works fine. I can find no significant differences between the old and the updated probing routines. Also, probing with my own custom routines works fine. It is only when I click a probing routine on the probing tab with it set to update the WCO that it locks up. If I comment out the G10 line, the ui does not stay locked. I have tried running linuxcnc from the terminal to see if there is any debug output but no luck there either.

I figured that support from the people who make it for what appears to be a bug in a version from 2023 would be a long shot. It is from before installing from apt was even an option. There are also a few modifications I no longer have to do because they have become features. I have not connected the new version to the machine to test if probing behaves the same way yet. Wanted to make sure I could get everything to behave the way we have trained people. I have a little mini pc set aside to for that once I get a copy of the config modified for our machine.

Appreciate that it can be tiresome to see the same stuff repeatedly. Everyone is at a different point in their journey of learning.

OK, installation is done.
At the moment the latency test looks like this:
 

The only thing is that i allways get the same depending-problems, so i can not upgrade the kernel.
 

Can someone help me here..
Thanks a lot
Jens

I can guarantee you that there are many users in Poland with that equipment.
But if they are here and see this request is another thing.

This is described on page 11 of the 7I96S manual

basically:

RX-/TX- connect to RS-485 "A"
RX+/TX+ connect to RS-485 "B"
W7 right
 

I have a 7i96s rev E that I'm trying to connect to a WJ200 VFD. The VFD  uses a 2-wire RS485 interface with pins labeled SN and SP.

How should I connect this to the 7i96s i/o pins?  What position should W7 be in? 

Thanks,
BR

 

ok i think i found a bug dealing with pocket in the tool table causing some odd behavior. let me dig into it some and see what is happening.

Hi Andy,

Sorry for the confusion.

Python files in /linuxcnc/lib/ may not be processed by the "make" command.

Python files in /linuxcnc/src/ may be processed by the "make" command.

I've tested it now.
You were right.

Hi,
I am wondering if there may be someone experienced with linuxCNC and MESA board based controllers from Warsaw (Poland) (or near Warsaw).

Cris.

Thank you Tommylight, I gave up on my previous efforts and installed Mint as you suggested. Upgrading now. Hope this one is less hairy than my last attempt.
Will let you know when it's up and running.

It is cheaper to get the real ones from Mesa.

It's standard linuxcnc homing from here on
linuxcnc.org/docs/html/config/ini-homing.html