Advanced Search

Only way to know is to have the xml and hal files, the error messages and some lines around them, and the last say 30 lines of the syslog.

need for v2.8.4
I created a program file and embedded debug messages into it. It was established that the error was triggered directly during execution of the g38.5 command

===========
            (LOG,стр 65 )
        #5070=1
        (LOG,X#5061 Y#5062 Z#5063)
        #5070=1
             (LOG,стр 68)
        #5070=1
        G38.5 F[#<_скорость_отскока>]  Z[#<_z> + #<_отскок>] 
             (LOG,стр 70)
===========
there is an entry in the log "стр 68", the machine was stopped by mistake and the state of the sensor - it drove away and in the "no contact" state #5070=0

seems like the lcec file in the hal fie has an invalid path. or XML has an invalid path.

I certainly could but would we want to make the python vtk module a runtime dependency?

Better like that?

You are making good progress. Once you have it all running, I will have to use your HAL and Ini to upgrade my machine to 2.9

I'd go one step further and establish that the network card appears in lspci. And that it has an appropriate address.

But we can only speculate on how to fix this issue until more information is supplied by the OP.

You understand that when you see a directory listing such as when you browse the Linuxcnc repo that those listings are created by the web server on the fly ? So I'm not sure if Apache et al allows for what your suggesting, or whether the Debian repo model allows for the behaviour you suggest.
Whilst saving a few dollars it could be an administrative headache.

Has anyone tried rock 5c / orange pi 6 / Orion 6 ?

Hi, would you be willing to share your linuxcnc config files?
I have a Cincinatti Milacron Sabre 750 with similar drives but the heidenhain control and powered it up for the first time & the hard disk has just failed with no backups.
I believe replacement drives are NLA, so it might be as well just just bite the bullet and go straight to a retrofit with linuxcnc.

I have done a linuxcnc retrofit before and have spare mesa boards, so would be using a similar mesa hardware as yourself, and any configurations would potentially be very helpful.

There are no errors in pnccfg, but there is no 7i96s+7i77 option, only 7i92+7i77... later I want to use the benefits of 7i96s and the configuration made in hal and ini via 7i92, I would have to change a lot manually... that's why I tried through Mesa CT. It can, however, it doesn't allow me any input regarding min-max angular velocity and that's why it won't export the configuration. I'll try to I will restart and let you know. thank you very much

usually when working systems break, something has broken. Its told you the error but you have not really told us.
Start at the beginning. can you ping your mesa card

hmm I can't remember if I kept all my Puppy versions, I used to help Barry a little bit from time to time getting wireless going in the very early days. Geesh even used to build my own custom ones. Some for booting a workstation from a server. And yes I was just as grumpy and the same old asshole back then.

What has happened is that the package you tried to install was build on a system with a different version of python.

The reason the package manager has given you this message and wont install is it can not install the version of a package to make things work. From version to version things change, modules are left out or with Python they change almost everything from Python2 to Python3. So yes versions do matter, even small changes to the API and what that particular package may depend on, its there to stop you having a broken system.

Please ignore this comment

Apt (and package managers in general) are really annoying when it comes to irrelevent versions of thing like python.

as the poster has a disconnect between what he thinks he knows, what he knows and what is in fact actually reality.

unknown wrote:

Even Puppy Linux had an ISO for Linuxcnc.

Yes, there were two versions:
-CoolCNC ISO at i think 50MB in total size
-Debian Dog at something like 350MB in total size
It is getting increasingly hard to find those, so archiving them for when we grow old might be a good idea, although might not need them, ever!