A couple of errors during update 2.8.2-130-g87f66feaf

Testing done - issue gone with your branch.

Ran an ngc file 15 times and each time jogging worked as expected after selecing the manual mode button.  No more errors.

Next step will be something updating master branch and then I switch back using git checkout master?

Thank you very much, BTW

@spumco :
@johnnyCNC :

> Next step will be something updating master branch
> and then I switch back using git checkout master?

1) The problem exists in the 2.8 branch so testing
by johnnyCNC (or others) is needed before adding
commit to 2.8

2) After 2.8 branch is updated, master branch will be updated

There may be to-be-determined (unwanted) side effects
so continued testing and usage to exercise more parts
of LinuxCNC will be appreciated .  It may take some
time to confirm changes are ok for 2.8 branch.

 

Will do, and thanks again.

I'll try turning off my vc-p4s also. I'm running 2.8 and this also not a problem a few months ago.

dgarrett wrote:

@spumco :
@johnnyCNC :

> Next step will be something updating master branch
> and then I switch back using git checkout master?

1) The problem exists in the 2.8 branch so testing
by johnnyCNC (or others) is needed before adding
commit to 2.8

2) After 2.8 branch is updated, master branch will be updated

There may be to-be-determined (unwanted) side effects
so continued testing and usage to exercise more parts
of LinuxCNC will be appreciated .  It may take some
time to confirm changes are ok for 2.8 branch.


 

This is great.  Thank You.  I will try to get to some testing today.
 

I am starting to look at this now. I looked at the list of scratch package and don't see one that matches what I am running. I have some spare SSDs. I could just do a new install on one of those. What do you think?

Distributor ID: LinuxMint
Description: Linux Mint 19.3 Tricia
Release: 19.3
Codename: tricia

Also, I ran linuxcnc_info and there was no output.

Thanks
John

@johnnyCNC :

> I am starting to look at this now. I looked at the
> list of scratch package and don't see one that
> matches what I am running. I have some spare SSDs. I
> could just do a new install on one of those. What do
> you think?

Your initial forum post indicates: 2.8.2-130-g87f66feaf
1) How did you install LinuxCNC?

> Distributor ID: LinuxMint
> Description: Linux Mint 19.3 Tricia
> Release: 19.3
> Codename: tricia

The buildbot makes 2.8 scratch debs for debian buster,
and debian stretch
Ref: buildbot.linuxcnc.org/dists/

I don't know which one (if any) is suitable for Mint 19.3
You are on your own if you can't use a
buildbot-supported scratch package but want a prebuilt
deb.

2) Please post result from command:
$ dpkg -l "linuxcnc*"

> Also, I ran linuxcnc_info and there was no output.
3) Please post result from these commands:

$ which linuxcnc_info
$ env|grep -E EDITOR\|VISUAL


The installed linuxcnc_info command outputs to an
editor.  Supported editors include:
gedit mousepad geany nedit gvim abiword

4) What text-mode editor do you use?

 

1. It has been a while so I am not positive. I know I installed it many times when I switch from Wheezy with 2.7 RTAI to Mint 19.3 with 2.8 preempt-rt
2. Can't do that at the moment. I am installing Buster on a spare SSD and will test there. First replicating the issue and then trying your fix.
3. same as #2
4. I normally use vi or nano but I have used some of the ones you listed so I will try one of those.

I have a fresh install using the LinuxCNC 2.8.2 Debian 10 Buster PREEMPT-RT ISO. I have my machine up and running. It most of the day to get this far. I Hate Debian and xfce. Mint 19.3 just works with almost no effort.
OK back on track. As usually happens with this kind of stuff I can't make it fail now. I'll keep trying though. There were times in the past when I thought "oh it must have gotten fixed in the update" then bam, it was back.

I'll keep trying and when it fails I'll get the additional info and try removing the P4S pendant stuff and test again. If I get it to fail again I'll get the test fix installed. I need to read up on that as I don't know how to build the deb yet.

Thank you for your work on this dgarrett.

John

I've done some more testing and I am not seeing the issue. However I noticed that the version I am now running is 2.8.2-11-g6a3d0a434 and the version where I was last having the issue was 2.8.2-144. Could it be that the version that is is the distro is prior to when the issue was introduced?

I was suprised that after the fresh install that it didn't update to 2.8.2-144. I must have something setup incorrectly. Right now the machine seems to be working great so maybe I should just leave well enough alone.

One other issue seems to be also solved. I was chasing an issue with my M6 remap where I was getting inconsistant results when measuring variable length tools. The test block I am cutting is now spot on. In the 2.8.2-144 vesion my results were not repeating that accuartely. Next I am going to go back and repeat some of the other tests where I was getting inconsistant results and see what they look likr now.

Thank you Dewey for your work on this.