- Posts: 5712
- Thank you received: 0
#<holes> = 3 - Unexpected behaviour
2 years 2 months ago #308658
by phillc54
Replied by phillc54 on topic #<holes> = 3 - Unexpected behaviour
There must be an issue with pathing differences between package installs and run in place installs...
Try this as a workaround from a terminal:
Then restart linuxcnc again.
Try this as a workaround from a terminal:
Code:
mkdir -p ~/linuxcnc/nc_files/m_files
cp ~/usr/share/doc/linuxcnc/examples/nc_files/plasmac/m_files/* ~/linuxcnc/nc_files/m_files/
Please Log in to join the conversation.
2 years 2 months ago #308660
by CFE
Replied by CFE on topic #<holes> = 3 - Unexpected behaviour
Hi Phil,
I get this :
plasma@plasma:~$ mkdir -p ~/linuxcnc/nc_files/m_files
plasma@plasma:~$ cp ~/usr/share/doc/linuxcnc/examples/nc_files/plasmac/m_files/* ~/linuxcnc/nc_files/m_files/
cp: cannot stat '/home/plasma/usr/share/doc/linuxcnc/examples/nc_files/plasmac/m_files/*': No such file or directory
This is out of my territory I am afraid
I get this :
plasma@plasma:~$ mkdir -p ~/linuxcnc/nc_files/m_files
plasma@plasma:~$ cp ~/usr/share/doc/linuxcnc/examples/nc_files/plasmac/m_files/* ~/linuxcnc/nc_files/m_files/
cp: cannot stat '/home/plasma/usr/share/doc/linuxcnc/examples/nc_files/plasmac/m_files/*': No such file or directory
This is out of my territory I am afraid
Please Log in to join the conversation.
2 years 2 months ago #308662
by phillc54
Replied by phillc54 on topic #<holes> = 3 - Unexpected behaviour
My bad...
Need to remove the ~ from the beginning of the second line:
Need to remove the ~ from the beginning of the second line:
Code:
cp /usr/share/doc/linuxcnc/examples/nc_files/plasmac/m_files/* ~/linuxcnc/nc_files/m_files/
Please Log in to join the conversation.
2 years 2 months ago #308663
by CFE
Replied by CFE on topic #<holes> = 3 - Unexpected behaviour
No success Phil, I still get the M190 related error, see screenshot attached. I must admit I have never used sim configurations, so this is out of my depth
Please Log in to join the conversation.
2 years 2 months ago #308665
by phillc54
Replied by phillc54 on topic #<holes> = 3 - Unexpected behaviour
No worries, this is distracting us from your main issue anyway.
I really don’t know what is going on with the velocity as it works fine here. I will have a play in the morning and see if anything odd happens.
I really don’t know what is going on with the velocity as it works fine here. I will have a play in the morning and see if anything odd happens.
Please Log in to join the conversation.
2 years 2 months ago #308667
by CFE
Replied by CFE on topic #<holes> = 3 - Unexpected behaviour
Thank you Phil, I will have a deeper look here too.
Please Log in to join the conversation.
2 years 2 months ago #308671
by CFE
Replied by CFE on topic #<holes> = 3 - Unexpected behaviour
I have attached a short video made with PEEK which shows the velocity increase at the last leg of the contour. Maybe this gives a bit more insight in the issue we're facing.
Cheers, Peter
Cheers, Peter
Please Log in to join the conversation.
2 years 2 months ago #308674
by phillc54
Replied by phillc54 on topic #<holes> = 3 - Unexpected behaviour
Could you open halmeter from a terminal and select the pin plasmac.feed-reduction and then do another video. It should change to 60 as it begins each fillet end return to 0 at the end of each fillet.
Please Log in to join the conversation.
2 years 2 months ago #308756
by CFE
Replied by CFE on topic #<holes> = 3 - Unexpected behaviour
Hi Phil,
I had a chance to make up a video with HAL Meter and the feed reduction stays at 60% except for the last leg.
Cheers, Peter
I had a chance to make up a video with HAL Meter and the feed reduction stays at 60% except for the last leg.
Cheers, Peter
Please Log in to join the conversation.
2 years 2 months ago #308757
by phillc54
Replied by phillc54 on topic #<holes> = 3 - Unexpected behaviour
The feed-reduction pin should be directly connected to motion.analog-out-03 which should be switched by the M67 E3 Qn g-code commands.
Could you look at motion.analog-out-03 with HAL Meter and see what it does.
They do change state correctly here.
Could you look at motion.analog-out-03 with HAL Meter and see what it does.
They do change state correctly here.
Please Log in to join the conversation.
Time to create page: 0.131 seconds
