- Posts: 185
- Thank you received: 57
wrong dro after start, and axis tool change window
4 years 11 months ago #226473
by DoWerna
wrong dro after start, and axis tool change window was created by DoWerna
It's about my Maho MH500,
forum.linuxcnc.org/42-deutsch/42077-maho...-plugandplay?start=0
running with linuxcnc 2.8.2 and gmoccapy.
Beforehand the machine was configured with this basic configuration.
forum.linuxcnc.org/30-cnc-machines/41442...tion?start=20#204531
so started with Axis, and then only changed to gmoccapy in the configuration.
What I noticed now is that after the homing the wrong DRO is displayed first
G58 is displayed, but with the machine coordinates on the right. If I really want to see g58, for example, I must first call a g57 and back again aug G58, then the DRO output is also correct.
Have googled , on github I have found exactly such an issue from 2016.
github.com/LinuxCNC/linuxcnc/issues/157
The next thing would be the tool change.
works fine , but with the axis window.
Probably because my configuration was only changed to gmoccapy, from axis.
Afterwards I have to look again at the connections in the Hal and compare them with a gmoccapy example
but at least with the DRO story I'm quite at a loss
My configuration folder is on github
github.com/DoWerna/maho_retrofit/blob/master/basic7i97.hal
github.com/DoWerna/maho_retrofit/blob/master/basic7i97.ini
github.com/DoWerna/maho_retrofit/blob/master/custom_postgui.hal
and the entire folder
github.com/DoWerna/maho_retrofit
forum.linuxcnc.org/42-deutsch/42077-maho...-plugandplay?start=0
running with linuxcnc 2.8.2 and gmoccapy.
Beforehand the machine was configured with this basic configuration.
forum.linuxcnc.org/30-cnc-machines/41442...tion?start=20#204531
so started with Axis, and then only changed to gmoccapy in the configuration.
What I noticed now is that after the homing the wrong DRO is displayed first
G58 is displayed, but with the machine coordinates on the right. If I really want to see g58, for example, I must first call a g57 and back again aug G58, then the DRO output is also correct.
Have googled , on github I have found exactly such an issue from 2016.
github.com/LinuxCNC/linuxcnc/issues/157
The next thing would be the tool change.
works fine , but with the axis window.
Probably because my configuration was only changed to gmoccapy, from axis.
Afterwards I have to look again at the connections in the Hal and compare them with a gmoccapy example
but at least with the DRO story I'm quite at a loss
My configuration folder is on github
github.com/DoWerna/maho_retrofit/blob/master/basic7i97.hal
github.com/DoWerna/maho_retrofit/blob/master/basic7i97.ini
github.com/DoWerna/maho_retrofit/blob/master/custom_postgui.hal
and the entire folder
github.com/DoWerna/maho_retrofit
Please Log in or Create an account to join the conversation.
4 years 11 months ago #226571
by DoWerna
Replied by DoWerna on topic wrong dro after start, and axis tool change window
Just test renamed the .var .pref files and restarted the machine.
Unfortunately without success the DRO still shows the wrong values at startup.
Only when I run a G55 and G54 the G54 values are displayed.
Unfortunately without success the DRO still shows the wrong values at startup.
Only when I run a G55 and G54 the G54 values are displayed.
Please Log in or Create an account to join the conversation.
4 years 11 months ago #226575
by MaHa
Replied by MaHa on topic wrong dro after start, and axis tool change window
Did you try in [RS274NGC] section to enter a startup code with the desired UCS
Code:
RS274NGC_STARTUP_CODE = G0 G17 G21 G40 G49 G55 G80 G90 G92.1 G94 M48
The following user(s) said Thank You: DoWerna
Please Log in or Create an account to join the conversation.
4 years 11 months ago #226586
by DoWerna
Replied by DoWerna on topic wrong dro after start, and axis tool change window
Yes
I have just inserted the line.
but has unfortunately brought nothing.
After homing, the Abs coordinates are always displayed in the DRO, although the values in the DRO are labeled with G55.
to see the real G55 values you need a G54 and then G55
I have just inserted the line.
but has unfortunately brought nothing.
After homing, the Abs coordinates are always displayed in the DRO, although the values in the DRO are labeled with G55.
to see the real G55 values you need a G54 and then G55
Please Log in or Create an account to join the conversation.
4 years 11 months ago #226606
by DoWerna
Replied by DoWerna on topic wrong dro after start, and axis tool change window
in the githubissue the problem was solved by recompiling everything.
What I have done so far
sudo apt remove linuxcnc-uspace
sudo apt autoremove
sudo apt install linuxcnc-uspace
so linuxcnc including dependencies deleted and reinstalled.
This has brought nothing
Possibly it has similar reasons with me,
I started the machine configuration with 2.9 from the buildbot, my 7i97 was not supported by 2.8.
have then later changed to the stable 2.8.2...
Translated with www.DeepL.com/Translator (free version)
What I have done so far
sudo apt remove linuxcnc-uspace
sudo apt autoremove
sudo apt install linuxcnc-uspace
so linuxcnc including dependencies deleted and reinstalled.
This has brought nothing
Possibly it has similar reasons with me,
I started the machine configuration with 2.9 from the buildbot, my 7i97 was not supported by 2.8.
have then later changed to the stable 2.8.2...
Translated with www.DeepL.com/Translator (free version)
Please Log in or Create an account to join the conversation.
4 years 11 months ago #226649
by DoWerna
Replied by DoWerna on topic wrong dro after start, and axis tool change window
wiped through a bit again
sudo apt purge linuxcnc-uspace
sudo apt --purge autoremove
sudo apt purge mesaflash
sudo apt --purge autoremove
sudo apt update
sudo apt dist-upgrade
sudo apt install linuxcnc-uspace-dev
sudo apt install mesaflash
Now it seems to work
sudo apt purge linuxcnc-uspace
sudo apt --purge autoremove
sudo apt purge mesaflash
sudo apt --purge autoremove
sudo apt update
sudo apt dist-upgrade
sudo apt install linuxcnc-uspace-dev
sudo apt install mesaflash
Now it seems to work
Please Log in or Create an account to join the conversation.
Time to create page: 0.256 seconds