#hazzy | Logs for 2020-07-11
Back
[00:45:28] * TurBoss uploaded an image: Captura de pantalla de 2020-07-11 06-44-56.png (42KB) < https://matrix.org >
[00:46:02] <TurBoss> hands: the super should call ProbeBasicVertcal too
[00:57:13] -!- c-log has quit [Ping timeout: 264 seconds]
[01:05:36] -!- c-log has joined #hazzy
[02:00:37] -!- cerna1 has joined #hazzy
[02:01:11] -!- joe[m]11 has joined #hazzy
[02:01:30] -!- cerna has quit [Ping timeout: 256 seconds]
[02:01:32] -!- joe[m]1 has quit [Ping timeout: 256 seconds]
[02:02:31] -!- alex[m]15 has joined #hazzy
[02:02:31] -!- alex[m] has quit [Ping timeout: 256 seconds]
[02:03:21] -!- Watze[m] has quit [Ping timeout: 256 seconds]
[02:03:48] -!- Watze[m] has joined #hazzy
[02:04:36] -!- karl[m]11 has joined #hazzy
[02:05:56] Watze[m] is now known as 21WAAB4B0
[02:05:56] -!- karl[m]1 has quit [Ping timeout: 256 seconds]
[02:06:39] <Joco[m]> question: getting lost in a pile of forum threads on HAL. Any of you guys know how to us a hal pin that is IO (i.e. has both In and Out). When I try and link it to a qtpyvcp hal button Out pint via a net command I get an error about not being able to add the Out pin of the button.
[02:08:26] <Joco[m]> * question: getting lost in a pile of forum threads on HAL. Any of you guys know how to us a hal pin that is IO (i.e. has both In and Out). When I try and link it to a qtpyvcp hal button Out pin via a net command I get an error about not being able to add the Out pin of the button.
[02:20:38] <TurBoss> you need to do net on postgui hal
[02:20:49] <TurBoss> hal postgui
[02:21:51] <TurBoss> @joco
[02:24:28] <Joco[m]> had this line in a hal file called in the postgui_call_list.hal
[02:24:28] <Joco[m]> ```
[02:24:28] <Joco[m]> net glass-scale-reset <= [HMOT](CARD0).7i76.0.0.enc0.reset => qtpyvcp.halbtn-resetEnc0.out
[02:24:40] <Joco[m]> still got error
[02:26:24] * Joco[m] uploaded an image: image.png (8KB) < https://matrix.org >
[02:26:30] <Joco[m]> from halshow
[02:26:45] <Joco[m]> the challenge seems to be that the Direction is both In/Out
[02:27:28] <Joco[m]> hang on let me get it to fail and I'll post the exact error message
[02:31:17] * Joco[m] sent a long message: < https://matrix.org >
[02:32:27] <Joco[m]> bit stumped at the moment.
[02:38:07] <Joco[m]> I can do a manual setp via halshow no probs
[02:38:39] <Joco[m]> TurBoss: so if you have some more good ideas, I'm all ears. 🙂
[02:40:54] -!- JT-Cave has quit [Ping timeout: 240 seconds]
[02:41:26] -!- JT-Shop_ has quit [Ping timeout: 258 seconds]
[02:42:51] -!- jthornton has joined #hazzy
[02:44:14] -!- JT-Shop has joined #hazzy
[03:05:33] <TurBoss> Joco: whats the goal?
[03:05:34] <TurBoss> :P
[03:06:04] <TurBoss> ```
[03:06:04] <TurBoss> net glass-scale-reset qtpyvcp.halbtn-resetEnc0.out <= [HMOT](CARD0).7i76.0.0.enc0.reset
[03:07:11] <Joco[m]> I have this glass scale linked to enc0 on the 7i76 in mode 2. This is one of the MPG encoders. I want to use this to map the ballscrew in an autmated manner. So when I home the axis I need to reset the encoder to zero so that measurements are from the correct reference.
[03:07:33] <TurBoss> ahhhh
[03:07:37] <Joco[m]> I could do it by hand using halshow and a setp command. That is how I have been testing. But that seems really manky
[03:07:50] <Joco[m]> so want to link to a btn in gui if at all possible
[03:07:56] <Joco[m]> for ease of use
[03:08:25] <Joco[m]> eventually I will get a real encoder add on board as I want to mount these scales permanently and use them to inform eoffsets
[03:08:46] * TurBoss sent a long message: < https://matrix.org >
[03:09:12] <TurBoss> should be in?
[03:09:15] <Joco[m]> yes
[03:09:20] <Joco[m]> no its a button
[03:09:32] <TurBoss> ok
[03:09:57] <TurBoss> do the button show in halmeter?
[03:10:02] <Joco[m]> yes
[03:10:09] <TurBoss> 🤔
[03:10:17] <Joco[m]> visiible in halshow
[03:10:57] <Joco[m]> let me start machine up so I can take some halshow snips
[03:11:03] <TurBoss> oki
[03:13:20] * Joco[m] uploaded an image: image.png (31KB) < https://matrix.org >
[03:14:15] * Joco[m] uploaded an image: image.png (33KB) < https://matrix.org >
[03:15:12] <Joco[m]> its like a need to have an intermediate component that has an IO link on one side and on the other separated IN and OUT pins
[03:15:42] <TurBoss> qtpyvcp.halbtn-resetEnc0.out is OUT only
[03:15:52] <Joco[m]> I know
[03:15:58] <Joco[m]> that's the problem
[03:16:29] <TurBoss> you want to add IO to halbtn?
[03:16:50] <Joco[m]> but what can I put in the middle to act as an agent to allow the linkage?
[03:17:03] <TurBoss> in the main python
[03:17:06] <TurBoss> of thevcp
[03:17:10] <TurBoss> * of the vcp
[03:17:12] <Joco[m]> ok
[03:17:28] <TurBoss> hmmm
[03:17:48] <TurBoss> meybe we can add a setenable I bit to hal btl
[03:17:56] <Joco[m]> I will hunt through all the HAL docs and see if there is an existing component that will solve this. I can NOT be the first person hitting this.
[03:19:01] <Joco[m]> there is where lcnc is weak. The HAL documentation is skimpy and the IP in the forums is a nightmare to wade through
[03:19:43] <TurBoss> clicked is a good nema?
[03:19:57] <Joco[m]> huh?
[03:26:15] * TurBoss uploaded an image: Captura de pantalla de 2020-07-11 09-25-59.png (92KB) < https://matrix.org >
[03:26:46] <TurBoss> it needs some logic but is working
[03:27:06] * TurBoss uploaded an image: Captura de pantalla de 2020-07-11 09-26-52.png (18KB) < https://matrix.org >
[03:30:58] <Joco[m]> your plc gadget?
[03:31:32] <TurBoss> just added a in pin to the hal button
[03:32:20] <Joco[m]> so - would that allow it to be connected to an IO pin?
[03:33:41] <TurBoss> yes
[03:36:48] <Joco[m]> ok - will see if I can figure out how to do that
[03:37:22] <TurBoss> I'm doing
[03:37:41] <TurBoss> I'mt trying to figure some logic stuff
[03:37:58] <Joco[m]> rgr
[03:42:10] -!- c-log has quit [Ping timeout: 265 seconds]
[03:44:04] -!- c-log has joined #hazzy
[04:15:07] <TurBoss> Joco: I can't figure how to hook the logic correctly
[04:16:17] * TurBoss uploaded an image: Captura de pantalla de 2020-07-11 10-15-58.png (162KB) < https://matrix.org >
[04:22:08] <Joco[m]> I'll have a look later. Watching movie at the moment. 8:22pm here
[04:36:36] <TurBoss> okay
[05:04:33] -!- JT-Shop has quit [Read error: Connection reset by peer]
[05:04:54] -!- JT-Shop has joined #hazzy
[06:08:16] <jthornton> morning
[06:18:40] jthornton is now known as JT-Cave
[06:26:47] <TurBoss> hello
[06:27:45] <TurBoss> jthornton: how are your sercos devices?
[06:27:50] <TurBoss> just curious
[06:28:02] <TurBoss> wich model
[06:28:11] <JT-Cave> the Koreans are working on it via my laptop and TeamViewer
[06:28:28] <JT-Cave> allen bradley sercos device
[06:28:37] <TurBoss> cool
[06:28:40] <TurBoss> great
[06:28:41] <JT-Cave> http://www.plctalk.net
[06:29:48] <JT-Cave> I think it is not a program issue as I found out the start of the problem was a night shift maintenance guy blew it out with the power on and that's when it died
[06:30:06] <TurBoss> oh :(/
[06:31:24] <JT-Cave> I'm thinking the Kinetix 2000 drives are the issue
[06:40:28] <Joco[m]> TurBoss: might have cracked it. Just coded an activated io pin on the hal_button and blended it into the logic of the existing press code. Hooked it up and works. The next part would be for it to honour a True value coming in. Not sure how that would be used. At the moment its just sink for incoming.
[06:41:21] <TurBoss> you did?
[06:41:51] * Joco[m] posted a file: hal_button.py (3KB) < https://matrix.org >
[06:42:37] <Joco[m]> just tested it on real machine. HAL now works and the gui button activates the reset pin on the encoder
[06:42:57] <Joco[m]> see attached file above
[06:45:08] <TurBoss> great
[06:45:14] <TurBoss> I'm booting dev
[06:58:05] <Joco[m]> TurBoss: not saying it’s great. Just it worked.
[06:58:12] <TurBoss> xD
[06:58:19] <TurBoss> just testing
[06:58:27] <TurBoss> did you make the button checkable?
[07:03:14] <TurBoss> we need a keep
[07:03:52] * TurBoss uploaded an image: Captura de pantalla de 2020-07-11 13-03-32.png (16KB) < https://matrix.org >
[07:04:58] <Joco[m]> Nope. Just a push button. Not on/off.
[07:05:21] <TurBoss> then that should work
[07:06:57] <Joco[m]> Yup. It’s working on my real rig. Just used it to setup a test of the automated mapping gcode I have from the forums. Just did 256 samples going in positive and negative directions with the scale readings all being correctly recorded to file.
[07:08:25] <Joco[m]> pretty awesome to watch the machine just doing all this automatically
[07:08:45] <TurBoss> little vid?
[07:08:52] <TurBoss> :P
[07:09:18] <Joco[m]> lol - not very interesting to watch. But will be doing another run in a few mins. Will take a short vid and post
[07:09:28] <TurBoss> great
[07:09:43] <TurBoss> so I will know whats this about lol
[07:09:54] <Joco[m]> lol
[07:09:58] <Joco[m]> ball screw mapping
[07:10:07] <TurBoss> that means?
[07:10:11] <TurBoss> lol
[07:10:50] <TurBoss> hehehe
[07:11:52] <Joco[m]> you basically measure the machine travel v's an independent measure of travel (e.g. DRO scale) and record that info for the same set of distance points going from in one direction then going back in the other. (e.g. from 0 to max travel, then from max travel back to 0).
[07:12:24] <Joco[m]> This is put into a specific format used by the linuxcnc screw compensation processing.
[07:12:36] <TurBoss> ohhhhhhhhhhhh
[07:12:44] <TurBoss> ahhhhh
[07:12:45] <Joco[m]> It allows lcnc to cope with the variations that exist in C7 ball screws
[07:12:48] <TurBoss> innteresting
[07:12:51] <Joco[m]> as well as backlash
[07:12:53] <TurBoss> sorry didin't know bout
[07:13:01] <Joco[m]> that's ok
[07:13:47] <Joco[m]> if you have high spec ball screws you wouldn't need it. But for C7 where there is variation in the pitch of the screw even if you have double nuts.
[07:14:08] <Joco[m]> It has the potential to really tighten things up.
[07:14:13] <Joco[m]> Well that's the plan anyway
[07:15:00] <TurBoss> i think i have it
[07:18:46] * TurBoss uploaded an image: Captura de pantalla de 2020-07-11 13-18-29.png (77KB) < https://matrix.org >
[07:19:34] <TurBoss> hmmm 😕 not sure...
[07:20:16] <TurBoss> if value changed i don't need to asign it again
[07:20:40] <TurBoss> the I don't need setButtonDown functio
[07:20:44] <TurBoss> * the I don't need setButtonDown function
[07:21:55] <Joco[m]> are you trying to make it work for a sticky button? i.e. checkable?
[07:22:23] <TurBoss> just trying to sync hal and user click
[07:22:46] <TurBoss> if you set it from hal the click on the button with the mouse
[07:24:44] <Joco[m]> i'm not sure you need to set the pin in the setbutton proc
[07:25:09] <Joco[m]> actually - you might
[07:25:22] <Joco[m]> depends how the the other functions get fired
[07:25:47] <Joco[m]> you should probabltyy be checking it not None as is done in the other functions
[07:25:50] <TurBoss> oh ok
[07:26:22] <Joco[m]> I'm guessing that defensive pattern is there for a reason
[07:26:37] <TurBoss> not sure
[07:29:47] * TurBoss uploaded an image: Captura de pantalla de 2020-07-11 13-29-29.png (14KB) < https://matrix.org >
[07:29:56] <TurBoss> what do you think?
[07:30:40] <TurBoss> ```
[07:30:40] <TurBoss> setp qtpyvcp.halbutton.io 1
[07:32:20] <TurBoss> I think thoose safeties are there in case the click evenge gets fired before hal gets linked... 🤔
[07:32:37] <TurBoss> * I think thoose safeties are there in case the click event gets fired before hal gets linked... 🤔
[07:32:56] <Joco[m]> could work. Need to step through it to see what is happening
[07:35:53] <TurBoss> Joco: are you managing this from Gcode?
[07:36:20] <Joco[m]> managing what? The rest?
[07:36:35] <Joco[m]> reset
[07:37:24] <TurBoss> I mean you can use
[07:37:24] <TurBoss> ```
[07:37:24] <TurBoss> DEBUG(EVAL(vcp.widget.button).setDown({1})
[07:37:28] <TurBoss> from gcode
[07:37:42] <TurBoss> not sure if correct synyax
[07:37:46] <TurBoss> * not sure if correct syntax
[07:37:54] <Joco[m]> nah - I just get it all setup correctly at start via GUI
[07:38:02] <TurBoss> cool
[07:38:22] <TurBoss> there are also motion pins
[07:38:27] <Joco[m]> not trying to over complicate it. Just had to solve the io v's out problem
[07:38:34] <TurBoss> okay
[07:38:42] <TurBoss> not casino
[07:38:43] <TurBoss> :(
[07:38:45] <TurBoss> :P
[07:38:48] <Joco[m]> the gcode I have is logging correctly
[07:42:09] <Joco[m]> well ... seems to be sort of working. About to have another go. Will do quick video
[07:43:01] <TurBoss> hurray!
[07:45:34] * Joco[m] uploaded a video: video_31eb7a5.mp4 < https://matrix.org >
[07:47:02] <TurBoss> ohhh
[07:47:35] <Joco[m]> Hmmm seems to have chopped it a bit.
[07:47:50] <Joco[m]> Or is that just my phone.
[07:47:54] <TurBoss> so there are absolute encoders?
[07:48:03] <TurBoss> or no
[07:48:52] <Joco[m]> Glass linear scales. So no absolute. Hence why I need to get them to home position and reset the encoder counting.
[07:49:06] <TurBoss> ahhhhhhhhhhhhhhhhhhhhhhh
[07:49:10] <TurBoss> 👂️
[07:49:15] <TurBoss> got it
[07:58:20] <Joco[m]> https://drive.google.com
[07:58:34] <Joco[m]> hopefully better
[07:59:18] <Joco[m]> looks like video up there is ok after all
[07:59:43] <Joco[m]> nice thing about this process is I can set it up and walk away and leave it. :)
[08:00:12] <TurBoss> I just created a branch
[08:00:18] <TurBoss> with the halbutton
[08:05:11] <Joco[m]> cool
[08:05:57] <Joco[m]> running another sample. Going to do 3 or 4 and see how the numbers compare
[08:06:22] <Joco[m]> that will be a tad over 2000 samples
[08:07:11] <Joco[m]> And tomorrow I will tackle the problem of perm mounting these things
[08:13:37] <TurBoss> nite
[08:13:44] <Joco[m]> nite
[09:13:55] <Lcvette> whats crackin?
[09:14:15] <Joco[m]> been hacking halbutton
[09:14:31] <Joco[m]> needed an io pin on it. Think TurBoss has a branch
[09:14:55] <Joco[m]> got screw comp auto creation working. video back a little on chat
[09:15:12] <Joco[m]> now 1:14am and I really should go to bed
[09:15:33] <Lcvette> Nice joco
[09:15:34] <Joco[m]> but just processing a screw compensation file based on 2000 odd samples
[09:15:43] <Lcvette> So how is the accuracy now?
[09:16:22] <Joco[m]> about to build a new compensation file and run the logging code to see how it compares to the dro scale
[09:17:49] <Lcvette> But have you just wanted basic measuring yet?
[09:17:49] <hazzy-m> Joco: nice!!!
[09:21:05] <Joco[m]> <Lcvette "But have you just wanted basic m"> not sure what you mean. Sorry - brain starting to get rathey fuzzy
[09:21:40] <Lcvette> ie commanded move verse dro move amount
[09:22:01] <Joco[m]> yeah - that is what have been measuring
[09:22:03] <Joco[m]> in an automated wat
[09:22:04] <Joco[m]> way
[09:22:32] <Joco[m]> 256 sample in forward direction, 256 sample in reverse (negative) direction
[09:24:00] * Lcvette uploaded an image: image.png (346KB) < https://matrix.org >
[09:25:21] <Lcvette> is that 449.800 vs 449.736?
[09:28:41] <Lcvette> * But have you just tested basic measuring yet?
[09:29:13] <Lcvette> is this with the scrw settings set at 5mm?
[09:31:40] <Joco[m]> step scale has been adjusted based on a reading over ~450mm of travl
[09:31:43] <Joco[m]> STEP_SCALE = -400.266844563042
[09:32:41] <Joco[m]> Otherwise if becomes stupidly out.
[09:33:00] <Lcvette> that was what i am looking for is what was the 5mm setting on that 450mm travel
[09:33:59] <Joco[m]> You could reverse engineer from the scale. 2000 steps per turn
[09:34:02] <Lcvette> vs the dro
[09:34:27] <Lcvette> k
[09:34:34] <Joco[m]> Actually I could do that now. Lol
[09:34:36] <Lcvette> cool looks like you are havign fun!
[09:34:37] <Lcvette> :d
[09:34:46] <Lcvette> * :D
[09:34:49] <Lcvette> \o/
[09:35:08] <Joco[m]> tired. Going to quickly see how this new compensation file goes then call it a note.
[09:35:53] <Joco[m]> You are bang on. Now I have the scale I should use that for a 480mm reading to calc the steps/mm
[09:36:48] <Lcvette> yeah if you have the benefit of the scale its like setting up whatever blocks you want
[09:36:49] <Lcvette> :D
[09:37:12] <Lcvette> im interested to see how far off those screws are
[09:43:12] <Joco[m]> running the logging code with the new compensation file
[09:44:53] <Joco[m]> done in one direction.
[09:45:03] <Joco[m]> max error looks to be about 0,02mm
[09:45:15] <Joco[m]> the vast builk at 0.015mm or less
[09:46:08] <Lcvette> nice
[09:46:34] <Lcvette> sounds like you got it dialed in
[09:46:37] <Joco[m]> every now and then I get a 0.025
[09:46:43] <Lcvette> you should make a deviation graph
[09:46:45] <Joco[m]> on the return run
[09:46:51] <Joco[m]> I will tomorrow
[09:46:59] <Joco[m]> the points are all being logged
[09:47:07] <Lcvette> for how much it had to be corrected to get there
[09:47:56] <Joco[m]> I will do this with no compensation file and the nominal 400/mm step setting
[09:48:06] <Joco[m]> just to see how far off things are.
[09:48:07] <Lcvette> YES!
[09:48:12] <Joco[m]> Graphin that could be interesting
[09:48:17] <Lcvette> that is the hard data i find most interesting
[09:48:24] <Lcvette> to see if it is close to its C7 rating
[09:48:31] <Joco[m]> but tomorrow. I'm knackered. 1:48am here
[09:48:42] <Lcvette> ok,, that is acceptable
[09:48:46] <Lcvette> lol\
[09:48:50] <Lcvette> get soe sleep
[09:48:53] <Joco[m]> lol
[09:48:54] <Lcvette> * get some sleep
[09:50:50] <Joco[m]> i reckon if I can get these scales on proper encoders and do some clever feedback to eoffsets I might be able to get things even tighter. solid compensation file and some 0.01 to 0.02mm dynamic tweaking based on realtime scale feedback. Could be good. lol - will dream that. How sad.
[09:52:52] <Joco[m]> right scale done. Still looks good. Scans in both directions have the vast bulk of errors sub 0.01mm with s prinkling of points with 0.015, 0.02 or 0.025mm error. Overall. orders of magnitude better than it was. Next proof in the pudding will be cutting of course. But at least the base position is much netter than it was.
[10:47:14] -!- jj46 has joined #hazzy
[10:48:02] -!- jj46 has quit [Remote host closed the connection]
[10:51:54] * hazzy-m is a little sad, just had to cut down our last standing peach tree
[10:52:57] <TurBoss> hello
[10:53:03] <hazzy-m> TurBoss: hey
[10:53:28] <TurBoss> sup hazzy ?
[13:42:57] -!- c-log has quit [Ping timeout: 265 seconds]
[13:45:21] -!- c-log has joined #hazzy
[15:14:08] -!- Stran_ge[m] has joined #hazzy
[15:47:43] <TurBoss> hazzy: did you figured the spamminator issue?
[15:48:10] <TurBoss> maybe if you fix could you link it to the #kcjengr_log:jauriarts.org spam room
[15:48:34] <TurBoss> 😲 that room is not on IRC
[15:49:13] <TurBoss> Lcvette: did a lot of work on LATC VCP
[15:49:27] <TurBoss> also hans is helping with VerticalVCP
[16:00:46] <Joco[m]> Morning. I think its morning. Im still fuzzy headed. In bed with ipad trying to wake up. Lol
[16:01:03] <Lcvette> TurBoss: great!!
[16:01:04] <Lcvette> :D
[16:01:06] <TurBoss> morning
[16:01:17] <Lcvette> \o/
[16:01:21] <Lcvette> i love new helpers!
[16:01:35] <Joco[m]> Hans is hands?
[16:01:36] <TurBoss> he did what told me 2 days in 30 mins
[16:01:48] <TurBoss> * also hansd is helping with VerticalVCP
[16:02:00] <TurBoss> * also hands is helping with VerticalVCP
[16:02:02] <TurBoss> yes
[16:02:07] <TurBoss> hands:
[16:02:18] <TurBoss> sorry
[16:02:20] <TurBoss> :OP
[16:02:29] <Joco[m]> Ah. Hard core dev. 20 yrs in the game. Gonna be a big help.
[16:03:14] <Joco[m]> Yeah - him. Hi hands
[16:03:49] <Joco[m]> For when hes back. 😇👍
[16:04:02] <Joco[m]> Gah. Head soooo muzzzy
[16:52:21] <Joco[m]> Right. Ups. And measurements for Lcvette
[16:52:34] <Lcvette> \o/
[17:04:12] <Joco[m]> Lcvette: so we want scale at 400/mm (i.e. nominal) with NO backlash compensation or screw compensation. Yes?
[17:10:29] <hands[m]> I have found a difference in the same control between the normal probe_basic and probe_basic_vertical... Specifically the vertical version has some dynamic properties (statusitem, format, etc) AND a rule... where as the same control only has a rule on the probe_basic template..
[17:10:39] <Lcvette> Joco: yes
[17:11:12] <Lcvette> hands: the vertical is outdated
[17:11:33] <TurBoss> he is updating it :)
[17:11:34] * hands[m] uploaded an image: unknown.png (102KB) < https://matrix.org >
[17:11:41] <hands[m]> vs.
[17:12:05] <Lcvette> vertical needs to have the newer probe basic horizontal items brought over
[17:12:11] * roguish[m] uploaded an image: image.png (61KB) < https://matrix.org >
[17:12:16] <roguish[m]> is it warm out yet ????
[17:12:26] * hands[m] uploaded an image: unknown.png (117KB) < https://matrix.org >
[17:12:41] <hands[m]> however, probe_basic has some controls that still use statusitem.
[17:13:12] <Lcvette> i have not been in the vertical UI in some time
[17:13:14] <hands[m]> are those dynamic properties deprecated and I should move those to rules when I seem them?
[17:13:19] <TurBoss> hands: dynamic properties noremally are remove properties from the widget
[17:13:31] <TurBoss> * hands: dynamic properties noremally are removed properties from the widget
[17:13:57] * Joco[m] uploaded an image: ima_b1ccf63.jpeg (156KB) < https://matrix.org >
[17:14:02] <hands[m]> ok, so when I see them delete them? (just confirming)... but that sounds like what you are suggesting... 🙂
[17:14:09] <Lcvette> i would compare them to the current probe basic and change to the same as the current probe basic style
[17:14:11] <TurBoss> yes safe to delete tem
[17:14:18] <TurBoss> * yes safe to delete them
[17:14:52] <Joco[m]> Lcvette: there you go. That is 0 to 480 move in single go at 200mm/min
[17:14:54] <Lcvette> and be careful the naming conventions remain the same as many of the items are connecte to subroutine calls
[17:14:55] <hands[m]> I am about 3/4 the way through the controls that are on all the screens.. then on to the middle switchable space.
[17:15:13] <hands[m]> Lcvette, that is what I am doing, control by control..
[17:15:21] <hands[m]> but this was soo different I wanted to confirm 🙂
[17:15:33] <Lcvette> awesome and thank you!
[17:15:48] <Lcvette> Joco: that looks pretty bad
[17:15:50] <Lcvette> :o
[17:16:06] <Lcvette> hands: yes different because so outdated
[17:16:16] <TurBoss> hands: in the main py file just saw a little thing :)we need to rename the ProbeBasic in supper car too
[17:16:24] <hazzy-m> hands: yes, statusItem has been removed (just confirming the confirmation lol)
[17:16:27] <TurBoss> * hands: in the main py file just saw a little thing :)we need to rename the ProbeBasic in supper call too
[17:16:34] <Joco[m]> 0.26mm our
[17:16:37] <Lcvette> i figured once probe basic was finished and locked down i would update instead of continuously updating two
[17:16:41] <Joco[m]> * 0.26mm out
[17:16:58] <Lcvette> but thanks to you it will get done sooner!
[17:16:59] <Lcvette> :D
[17:17:01] <Lcvette> \o/
[17:17:03] <Lcvette> Thank you Hands
[17:17:09] <Lcvette> TurBoss: o/
[17:17:12] <Lcvette> :D
[17:17:14] <Lcvette> \o/
[17:17:19] <Lcvette> fresh help!!
[17:17:21] <TurBoss> booting dev
[17:17:28] <hands[m]> well I am building a machine and I want vertical for it so... yah Open Source 🙂
[17:17:59] <TurBoss> Lcvette: we have to take a look at thw linear atc changes I did yesterday
[17:18:08] <Lcvette> ok
[17:18:10] <Lcvette> im at dev
[17:18:30] <Joco[m]> <hands[m] "well I am building a machine and"> Yup that how it works. Find and itch and scratch but others benefit from the scratching. It’s really a bit group scratch season.
[17:18:39] <Joco[m]> * > <@_discord_418751959818960896:jauriarts.org> well I am building a machine and I want vertical for it so... yah Open Source 🙂
[17:18:40] <Joco[m]> Yup that how it works. Find an itch and scratch but others benefit from the scratching. It’s really a bit group scratch season.
[17:18:53] <Lcvette> Joco: can you run it over 300mm
[17:19:05] <Lcvette> that is the tolerance std
[17:19:14] <Lcvette> supposed to be +/-50 microns lead error
[17:19:54] * TurBoss uploaded an image: Captura de pantalla de 2020-07-11 23-19-31.png (21KB) < https://matrix.org >
[17:21:30] <Joco[m]> <Lcvette "Joco: can you run it over 300mm"> I'm just running a complete screw mapping with these "default" settings. That will give me a picture of what is happening using nominal values with 256 measurements across the full travel
[17:22:08] <Joco[m]> love this program.
[17:22:17] <Lcvette> TurBoss: i cannot launch latc
[17:22:21] <Lcvette> on the new master
[17:22:32] <Joco[m]> got it from this thread: https://forum.linuxcnc.org
[17:22:54] <TurBoss> gotany error message?
[17:23:20] * Lcvette sent a long message: < https://matrix.org >
[17:23:52] <TurBoss> this should fix the "no module error"
[17:24:10] <Lcvette> im in the new branch master
[17:24:36] <TurBoss> ```python
[17:24:36] <TurBoss> python -m pip install --upgrade .e .
[17:24:43] <TurBoss> in the probe_basic directory
[17:24:54] <TurBoss> needed because some changes
[17:24:58] * Lcvette uploaded an image: Screenshot_2020-07-11_17-24-47.png (37KB) < https://matrix.org >
[17:25:02] <TurBoss> * ```python
[17:25:02] <TurBoss> python -m pip install --upgrade -e .
[17:25:02] <TurBoss> ```
[17:25:57] <Lcvette> ok ran that and now when i try an open i get a blank temrinal scren
[17:26:16] * Lcvette uploaded an image: Screenshot_2020-07-11_17-26-08.png (11KB) < https://matrix.org >
[17:26:19] <TurBoss> yes there
[17:26:22] <TurBoss> is fine
[17:26:26] <Lcvette> no no
[17:26:41] <Lcvette> this is what i get when i try and run probe basic after runnong the pip
[17:28:10] * Lcvette posted a file: pb_launch_issue.mkv (368KB) < https://matrix.org >
[17:28:15] <Lcvette> turboss ^^^
[17:30:27] <hazzy-m> it's not running any command it looks like
[17:30:29] <hazzy-m> strange
[17:31:02] <TurBoss> that messed
[17:31:09] <Lcvette> /o\
[17:31:11] <Lcvette> lol
[17:31:49] <TurBoss> can you open a new terminal an run
[17:31:49] <TurBoss> ```
[17:31:49] <TurBoss> linuxcnc /home/path/to/latc/ini.ini=
[17:31:56] * TurBoss sent a long message: < https://matrix.org >
[17:32:45] <TurBoss> just saw the vid
[17:34:46] * Lcvette sent a long message: < https://matrix.org >
[17:35:24] <TurBoss> replace /home/cris/dev/probe_basic/config/pro...
[17:36:33] <Lcvette> ?
[17:37:11] <TurBoss> you need to run the command linuxcnc then the path to the latc ini
[17:37:40] <TurBoss> >/home/path/to/latc/ini.ini
[17:37:40] <TurBoss> this was just an example
[17:37:46] <TurBoss> * >
[17:37:46] <TurBoss> /home/path/to/latc/ini.ini
[17:37:46] <TurBoss> this was just an example
[17:38:51] <Lcvette> no idea
[17:38:58] <Lcvette> why doesn't it work with my launcher?
[17:39:13] <Lcvette> ```
[17:39:14] <Lcvette> xfce4-terminal -e "linuxcnc /home/chris/dev/probe_basic/config/probe_basic_latc/probe_basic.ini" --hold
[17:41:15] <TurBoss> ```
[17:41:15] <TurBoss> linuxcnc /home/chris/dev/probe_basic/config/probe_basic_latc/probe_basic.ini
[17:41:28] <TurBoss> * ```
[17:41:28] <TurBoss> linuxcnc /home/chris/dev/probe_basic/config/probe_basic_latc/probe_basic_latc.ini
[17:41:28] <TurBoss> ```
[17:41:33] <TurBoss> probe_basic_latc.ini
[17:43:15] <TurBoss> Lcvette: ^^
[17:43:48] <TurBoss> any luck?
[17:46:03] * Lcvette sent a long message: < https://matrix.org >
[17:46:06] <Lcvette> same error
[17:46:13] <Lcvette> but it trys starting now
[17:46:32] <TurBoss> ahhhh
[17:46:47] <TurBoss> you need to run """qcompile ."""
[17:47:14] <TurBoss> under probe_basic directory run
[17:47:14] <TurBoss> ```
[17:47:14] <TurBoss> qcompile .
[17:49:48] <Lcvette> you broke all the formatting, but it opened
[17:50:03] <Lcvette> \o/ and /o\
[17:50:38] <TurBoss> well
[17:50:41] <Lcvette> TurBoss: ^^^
[17:50:42] <TurBoss> its fragile
[17:51:33] <Lcvette> broke many things
[17:51:37] <Lcvette> /o\
[17:51:44] <TurBoss> its much broke?
[17:51:46] <Lcvette> think gonna have to go back and revrt
[17:51:50] <Lcvette> very much
[17:51:59] <Lcvette> on all pages lots of things
[17:52:18] <Lcvette> i did not update my master branch yet
[17:52:23] <TurBoss> yes
[17:52:25] <Lcvette> just checkout out yours
[17:52:28] <TurBoss> sure
[17:59:05] * TurBoss posted a file: debug.ngc (1KB) < https://matrix.org >
[17:59:23] <TurBoss> Lcvette: run this file on LATC
[18:05:16] <Lcvette> i tried running now luck does nothing
[18:05:52] <TurBoss> in the latc tab?
[18:06:45] <Lcvette> ?
[18:07:22] * Lcvette uploaded an image: Screenshot_2020-07-11_18-07-08.png (121KB) < https://matrix.org >
[18:07:55] <TurBoss> swich to lineat atc tab
[18:08:00] <TurBoss> the click cycle run
[18:08:08] <TurBoss> * then click cycle run
[18:09:57] * TurBoss posted a file: debug.ngc (1KB) < https://matrix.org >
[18:11:26] <Lcvette> does nothing but flash the buttons for a second
[18:11:29] <Lcvette> what am i looking for?
[18:11:47] * TurBoss uploaded a video: linear_atc_demo.webm (473KB) < https://matrix.org >
[18:12:11] <TurBoss> didi a vid
[18:12:31] <Lcvette> \o/
[18:12:36] <Lcvette> i see yes im showing tools
[18:12:49] <TurBoss> hurray!
[18:12:50] <Lcvette> but i was not on linearatc tab when i first ran it so was not seeing it change
[18:12:52] <Lcvette> hurray!!
[18:12:54] <Lcvette> \o/
[18:13:00] <TurBoss> ya
[18:13:03] <TurBoss> great!
[18:13:09] <TurBoss> so whats the breakage?
[18:13:22] <TurBoss> layout?
[18:14:21] <Lcvette> all the formatting and font and colors
[18:14:27] <Lcvette> alot of broken stuff
[18:14:29] <Lcvette> not sure why
[18:14:36] <Lcvette> not idea where to look to fix it
[18:15:02] * TurBoss uploaded an image: Captura de pantalla de 2020-07-12 00-14-42.png (259KB) < https://matrix.org >
[18:15:08] <TurBoss> not good?
[18:15:42] <TurBoss> me is confused
[18:15:58] <TurBoss> needs to smoke
[18:16:11] <Lcvette> see the big 0 in the top left box
[18:16:23] <Lcvette> * see the big 0 in the top right box
[18:16:29] <TurBoss> ah
[18:16:32] <Lcvette> different from the box underneath it
[18:16:44] <Lcvette> click the atc setup tab top left corner
[18:16:51] <Lcvette> all box test is formatted wrong
[18:16:58] <Lcvette> the probe screen buttons are all wrongs
[18:17:38] <Lcvette> backgrouns coloring etc
[18:18:17] <TurBoss> qss file is old
[18:19:09] <Lcvette> why is it old?
[18:19:20] <Lcvette> what other files are wrong?
[18:19:34] * TurBoss uploaded an image: Captura de pantalla de 2020-07-12 00-19-15.png (310KB) < https://matrix.org >
[18:19:40] <TurBoss> fixed
[18:19:48] <Lcvette> \o/
[18:20:00] <TurBoss> xD
[18:20:04] <Lcvette> are the subroutine folder the enwest one?
[18:21:08] <TurBoss> it was a mess because there were things done to regular probe_basic and I had to begin picking from from regular to latc
[18:22:14] <TurBoss> Lcvette: I'll push the style fix
[18:22:35] <Lcvette> TurBoss: that scares me
[18:22:50] <Lcvette> because there is alot different im sure so now im not sure what else is mixed up
[18:22:53] <Lcvette> /o\
[18:23:29] <TurBoss> the old branch has all the work done in regular pb
[18:24:38] <Lcvette> give it a try
[18:24:45] <Lcvette> yes
[18:24:50] <Lcvette> my master branch is current
[18:27:05] <TurBoss> just pushed
[18:27:12] <Lcvette> k
[18:27:14] <Lcvette> \o/
[18:28:34] <TurBoss> ok something less
[18:29:09] <TurBoss> thats because the new field entries are setings and the old qss file didn't know how to paint them
[18:40:04] <Joco[m]> Lcvette: got some graphs of the error over the screw with nominal settings.
[18:40:17] * Joco[m] uploaded an image: x_base_neg.png (17KB) < https://matrix.org >
[18:40:27] * Joco[m] uploaded an image: x_base_pos.png (18KB) < https://matrix.org >
[18:40:57] <Joco[m]> thats with 400/mm step setup
[18:42:14] -!- c-log has quit [Ping timeout: 256 seconds]
[18:46:22] -!- c-log has joined #hazzy
[18:53:21] <Lcvette> TurBoss: sorry got called to the dinner table
[18:53:30] <TurBoss> no problem
[18:54:05] <Lcvette> joco, so i guess now you can dial the steps per to flattent hat line out
[18:54:16] <Lcvette> good news is it looks fairly linear
[18:54:31] <Lcvette> then you can dial in the lead error
[18:54:34] <Joco[m]> yeah - might need to run things again
[18:54:41] <Joco[m]> here's some more pics
[18:55:25] <Lcvette> im trying also now to help someone communicate with their new 7i76e card and not going well
[18:55:47] <Joco[m]> These are the pics with a "better" steps/mm setting
[18:56:03] * Joco[m] uploaded an image: x_steps_neg.png (19KB) < https://matrix.org >
[18:56:05] <Lcvette> joco do you have static ip setup on mesa?
[18:56:09] * Joco[m] uploaded an image: x_steps_pos.png (19KB) < https://matrix.org >
[18:56:57] <Joco[m]> <Lcvette "joco do you have static ip setup"> I'm currently running a plug-n-go kit. Mate has his set for the default that comes out of the box
[18:57:00] <Lcvette> sp looks like you could tweak it a hair more
[18:57:17] <Lcvette> turboss yours is ethernet card correct?
[18:57:30] <Lcvette> or no you have 6i25/7i76
[18:57:37] <TurBoss> pcie
[18:57:41] <TurBoss> yes
[18:57:55] <Lcvette> do you guys know how to set the static IP?
[18:58:21] <Joco[m]> on the card or on oc?
[18:58:25] <Lcvette> https://forum.linuxcnc.org
[18:58:33] <Lcvette> i tried following this but it errors
[18:59:01] <Lcvette> we set the jumper on the card for 10.10.10.0
[18:59:11] <Joco[m]> ok
[18:59:29] <Joco[m]> if you type ifconfig in terminal what comes back?
[19:02:19] <Lcvette> bash
[19:02:22] <Lcvette> ipconfig?
[19:02:40] <Joco[m]> sorry - yeah
[19:02:42] <Joco[m]> ipconfig
[19:02:51] <Lcvette> bash on that too
[19:03:02] <Lcvette> command not found
[19:03:03] <Joco[m]> no - its ofconfig
[19:03:11] <Joco[m]> * no - its ifconfig
[19:03:35] <Joco[m]> no ifconfig???
[19:03:38] <Lcvette> command not found
[19:03:52] <TurBoss> ```
[19:03:53] <TurBoss> ip a
[19:03:53] * Lcvette sent a long message: < https://matrix.org >
[19:03:54] <Joco[m]> fuck - that install has moved to the bloody ip commane
[19:04:32] <Joco[m]> ip link
[19:04:41] <Lcvette> eth0
[19:05:01] <Joco[m]> did you use eth0 in the networks setup?
[19:05:05] <Lcvette> yes
[19:05:09] <Joco[m]> cool
[19:05:48] <Joco[m]> so if you use ip address
[19:06:02] <Joco[m]> you get the 10.10... you are expecting on eth0?
[19:06:03] * Lcvette sent a long message: < https://matrix.org >
[19:06:26] * Lcvette uploaded an image: image.png (53KB) < https://matrix.org >
[19:07:06] <Lcvette> turboss joco ^^^
[19:07:24] <Joco[m]> what is you loadrt line?
[19:07:27] <Lcvette> that is the error message i get
[19:08:14] <Lcvette> ```
[19:08:14] <Lcvette> loadrt hostmot2
[19:08:14] <Lcvette> loadrt hm2_eth board_ip="10.10.10.10" config=" num_encoders=1 num_pwmgens=0 num_stepgens=5 sserial_port_0=00xxxx"
[19:08:51] <Joco[m]> why is the address in the networks not 10.10.10.10?
[19:09:09] <Lcvette> just following what was in that link
[19:09:13] <Lcvette> i dunno
[19:09:36] <Joco[m]> oh - i know
[19:09:43] <Lcvette> you know the issue?
[19:09:45] <Lcvette> :o
[19:09:47] <Lcvette> \o/
[19:10:09] <Joco[m]> no - lol - I know why addresses not the same
[19:10:45] <Lcvette> oh
[19:11:24] <TurBoss> Lcvette: is you mesa car directly connected?
[19:11:29] <Lcvette> yes
[19:12:20] <TurBoss> what does
[19:12:20] <TurBoss> ```bash
[19:12:20] <TurBoss> ip a
[19:13:05] <TurBoss> you have two entries in for eth0 in you network settings
[19:13:10] <Joco[m]> do you have a wifi dongle in the machine?
[19:13:17] * TurBoss sent a long message: < https://matrix.org >
[19:13:43] <Joco[m]> snap - you beat me
[19:14:11] <Lcvette> ok testing
[19:14:13] <Lcvette> sek
[19:17:08] <Lcvette> same error
[19:17:20] <Lcvette> how can i test comunication with 7i76e?
[19:17:34] <TurBoss> Lcvette:
[19:17:34] <TurBoss> ```
[19:17:34] <TurBoss> ping 10.10.10.10
[19:18:07] <Lcvette> TurBoss: what should the reponse be
[19:18:21] <Lcvette> copy results here
[19:18:27] <TurBoss> past
[19:18:40] * Lcvette uploaded an image: image.png (35KB) < https://matrix.org >
[19:18:46] <TurBoss> no comm
[19:19:00] <Lcvette> so then what?
[19:19:05] <Lcvette> /o\
[19:19:07] <TurBoss> ```
[19:19:07] <TurBoss> ip a
[19:19:10] <TurBoss> then show here
[19:19:22] * Lcvette sent a long message: < https://matrix.org >
[19:19:50] <TurBoss> for some reason eth0 is not getting an ip
[19:20:11] <TurBoss> where are you editing the configs?
[19:20:14] <TurBoss> wich file path
[19:20:49] <Lcvette> i forgot to run sudo /etc/init.d/networking restart
[19:20:56] <Lcvette> after i changed it
[19:20:59] <Lcvette> retesting
[19:21:04] <TurBoss> ping works?
[19:21:06] <TurBoss> ok
[19:22:28] <Lcvette> worked after network restart\o/
[19:22:30] <Lcvette> hurray!!
[19:22:32] <Lcvette> :D
[19:22:35] <TurBoss> great
[19:22:36] <Lcvette> party!!
[19:22:36] <Joco[m]> lol
[19:22:54] <TurBoss> but didi you remove the ofending eth0 entry?=
[19:23:05] <Joco[m]> you should do
[19:23:25] <Lcvette> ?
[19:23:37] * TurBoss sent a long message: < https://matrix.org >
[19:23:44] <Lcvette> i did not restart the netowrk for changes to take effect
[19:23:47] <Lcvette> yes
[19:23:50] <Lcvette> removed that
[19:23:55] <TurBoss> great
[19:24:00] <Lcvette> did not retsrat network after making that change
[19:24:10] <Lcvette> after restart network it worked
[19:24:54] <Joco[m]> cool - you are away then
[19:25:22] <Joco[m]> I have to do all this soon when I convert my rig to ethernet
[19:26:03] <Joco[m]> the card is sitting there with an accusing look on it
[19:26:24] <Lcvette> geterdone!
[19:28:04] <Joco[m]> yes Keith
[19:35:05] <Joco[m]> Lcvette: refined the steps/mm. Think its quite a bit tighter now. Here are the error graphs.
[19:35:15] * Joco[m] uploaded an image: x_steps_neg.png (21KB) < https://matrix.org >
[19:35:23] * Joco[m] uploaded an image: x_steps_pos.png (21KB) < https://matrix.org >
[19:36:16] <Joco[m]> now I need to process a new compensation file.
[19:36:16] <Lcvette> is blc off still?
[19:36:33] <Joco[m]> yup
[19:37:35] <Lcvette> so the directional error is your backlash amount maybe?
[19:37:55] <Joco[m]> to a point. Along with some likely variation in the screw
[19:37:56] <Lcvette> 0.07mm?
[19:38:23] <Joco[m]> but yeah circa 0.7mm
[19:38:29] <Lcvette> well start of travel appear to change from one graph to the next
[19:38:29] <Joco[m]> 0.07mm
[19:39:10] <Lcvette> try throwing that in and run it again and see if it matches
[19:39:20] <Joco[m]> the process is start at x0, rapid to x480, start samples back to 0, then revrse sample back to 480
[19:39:33] <Lcvette> ie brings the start to the same place the previous move ends on the scale
[19:39:41] <Lcvette> that shold be a great way to nail down blc
[19:41:05] <Joco[m]> part of the challenge is that there is measurable variation in travel per turn as well. The joys of rolled v's ground.
[19:41:42] <Joco[m]> but the backlash part is really moot. The compensation file overrides the backlash setting when you use a compensation file.
[19:42:10] <Joco[m]> the fact there is backlash is essentially baked into the compensation file.
[19:45:34] <Joco[m]> will crack in to gettting this new compensation file built then will try another test using that.
[21:25:37] -!- travis-ci has joined #hazzy
[21:25:37] <travis-ci> kcjengr/qtpyvcp#1657 (QPlainTextEdit - 9862885 : Kurt Jacobson): The build was fixed.
[21:25:37] <travis-ci> Diff view : https://github.com
[21:25:37] <travis-ci> Build details : https://travis-ci.org
[21:25:37] -!- travis-ci has parted #hazzy
[21:25:48] <TurBoss> \o/
[21:26:02] <TurBoss> some spam
[21:30:17] -!- TurBoss_backup has joined #hazzy
[21:31:02] -!- TurBoss_backup has parted #hazzy
[22:15:20] * hands[m] uploaded an image: unknown.png (184KB) < https://matrix.org >
[22:15:21] <hands[m]> a lot still broken.. but progress...
[22:15:43] <hazzy-m> hurray!
[22:15:46] <Joco[m]> progress is good.
[22:15:50] <Joco[m]> We like progress :-)
[23:31:47] <hazzy-m> Joco: This might replace our work on the QScintilla based gcode editor:
[23:31:47] <hazzy-m> https://github.com
[23:32:04] <hazzy-m> its pure QT using and based on a QPlainText edit
[23:32:17] <hazzy-m> to much more light weight and faster
[23:32:27] <hazzy-m> * so more light weight and faster
[23:33:43] * hazzy-m uploaded an image: image.png (32KB) < https://matrix.org >
[23:34:00] <Joco[m]> Lite weight sounds good.
[23:34:14] <hazzy-m> still needs tweaking. but it mostly works very well
[23:34:24] <hazzy-m> JT wrote it a while back
[23:34:27] <Joco[m]> I’m all for simple
[23:35:21] <hazzy-m> even has context menus for Run from line
[23:47:41] <Joco[m]> Nice.