Advanced Search

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!

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.

langdons wrote:

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.

GitHub can't provide a true browsable website directory like you can acheive with NGINX, for example (such as linuxcnc.org/iso or www3.langdonstaab.ca).

Therefore, GitHub cannot supply the DEB repo for APT.

GitHub also can't store the ISO files because they are way too big.

We do need an actual server for those 2 things (and the forum, of course, but that's separate).

However, literally everything else is possible without any real server at all.

Github can (and should) be the provider of all release debs on the website.

While we need the debs on our server too for stupid apt, all the DEB download links on linuxcnc.org should be GitHub links (why would we consume our server resouces and bandwidth when GitHub can provide the same for free).