2.7.15
- jazial
- Offline
- Junior Member
Less
More
- Posts: 21
- Thank you received: 1
12 Feb 2020 11:51 #157165
by jazial
2.7.15 was created by jazial
Hello,
I've upgraded to 2.7.15 and path is not accurate
Slots are not straight
Circles are oval
Downgraded to 2.7.14 and everything is fine
maybe some bug in release, or do I have to tune something ?
I've upgraded to 2.7.15 and path is not accurate
Slots are not straight
Circles are oval
Downgraded to 2.7.14 and everything is fine
maybe some bug in release, or do I have to tune something ?
Please Log in or Create an account to join the conversation.
- tommylight
- Offline
- Moderator
Less
More
- Posts: 19516
- Thank you received: 6547
12 Feb 2020 11:58 #157167
by tommylight
Replied by tommylight on topic 2.7.15
Add G64 P0.1 to the gcode file for mm machine or
G64 P0.01 for imperial
the 0.1 or 0.01 is the actual distance that the machine is allowed to stray off the path.
G64 P0.01 for imperial
the 0.1 or 0.01 is the actual distance that the machine is allowed to stray off the path.
Please Log in or Create an account to join the conversation.
- jazial
- Offline
- Junior Member
Less
More
- Posts: 21
- Thank you received: 1
12 Feb 2020 12:07 #157170
by jazial
Replied by jazial on topic 2.7.15
Here is the program beginning
G21 G40 G49 G64 P0.05
G17
G54
T28 M6
G43 H28
G0 Z78.000
Please Log in or Create an account to join the conversation.
- andypugh
- Offline
- Moderator
Less
More
- Posts: 23178
- Thank you received: 4861
26 Feb 2020 22:25 #158578
by andypugh
Are you using exactly the same config files in each case, or did you re-create your configs?
Release notes are here: github.com/LinuxCNC/linuxcnc/blob/ba122d...a8c/debian/changelog
Replied by andypugh on topic 2.7.15
Hello,
I've upgraded to 2.7.15 and path is not accurate
Slots are not straight
Circles are oval
Downgraded to 2.7.14 and everything is fine
maybe some bug in release, or do I have to tune something ?
Are you using exactly the same config files in each case, or did you re-create your configs?
Release notes are here: github.com/LinuxCNC/linuxcnc/blob/ba122d...a8c/debian/changelog
Please Log in or Create an account to join the conversation.
- PCW
- Away
- Moderator
Less
More
- Posts: 17991
- Thank you received: 4838
26 Feb 2020 23:22 #158580
by PCW
Replied by PCW on topic 2.7.15
Can you post your hal/ini files?
A PID component change could be the cause of this error
A PID component change could be the cause of this error
Please Log in or Create an account to join the conversation.
- jazial
- Offline
- Junior Member
Less
More
- Posts: 21
- Thank you received: 1
27 Feb 2020 08:45 #158604
by jazial
Replied by jazial on topic 2.7.15
I've just upgraded.
The only change is linuxcnc version from 2.7.14 to 2.7.15
The only change is linuxcnc version from 2.7.14 to 2.7.15
Please Log in or Create an account to join the conversation.
- jazial
- Offline
- Junior Member
Less
More
- Posts: 21
- Thank you received: 1
27 Feb 2020 08:50 #158605
by jazial
Replied by jazial on topic 2.7.15
Here are the files
Please Log in or Create an account to join the conversation.
- andypugh
- Offline
- Moderator
Less
More
- Posts: 23178
- Thank you received: 4861
27 Feb 2020 10:13 - 27 Feb 2020 10:13 #158614
by andypugh
Replied by andypugh on topic 2.7.15
So, it's an analogue servo system, so the problem could be this:
In fact, I see this in your HAL:But it seems that you might have an error in your HAL as there is nothing driving that signal elsewhere in the HAL. so the velocity command will always be zero and your FF1 term will be ineffective.
So, possibly, an error in your HAL has been masked by a bug in LinuxCNC.
If you comment-out the pid.L.command-deriv lines then you should be back where you were.
Better might be to leave those lines in and addfor each axis. But that might require some re-tuning of the FF1 PID terms.
The explanation here is that the PID component was meant to calculate velocity command internally if the pin was not connected, and use the supplied value if it was. But it was always calculating it internally. This took some time to be noticed, as it works nearly the same.
* pid: use command-deriv when supplied
In fact, I see this in your HAL:
net x-vel-cmd => pid.x.command-deriv
So, possibly, an error in your HAL has been masked by a bug in LinuxCNC.
If you comment-out the pid.L.command-deriv lines then you should be back where you were.
Better might be to leave those lines in and add
net L-vel-cmd axis.N.joint−vel−cmd
The explanation here is that the PID component was meant to calculate velocity command internally if the pin was not connected, and use the supplied value if it was. But it was always calculating it internally. This took some time to be noticed, as it works nearly the same.
Last edit: 27 Feb 2020 10:13 by andypugh.
Please Log in or Create an account to join the conversation.
- jazial
- Offline
- Junior Member
Less
More
- Posts: 21
- Thank you received: 1
27 Feb 2020 10:39 #158617
by jazial
Replied by jazial on topic 2.7.15
Thanks
I will try
If a bug fix an error, is it still a bug ?
I will try
If a bug fix an error, is it still a bug ?
Please Log in or Create an account to join the conversation.
- bbsr_5a
- Offline
- Platinum Member
Less
More
- Posts: 544
- Thank you received: 105
27 Feb 2020 12:41 #158627
by bbsr_5a
Replied by bbsr_5a on topic 2.7.15
many now did run in this problem as i see in the last 14days
so it needs to be fixed as quick as posible in the Master and buildbot
so it needs to be fixed as quick as posible in the Master and buildbot
Please Log in or Create an account to join the conversation.
Time to create page: 0.069 seconds