SOS-Config ruined after dist-up. Back to previous version old LinuxCNC dist?

How does this apply to LinuxCNC versions though? Apt-get install LinuxCNC=<official release I want>?

And isnt it necessary that this prev version exist in a repository. From what I know only the latest versions are in the LinuxCNC repository. Latest 2.7.14 or latest 2.9.0(master)

That link had a way to list the available versions. Does that say anything useful?

Unfortunately i dont have access to the specific pc now until Monday. I will try to check the general idea behind it with virtual machine on virtualbox.

m.bofi wrote: How does this apply to LinuxCNC versions though? Apt-get install LinuxCNC=<official release I want>?

And isnt it necessary that this prev version exist in a repository. From what I know only the latest versions are in the LinuxCNC repository. Latest 2.7.14 or latest 2.9.0(master)

Yes it is, and there are some there, for example right now buildbot has for Master from 2.9.0~pre0.653 back to 2.9.0~pre0.556.

2.7 is the current stable release of LInuxcnc. 2.9 (Master) is the current development branch (not stable). 2.8 is on the cusp of being released as the latest stable release of Linuxcnc. You can install it using the Linuxcnc repositories on buildbot.linuxcnc.org/ To install 2.8 simply setup a repo exactly the same as your buildbot repo for 2.7, except changing 2.7 to 2.8. The repos are there for 2.8, just the web pages and docs have not been updated to point to it yet because it's release isn't "official" yet.

I found the way to downgrade and i have been testing every past linuxcnc ver. However none works. And from a photo i had saved i verified that previously i had 2.9.0-pre0-613 and the config worked just fine. But now that i check the same version and it doesnt work. I am so buffled. What could cause this?

Can you post the HAL and INI files here?

I wonder if this might be a hardware failure.?

I am very positive that hardware works quite well. But then again maybe electronics is to blame and i cant really check this possibility. A bit of information about the config. Its a Mitsubishi RM501, a serial robot with 5 rotational joints with a custom controller, made by a previous student. The last two joints(the wrist) are linked with a differential system. when both motors rotate the same way the wrist goes up or down. When the motors turn in different directions the wrist rotates.

I assume that it was all working fine between 2019-06-12 and 2019-09-20 when you posted the first message?

Looking at the HAL (which is quite complicated) prompted some memories. Is this the same robot?
forum.linuxcnc.org/27-driver-boards/2759...ifiers?start=0#44662
The posts there do at least explain how the HAL is intended to function.

Step scale is 40 steps/degree and STEPGEN_MAXVEL (commented out in Joint 0) is 31.3. That means that you are, indeed, asking for 1252 step/second. The stepgen rate warning seems like it should always have been there, with a base period of 40,000nS.
Setting the STEPGEN_MAXACCEL to 31.2 (and uncommenting Joint0) will quiet that message.

Which joints are working, and which ones not? Can you check that the stepper drive direction pins are changing state as you attempt to jog in each direction?

Indeed it is! And yes after some minor adjustments to the ini and the custom kinematics it worked fine. Especially during last week that i ran some tests all was fine.

Joint 0 and joint 2 work as they supposed to.The problem with joint 1 and the wrist(joint 3 and 4).

Can you check that the stepper drive direction pins are changing state as you attempt to jog in each direction?

im quite bad at this. how do i check it?

I tried almost all 2.8 ver available on buildbot as well as the 2.7.14 as well and the problem insists.
So i just connected the old pc which had the original config with a 2.7.14-112 ver and it appears all works fine, apart from the fact that is is exceptionally slow(one of the reasons i went ahead and the config to a new pc). However the good news is that since it works fine we can verify that it is not a hardware malfunction, right?
And now i'm very very curious what has happened to the new pc and it doesnt work.