#hazzy Logs
Apr 07 2020
#hazzy Calendar
04:50 AM jthornton: morning
04:52 AM TurBoss: Morning
05:55 AM hazzy-m: morning
08:52 AM roguish[m]: good morning all. a cold and foggy day here. we get 'valley fog.' caused by a temperature inversion in the San Jauquine valley to the east. cold, sits at just about 40 def F.
09:05 AM TurBoss: helloroguish: here we had pre industry polution
11:17 AM * jthornton just got back from 12 miles of mountain biking
12:20 PM RacoonRider[m]: i am a little confused after e pull of probe_basic my machine didnt show the 4th axis. if i change it in settings it didn't remember.
12:21 PM RacoonRider[m]: anoter is the subcall on toolchange. can i disable it?
12:31 PM RacoonRider[m]: the call of m6_tool_call_main_panel.ngc seems hardcoded.
12:31 PM RacoonRider[m]: my M6 is remapped to messen
12:31 PM * RacoonRider[m] sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/zbqZUGMewFGwWzbtTAFeBegT >
12:31 PM RacoonRider[m]: But LCNC don't care about it.
01:33 PM hazzy-m: Lcvette: do you want a chipped 2016 X5M? 30k miles
01:37 PM hazzy-m: owner has lost $800k since this corona mess, and is trying to dump it...
01:41 PM Lcvette: how much?
01:48 PM Lcvette: hazzy: how do you make the jog increment travel the full distance per button click? someone on the forum is wanting that functionality and i can't remember what to do to make it that way
01:54 PM Lcvette: RacoonRider | MovT: you can change the subroutine to whatever you like. i set it up so it would actgivate certain codes as well as work with tool touch off and the new coolant angle output functionality available in the gui, but you can go in and change it to whatever you like on the subroutines. i recommend making a backup of them just in case.
01:55 PM hazzy-m: Lcvette: hey!
01:56 PM Lcvette: o/
01:56 PM hazzy-m: I can't remember how to change it so it jogs a fixed distance either
01:56 PM hazzy-m: I'll have to check in the code
01:56 PM Lcvette: ok
02:12 PM RacoonRider[m]: @Lcvette i already done that before in the ini. Do i need to change it in the probe_basic.ui???
02:12 PM Lcvette: the m6 buttons all call for subroutines from the subroutine folder
02:12 PM Lcvette: you can change it in the ui in designer or change the subroutines to suit
02:15 PM RacoonRider[m]: I used the RS274NGC section in the ini, is that obsolete?
02:16 PM RacoonRider[m]: or is that anyway not the right way to remap m commands?
02:17 PM Lcvette: that is the way you remap
02:17 PM Lcvette: i also remap in the ini for my atc
02:17 PM Lcvette: but the sub routine calls from the m6 buttons work in conjunction with the remap
02:18 PM Lcvette: its not one or the other
02:18 PM Lcvette: the m6 button subs are there to make manual tool changing work flawlessly
02:18 PM Lcvette: with the desired functions
02:19 PM Lcvette: ie setting tool offsets, tool touch off, programmable coolant
02:19 PM Lcvette: but again you can set things up however you want
02:23 PM RacoonRider[m]: Yea i understand. The thing is, i hve changed the m6_tool...ngc to my script and got error messages about missing for o<m6_tool....>
02:23 PM Lcvette: so go into the ui and remove the sub calls
02:24 PM Lcvette: change the buttons from sub call buttons to mdi buttons and just put an M6 in the mdi command line for the button
02:24 PM Lcvette: then everything will be soley for yourt remaps
02:25 PM Lcvette: you must change ALL of the M6 buttons in that scenario
08:27 PM RacoonRider[m]: i dont understand why the change crack my m6 mapping in the ini. i guess i am not the only one who do it this way and ran in this error.