Advanced Search

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!

It would referring to the Ethernet interface which would allow the computer to connect to the mesa card.

As if all things, we are not mind readers, it is so so so very helpful to post the actual error log. There maybe more to it than you can see. It is also helpful to describe you hard ware as well, what PC if possible a link to the actual specs, the ypre of mesa card and so forth. Aslo whether your network card (wired = ethernet generally) is on board or a separate add in card.

I not too sure what you mean, Linuxcnc does provide a server with ISO downloads and repos. It has done for many many years.

Actually apt is not stupid, if you ever used a RedHat distro in the 1990's or ealry 2000's you would know that dependencies had to be manually searched and installed. Slackware had the same issue as well, tho it did not have quite the software support a lot of packages had to be built by hand.

debs are a godsend, all dependencies are with the file it self (99.9999% of the time), everything is done automagically.

And honestly to not be able to install the latest packages via apt is really breaking the package system. A machinist may not want to download a script and then run it to install an update, they would prefer a simple way of doing it, apt & apt-get provide that method. And it is insurance from users trying to install packages they shouldn't, apt provides that.

Theres a lot of "behind the scenes" things that are involved in adding a deb package to a repo, it's not just about copying a file. Even when using a proxy to cache debs more things happen than just storing the file.

So before one goes shooting their mouth off, try setup reprepro on a server to provide a repo and have a look at what's involved. Or apt-cacher-ng and see if the files can link to external files.

I don't get why you have such an interest in thing being free. It's a little creepy.

I don't think that's true.

The NIST designed if for POSIX systems.
 

Could you provide the literature that confirms your claim.

Even if it is the RT implementations for WIndows NT & Linux are going to be different beasts, as would the RT for BSD. 

Even then Linux (most distros) NetBSD & OpenBSD are not certified as POSIX compliant yet comply in large part. Windows I think there was an effort with NT4 or Windows 2k, from memory a "POSIX Pack" was available. 
After looking through a number of documents I could not find posix mentioned. But if you have access to any plesae link.

andypugh wrote:

unknown wrote:

Linuxcnc isn't "designed for debian" originally the ISO were built for Ubuntu, 
I think that _originally_ EMC targeted Windows NT...

But FreeBSD was originally supported, according to en.wikipedia.org/wiki/LinuxCNC




 

Once again you have a more in depth, I can't think of the word.......I don't think I'm well and may not have long left before I'm not much good to anyone.
Th point I was trying to make is that building & running Linuxcnc is achievable on, I'll say most< Linux platforms. Even Puppy Linux had an ISO for Linuxcnc.

You've done something terribly wrong,
1; Didn't use RPi Imager to setup the settings
2: Choose to ignore the setup dialogue on the first boot.
In both instances you should have been able to setup a user name & password, the password for your account is the one that you use for sudo.
Both gparted and synaptic work when setup following the advice above.

imp can be replaced with (this module was removed from the version of python3 on trixie)
sudo apt install python3-zombie-imp

To go any further I think you will need to ask whether ProbeBasic and pyqtvcp has Trixie support.

I understand, but I installed GParted and Synaptic, and both require a password to log in. I use both because I have an SSD, and Synaptic for other tasks. I set a password in raspi-config, but it doesn't work to log in to these applications.

First of all I recommended to use the Rpi Imager to setup username, locale, and the other things needed.
If you didn't do this you should have gone through the setup screens to configure things.
This would have given you a user name.
This image is NOT LIKE the former images, it is based on the infrastructure that build the raspios images. The idea was to make it easier to setup the image and not have a preconfigured username and password.

Perhaps I wasn't more specific, but the error message indicates that it can't find the imp module.Then I send a screenshot of the error.From what I've read now, it seems to be due to something related to the Python version.

unknown wrote:

Linuxcnc isn't "designed for debian" originally the ISO were built for Ubuntu, 

I think that _originally_ EMC targeted Windows NT...

But FreeBSD was originally supported, according to en.wikipedia.org/wiki/LinuxCNC



 

If they do it now, I use it on several PIs with Debian 12.