#linuxcnc-devel Logs

Jul 09 2023

02:03 AM pere: andypugh_: I noticed your commit c15ac50957f341a0ed35d8aa2b2757f108816104. Are you aware that if the commit message include 'Fixes #2530', a link to the issue will be created in github and the issue will be closes?
02:32 AM rmu: andypugh_: what compiler do you use?
05:16 AM -!- #linuxcnc-devel mode set to +v by ChanServ
05:17 AM -!- #linuxcnc-devel mode set to +v by ChanServ
05:21 AM -!- #linuxcnc-devel mode set to +v by ChanServ
05:50 AM andypugh_: rmu: gcc I assume. I just type :make”
05:57 AM rmu: compiler version can make a difference in theory
06:41 AM andypugh_: Both systems have gcc (Debian 8.3.0-6) 8.3.0 (and are a standard Buster install from the LinuxCNC ISO)
06:44 AM pere: andypugh_: can you share a clue with your trick to extend limits during tool change? Setting the 'sel' pin extend the range, but deselecting the pin do not reset it back to the limited range. I can manually move the head past the limits.
06:47 AM andypugh_: The ini.Y.max_limit and ini.Z.max_limit pins are what I change. Monitor those are see if the values are reverting?
06:48 AM andypugh_: There may be a need to also fiddle with ini.0 and ini.1 pins for unhomed mode. But then you can’t do a tool change when not homed (or, you certainly shouldn’t try)
08:39 AM pere: andypugh_: the values are reverting, but can still move past them.
08:40 AM andypugh_: Are you homed?
08:41 AM pere: yes.
08:45 AM andypugh_: rene-dev5: For the moment I have deleted the limit_axis component. It isn’t what I want to be working on.
08:45 AM andypugh_: pere: Will G-code go past the limit, or just jogging?
08:45 AM pere: do not know, will test.
08:45 AM andypugh_: Are joint limits being set, or just axis?
09:00 AM pere: I checked both ini.1.max_limit and ini.y.max_limit, and both are set. I can not use G0 to go past the limit.
09:00 AM pere: the very strange thing is that now I can no longer reproduce it with jogging. now it behave as I want it to behave.
11:16 AM rmu: pere: look here, Z-axis limits is changed when toolchanging https://github.com/laserK3000/tc215Retrofit/tree/master/configs/brotherTC215
11:17 AM rmu: https://github.com/laserK3000/tc215Retrofit/blob/c051a0048563cf2300cfbfbe115b778080914d6b/configs/brotherTC215/brotherTC215.hal#L294
11:18 AM pere: rmu: thanks. it is similar to how it is done in the setup I am looking at, <URL: https://github.com/SebKuzminsky/MazakVQC1540 > branch bon-dev.
11:30 AM rene-dev5: Andypugh I can have a look at the build system
02:00 PM -!- #linuxcnc-devel mode set to +v by ChanServ
05:11 PM -!- #linuxcnc-devel mode set to +v by ChanServ
05:34 PM -!- #linuxcnc-devel mode set to +v by ChanServ
07:27 PM fdarling: seb_kuzminsky: have you worked on the HostMot 2 encoder velocity code? I have some questions about how the estimation works when there is less than 1 count per servo thread sate sample...
07:28 PM fdarling: *sate = rate
08:11 PM linuxcnc-build2: Build [#1163](http://buildbot2.highlab.com/buildbot/#builders/11/builds/1163) of `10-rip.debian-12-bookworm-rtpreempt-amd64` 4failed.
08:17 PM linuxcnc-build2: Build [#1228](http://buildbot2.highlab.com/buildbot/#builders/13/builds/1228) of `00-checkin` 4failed.