#hazzy Logs
May 23 2020
#hazzy Calendar
12:13 AM Joco[m]: solved the 'initalize' question. Need to subclass off VCPPrimitiveWidget
12:34 AM Joco[m]: oooh sooo close. Have control over font used i the body of the code editor via Designer. Now just need to make the numbers under the same control
12:35 AM Joco[m]: I tell yah. Being able to step through code in this thing is a god send.
01:13 AM Joco[m]: YES
01:14 AM * Joco[m] uploaded an image: image.png (117KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/vsJLhmrFNdKymhEMQHDNCSTY >
01:14 AM Joco[m]: applied Don's lexer updates and got my font setting from Designer working.
01:52 AM Joco[m]: some of the colors are hard coded at the moment but once we have a working INI plugin I can move those settings out to the ini file.
02:07 AM * Joco[m] uploaded an image: image.png (101KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/WZqMlPebvyjdMvyNaSzmPhMV >
02:08 AM Joco[m]: And using IBM 3270 old scool font
02:46 AM Not-944e: [02qtpyvcp] 07joco-nz opened pull request 03#35: Editor enhance2 - 13https://git.io/JfatA
03:27 AM TurBoss: cool
05:07 AM TurBoss: I'm thinking that a ini plugin is not doable
05:07 AM TurBoss: while on designer ini is not abailable
05:08 AM TurBoss: took me a while to figure lol
05:09 AM Joco[m]: TurBoss: you have ini working? Or have a path forward?
05:10 AM TurBoss: path forward?
05:10 AM TurBoss: no nothing works
05:10 AM TurBoss: :D
05:11 AM TurBoss: ini is only accesible on runtime
05:12 AM TurBoss: trying other direction
05:12 AM * TurBoss sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/KlIkRlojHhSthIYYfdWjTqZc >
05:12 AM TurBoss: this is my vcp main.py
05:19 AM Joco[m]: What we’re trying to do in Designer?
05:23 AM TurBoss: have access to ini options to show dro per example
05:24 AM TurBoss: you said another option right?
05:29 AM TurBoss: i'm taking a nap
05:29 AM TurBoss: latter
06:26 AM Joco[m]: sleeps for me
08:45 AM Lcvette1: morning
08:46 AM JT-Cave: morning
08:48 AM Lcvette1: borla time?
08:48 AM Lcvette1: :D
08:49 AM JT-Cave: tree trimming time until the rain starts
08:49 AM Lcvette1: rain dance!
08:49 AM Lcvette1: lol
08:49 AM JT-Cave: going out this afternoon to eat and celebrate our 33rd
08:49 AM Lcvette1: vrooom vrooom
08:49 AM Lcvette1: nice!
08:49 AM Lcvette1: congrats!
08:50 AM JT-Cave: thanks
09:46 AM hazzy-m: TurBoss: I was wondering about using default values in designer
10:04 AM Lcvette1: hazzy: what default values?
10:04 AM Lcvette1: like for DRO Display?
10:06 AM Lcvette1: i guess worst case scenario you could change the order of the dro stacked widget to accomodate by putting your preference as the first page, then it would by default be the displayed dro count
10:06 AM Lcvette1: or maybe make seperate ui files
10:06 AM Lcvette1: just seems it should be possible somehow to have a setting
10:07 AM Lcvette1: what about a rule?
10:08 AM Lcvette1: is there something in the rules that could look for axis count and change the page number bvased on the result?
10:08 AM Lcvette1: that way it would be after the start right?
10:09 AM Lcvette1: and eliminate the issue?
10:22 AM JT-Shop: wow swinging a 11 1/2' pole saw is more fun than I anticipated
10:22 AM Lcvette1: thats some work
10:22 AM Lcvette1: thing gets heavy after a while
10:23 AM JT-Shop: I'm glad it telescopes down to 7 1/2' for close in work
11:28 AM roguish[m]: JT-Shop: chain saw on a stick?
11:37 AM Lcvette1: TurBoss: are you here?
11:49 AM JT-Cave: roguish[m], pretty much a chain saw with a stick and a bar at the end of the stick
11:49 AM JT-Cave: https://www.stihlusa.com/products/pole-pruners/professional-pole-pruners/ht103/
02:39 PM Joco[m]: Re the dro display discussion , is that about how to have it show for 3, 4 or more axis depending on machine config?
02:48 PM Lcvette1: yes
02:48 PM Lcvette1: @joco ^^^
02:48 PM Lcvette1: * @joco: ^^^
02:48 PM Lcvette1: * joc yes
02:48 PM Lcvette1: Joco: yes
02:52 PM Joco[m]: Ok. Is this with or without an ini plug in?
02:53 PM Lcvette1: i think turboss deemed the ini plugin a failure
03:12 PM Joco[m]: I think it depends what is being looked for in its usage. Also I think if it is to be used for rules there needs to be some trigger mechanic that kicks the rules once after gui loads. So they fire. I faked it in my tests on the axis data in the status plug in. By adding a second channel to the rule and making that the trigger channel. Even though it was not used in the rule test.
03:13 PM Joco[m]: That second channel was more volatile ie the data changed, so the rule fired.
03:14 PM Joco[m]: A hack, but it worked.
03:14 PM Lcvette1: i currently have it setup on checkboxes
03:15 PM Lcvette1: and those checkboxes are persistent
03:15 PM Lcvette1: but they don't fire when starting
03:15 PM Lcvette1: would it be easier to have a rule setup on each of the check boxes?
03:15 PM Lcvette1: maybe add a trigger to say the power button?
03:16 PM Lcvette1: so it may not start and show the correct display, but once the power button is hit it would trigger the checkbox rules
03:16 PM Lcvette1: i don't know im in left field
03:17 PM Lcvette1: lol
03:17 PM Joco[m]: That would work. Run off machine power status as trigger
03:18 PM Joco[m]: The acrewy thing is i hav it working in my gui with a hide/show rule running off axis mask.
03:18 PM Lcvette1: You have it working?
03:19 PM Joco[m]: I have an A axis dro widget that I set as visible or not based on the status axis mask
03:19 PM Joco[m]: It works.
03:20 PM Lcvette1: Oh can we not so the same for a stacked widget?
03:20 PM Joco[m]: Run machine 3 axis, no display. 4 axis, displays.
03:20 PM Joco[m]: That seems to be what is different
03:21 PM Joco[m]: It has to be a quirk in how the rules are firing or what the order of them is.
03:21 PM Lcvette1: You mean it only pops up when A axis is moving?
03:22 PM Joco[m]: No. On start.
03:22 PM Joco[m]: Like it should
03:22 PM Joco[m]: As in on gui start
03:22 PM Lcvette1: Oh what if we set the check boxes the same way
03:23 PM Joco[m]: You could try.
03:23 PM Lcvette1: 4 axis if A
03:23 PM Lcvette1: 5 axis is B
03:23 PM Joco[m]: Yup
03:24 PM Lcvette1: i wonder if it would fire the checkboxes
03:24 PM Lcvette1: whats your rule look like?
03:24 PM Joco[m]: It could also be pure luck that mine is working. Just a fluke as to the order things were placed in the gui.
03:25 PM Lcvette1: only takes a moment to test
03:25 PM Lcvette1: can you show me the rule screen shot?
03:26 PM Joco[m]: Umm. Sunday mornig, 8:16am and im still in bed. 😂
03:26 PM Lcvette1: ah
03:26 PM Lcvette1: lol
03:26 PM Lcvette1: ok
03:26 PM Lcvette1: when you get too it
03:26 PM Joco[m]: Need to make wife cup o tea. So in about 5 or 10 mins.
03:26 PM * Lcvette1 uploaded an image: Screenshot_2020-05-23_16-17-52.png (37KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/goCzTksHtXGQhStVUkNMAQqq >
03:27 PM Lcvette1: the check boxes have rule
03:27 PM Lcvette1: \o/
03:27 PM Lcvette1: so does the stacked widget
03:28 PM Lcvette1: could try the stacked widget first
03:28 PM Lcvette1: then the check boxes
03:28 PM Joco[m]: Yup. Just remember that rules are still have limits. Until we have a broader data channel base for them to trigger off.
03:40 PM * Joco[m] uploaded an image: image.png (28KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/jrVMBEdTDMPSJJwEeDeDnQwH >
03:41 PM Joco[m]: and here is the list of status data items: http://www.qtpyvcp.com/components/status_items.html
03:43 PM * Joco[m] sent a long message: < https://matrix.org/_matrix/media/r0/download/matrix.org/UEBYKhCUAHEABGcTAVngTbaJ >
04:03 PM Lcvette1: cool will try it out
04:05 PM Lcvette1: would B axis be ch[0]==16
04:05 PM Lcvette1: ?
04:07 PM Lcvette1: Joco: im a little confused, your A=8 but you are making the rule for ch[0]==15
04:07 PM Lcvette1: oh its the sum of each axis value
04:08 PM Lcvette1: so 5 axis would be ch[0]==31
04:10 PM Lcvette1: well, it fires the check box but the check box must not fire in time to change the stacked widget
04:10 PM Lcvette1: it is now changing the checkbox though so something is happening
04:10 PM Joco[m]: you add up the values for each axis you are expecting.
04:11 PM Lcvette1: i will see if i can fire directly into the stacked widget
04:11 PM Joco[m]: x/y/z = 7
04:11 PM Lcvette1: 7,15,31
04:11 PM Joco[m]: x/y/z/a=15
04:11 PM Joco[m]: x/y/z/b == 24
04:12 PM Lcvette1: xyzab 31
04:12 PM Lcvette1: 5 axis
04:13 PM Joco[m]: yup
04:13 PM Lcvette1: ok i need to make a rule that is if then and sets the stacked widget page
04:13 PM Lcvette1: no clue though
04:15 PM Joco[m]: you have a different page for each widget?
04:15 PM Joco[m]: sorry each axis number variation?
04:17 PM Lcvette1: yes
04:17 PM Lcvette1: xyz, xyza, xyzab
04:17 PM Lcvette1: index 0, 1, 2
04:17 PM Lcvette1: respectively
04:17 PM hazzy-m: joco: thanks for the PR! Lots of good stuff in there
04:18 PM Lcvette1: o/
04:18 PM Joco[m]: ok - and the gui assumes xyz, xyza, xyzab
04:18 PM Joco[m]: hazzy: I have my moments
04:18 PM * Lcvette1 uploaded an image: Screenshot_2020-05-23_17-09-42.png (14KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/dUosrySQejRKMNFwkEoechjH >
04:19 PM Lcvette1: index 0 = xyz
04:19 PM Lcvette1: index 1 =xyza
04:19 PM Lcvette1: index 2 = xyzab
04:19 PM Lcvette1: not sure if you need to call the page name or the index number
04:20 PM Joco[m]: Lcvette: ok - think can use status:axes
04:20 PM Joco[m]: its page index
04:20 PM Lcvette1: was thinking it would look something like if ch[0]==7 then 0 elif 15 then 1 elif 31 then 2
04:21 PM Lcvette1: but i have no grasp of formatting
04:21 PM Joco[m]: so using the status:axes which returns the count of indexs i.e. 3, 4, 5 you can just use simple maths to get the page index
04:21 PM Joco[m]: ch[0]-3
04:22 PM Joco[m]: assuming channel 0 is status:axes
04:23 PM Lcvette1: would the else if method not work?
04:24 PM Joco[m]: rules are goin through a python EVAL statement and from my readying it will not cope with elif
04:24 PM Lcvette1: think we have elif rules
04:24 PM Joco[m]: I would like to see how they are structured. If you can find an example
04:25 PM Joco[m]: we have else rules
04:25 PM * Lcvette1 uploaded an image: Screenshot_2020-05-23_17-16-05.png (32KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/JNqBZkTFnRobZXRSTIkNEFLH >
04:25 PM Joco[m]: yes an else rule. That is not an elsif
04:26 PM * Lcvette1 uploaded an image: Screenshot_2020-05-23_17-17-11.png (33KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/eNdzvbRRMmKasfoIUgNicnQN >
04:26 PM Lcvette1: thats an else if no?
04:26 PM Lcvette1: and it works
04:26 PM Lcvette1: changes the dro colors
04:27 PM Lcvette1: red to yello to black
04:27 PM Lcvette1: * red to yellow to black
04:27 PM Lcvette1: for three different states
04:27 PM Joco[m]: that is separate single if's on different channels
04:27 PM Lcvette1: oh
04:27 PM Lcvette1: could we use 2 channels
04:28 PM Joco[m]: hazzy: can we do prooper python if elif else structures in rules>
04:28 PM Joco[m]: ?
04:28 PM Lcvette1: status:axis_mask and status:axes
04:28 PM Lcvette1: or have 0 be default and only use an if else for 4 and 5 axis?
04:29 PM Joco[m]: Lcvette: for the problem you are trying to solve my ch[0]-3 rule using status:axes will give you the correct page index
04:29 PM Lcvette1: oh
04:29 PM Lcvette1: ok great
04:29 PM Joco[m]: cose when axes=3 the result is 0
04:29 PM Joco[m]: and that is the page index you want
04:30 PM Joco[m]: etc etc
04:30 PM Joco[m]: we MAY need to add a second channel to be the trigger to force this rule to fire to drive the gui
04:30 PM * Lcvette1 uploaded an image: Screenshot_2020-05-23_17-21-50.png (28KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/bCkvMjXPjgPBEcLSPjYLtBbB >
04:31 PM Joco[m]: for example status:on with the trigger value set
04:31 PM Joco[m]: try it
04:31 PM Joco[m]: hang on
04:31 PM Lcvette1: whoops chnaged the property to current_index
04:31 PM Lcvette1: ok testing
04:31 PM Joco[m]: you need to change from Enable tp Page
04:31 PM Joco[m]: or Index
04:31 PM Joco[m]: whatever it is
04:32 PM Lcvette1: not working
04:32 PM Lcvette1: /o\
04:32 PM Lcvette1: running a 5 axis sim and it starts in 3 axis
04:34 PM Joco[m]: work around at the moment would be to add another channel, status:on and mark that as the trigger
04:34 PM * Lcvette1 uploaded an image: Screenshot_2020-05-23_17-25-02.png (28KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/TOfUZUDMTPfOXfMTHSLzXLsL >
04:34 PM Joco[m]: it should fix once you power on
04:34 PM Lcvette1: nope
04:34 PM Lcvette1: powered on, homed, stayed 3 axis
04:35 PM Joco[m]: picture of rule please?
04:35 PM Lcvette1: above
04:35 PM Joco[m]: add another channel to rule.
04:35 PM Joco[m]: status:on
04:36 PM Joco[m]: mark that channel as a trigger
04:36 PM Lcvette1: i don't know how
04:36 PM Lcvette1: lol
04:36 PM Lcvette1: /o\
04:37 PM Joco[m]: open the rule, click 'add channel'
04:37 PM Lcvette1: k done\
04:37 PM Joco[m]: type in status:on to that new channel
04:38 PM Joco[m]: make sure the checkbox trigger has a tick in it
04:38 PM Lcvette1: k
04:38 PM Lcvette1: says bool
04:38 PM Joco[m]: that's fine.
04:38 PM Lcvette1: k
04:39 PM Joco[m]: we are not adding anything to the rule expression
04:39 PM Lcvette1: ok
04:39 PM Joco[m]: just using this channel as a way to fire this rule
04:39 PM Lcvette1: test
04:39 PM Lcvette1: still 3 axcis
04:39 PM Joco[m]: F
04:40 PM * Lcvette1 uploaded an image: Screenshot_2020-05-23_17-31-09.png (30KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/KTlHzpubZnKIFPgMdhhZIMth >
04:40 PM Joco[m]: you have the status:on marked as a trigger?
04:40 PM Joco[m]: looks correct
04:40 PM Joco[m]: k - time for me to test on my machine here
04:40 PM Lcvette1: do we need to add something like curent index = ch[0]-3?
04:40 PM Joco[m]: nope
04:40 PM Lcvette1: ok
04:41 PM Joco[m]: I have stacked widgets in my gui. setting test up in designer
04:41 PM Lcvette1: geat!
04:44 PM Joco[m]: so just did a hard test with a fixed value index of 0 and it changes on estop and power
04:45 PM Joco[m]: will now try using the calc stuff
04:47 PM Joco[m]: ok - remove the trigger tick off status:axes channel
04:48 PM Joco[m]: i.e. only have one trigger, that being on status:on
04:48 PM Lcvette1: \o/
04:48 PM Lcvette1: success
04:48 PM Lcvette1: opened in 5 axis without no other thing needed
04:48 PM Lcvette1: hurray!
04:49 PM Joco[m]: probably working cose your estop is not fired?
04:50 PM Joco[m]: from behaviour i see on my sim is that when I "enabled" estop it caused the status:on to trigger
04:50 PM Lcvette1: estop must be fired
04:50 PM Lcvette1: then power
04:50 PM Lcvette1: in the sim
04:50 PM Joco[m]: yup
04:50 PM Lcvette1: will it be different if estop is already on?
04:50 PM Joco[m]: its still a work around. But at least gets things into correct state before usage
04:50 PM Lcvette1: think my machine starts with estop in the run position
04:51 PM Joco[m]: possibly. Would need to check
04:51 PM Joco[m]: same
04:51 PM Lcvette1: i think its a good gui setting no?
04:51 PM Joco[m]: mine like taht as well cose estop is a physical button
04:51 PM Lcvette1: well, can check that one off the list!
04:51 PM Joco[m]: an NC button.
04:52 PM Lcvette1: Thanks joco!
04:53 PM Lcvette1: \o/
04:53 PM Joco[m]: no probs. I would still like to get to the bottom of how these triggers are firing. Cose we should not have to do that hack to get around things
04:53 PM Joco[m]: It offends my sense of neatness
04:54 PM Joco[m]: initalise
04:55 PM Joco[m]: oops - lol - wanting to search on this.
04:55 PM Lcvette1: Lol
05:00 PM Joco[m]: I think my next thing to investigate is the status plugin. While we figure out what or if an INI plugin is useful/doable there are values in status plugin that come from the ini file (perhaps via linuxcnc itself) which are static. If you want to use them in a rule it "looks" like they need to be forced to reload/refresh after the gui is loaded but just before we go into the main program loop. I have already proven that
05:00 PM Joco[m]: works on the status:axes channel (i.e. not icky workaround Lcvette).
05:01 PM Lcvette1: nice!
05:02 PM Joco[m]: to fix the status:axes behaviour is a single line of code in the frameworks initialise() method
05:02 PM Joco[m]: sorry -- need to do american spelling. initialize()
05:02 PM Lcvette1: nice!
05:03 PM Lcvette1: more functionaliuty the better!
05:03 PM Joco[m]: yup. It all makes it easier to do things with minimal python in the mix
05:22 PM Joco[m]: right - have my new feature branch. :-) off to invetigate we go
06:02 PM Joco[m]: nice - that works.
06:02 PM Joco[m]: Lcvette if hazzy accepts this tweak to status.py we should be able to solve that icky rules work around.
06:05 PM hazzy-m: Joco: is it in a branch in your repo?
06:05 PM Joco[m]: just creating at the moment.
06:05 PM Lcvette1: \o/
06:07 PM hazzy-m: 👍
06:11 PM Joco[m]: branch is called: static-status-gui-interaction
06:14 PM Joco[m]: I can post a pull request. The change is trivial but is only for axes at the moment. Externalising it to a yaml config would be ideal but also potentially more complicated and definately more risk as the designer needs to know what they are doing
06:14 PM Joco[m]: from an implications at code level angle
06:16 PM Joco[m]: hazzy: I can make a quick pull request if that is useful. It is super small.
06:18 PM Joco[m]: Would allow Lcvette to clean up his rule and give us a hook to add in more of these static channel items that cause a similar issue on certain things. It IS a bit of a work around for stacked widgets but it greases the wheels as it were until someone has time to try and figure out a root cause and a fix, if there is a fix.
06:19 PM Lcvette1: \o/ hurray!
06:19 PM Lcvette1: hazzy pull it pull it!!
06:19 PM Lcvette1: :D
06:21 PM Joco[m]: I'll do the pull request. It can always be killed off if not desired.
06:25 PM Not-944e: [02qtpyvcp] 07joco-nz opened pull request 03#36: Static status gui interaction - 13https://git.io/Jfawl
06:27 PM Joco[m]: Lcvette: hazzy pull request up.
06:41 PM Lcvette1: hazzy ^^^ \o/
06:41 PM hazzy-m: Joco: sweet!
06:41 PM Lcvette1: :D
06:41 PM Lcvette1: Hurray!
06:42 PM Not-944e: [02qtpyvcp] 07KurtJacobson closed pull request 03#36: Static status gui interaction - 13https://git.io/Jfawl
06:42 PM Not-944e: [02qtpyvcp] 07KurtJacobson pushed 031 commit to 03master [+0/-0/±1] 13https://git.io/JfawM
06:42 PM Not-944e: [02qtpyvcp] 07joco-nz 03e348a3b - Static status gui interaction (#36)
06:43 PM Not-944e: [02qtpyvcp] 07KurtJacobson pushed 031 commit to 03gh-pages [+489/-0/±0] 13https://git.io/Jfawy
06:43 PM Not-944e: [02qtpyvcp] 07traviscibot 03cb590c2 - Deploy kcjengr/qtpyvcp to github.com/kcjengr/qtpyvcp.git:gh-pages
06:43 PM hazzy-m: Joco: I don't have a PC I can test on, but reviewed from my phone and looks good!
06:43 PM hazzy-m: Thanks
06:44 PM Joco[m]: I tested before commit. And I am pretty sure Lcvette will be checking it as welll
06:44 PM Joco[m]: And I kept things super tight cose I knew you were remote
06:45 PM hazzy-m: thanks!
06:46 PM Joco[m]: Lcvette: that fix is now in master
06:46 PM Lcvette1: \o/
06:47 PM Lcvette1: just pulled
06:47 PM Lcvette1: what do i need to do now?
06:51 PM hazzy-m: I don't think anything
06:51 PM hazzy-m: It just works (tm)
06:51 PM Joco[m]: you should be able to remove that extra channel from that rule and set the remaining channel as the trigger
06:51 PM Joco[m]: it should not give you the correct display on gui start
06:52 PM Lcvette1: oh
06:53 PM Lcvette1: but i like that it gives the correct gui display at start up
06:53 PM Lcvette1: lcvette wantes to leave it so it starts in the correct gui
06:53 PM Lcvette1: :D
06:54 PM Joco[m]: this will be "proper" no hack
06:54 PM Joco[m]: i.e. not relying on estop states
06:55 PM Joco[m]: it should give the correct gui display no matter is happeing
06:55 PM Joco[m]: and the correct display from the moment the gui appears.
06:55 PM Joco[m]: no matter what
06:55 PM Joco[m]: :-D
06:56 PM Lcvette1: > it should not give you the correct display on gui start
06:56 PM Lcvette1: but you said this
06:56 PM Lcvette1: did you mean it SHOULD?
06:56 PM Lcvette1: lol
06:56 PM Lcvette1: you are ocnfusing lcvette
06:56 PM Joco[m]: oh - lol - yeah
06:56 PM Joco[m]: typo
06:56 PM Lcvette1: * you are confusing lcvette
06:56 PM Lcvette1: ok then i will change
06:57 PM Lcvette1: remove the status on channel?
06:57 PM Joco[m]: yup
06:57 PM Lcvette1: check the other one?
06:57 PM Joco[m]: and set the remaing one to be trigger
06:57 PM Joco[m]: yes
06:58 PM Lcvette1: \o/
06:58 PM Lcvette1: hurray!! it works!
06:58 PM Joco[m]: was there any doubt? :-p
06:58 PM Lcvette1: none!
06:59 PM Lcvette1: :D
06:59 PM Lcvette1: turboss will be so happy!
07:02 PM Joco[m]: I do need to get back to Turboss at some point and understand why he felt the ini plug was a wash or not doable.
07:04 PM Lcvette1: where is the turboss
07:04 PM Lcvette1: he must be playing robots
07:11 PM Joco[m]: right off to the workshop/garage to make chips on my "big" manual mill.
07:12 PM * Joco[m] uploaded an image: ima_2d033ba.jpeg (320KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/tjWLcKNEjQePFVybOgHdbWMz >
07:12 PM Lcvette1: nice!!
07:12 PM Joco[m]: my manual kit. Where I make a mess and have fun relaxing
07:12 PM Lcvette1: i would love a manual mill anbd manual lathe
07:13 PM Lcvette1: well i have a manual 7x10
07:13 PM Lcvette1: lol
07:13 PM Lcvette1: that lathe right here is what i would love
07:13 PM Lcvette1: what did you say it was? 12x36?
07:13 PM Lcvette1: 13x36?
07:15 PM Joco[m]: swing over bed is 330mm. Over cross slide is 200mm and 1000mm between centres
07:15 PM Joco[m]: D1-4 camlock
07:15 PM Lcvette1: ~13x40
07:16 PM Lcvette1: in murican speak
07:16 PM Joco[m]: ~630KG
07:16 PM Lcvette1: lol
07:16 PM Lcvette1: I would love a 13x24 or 13x30
07:21 PM Joco[m]: and I would love a cnc lathe
07:22 PM Joco[m]: but space is not going to allow that for some time
08:55 PM Joco[m]: made some holes. Having some lunch
08:57 PM Lcvette1: Nice
08:57 PM Lcvette1: I'm still camming
08:57 PM Lcvette1: Being extra cautious
08:57 PM Lcvette1: Each piece of stock is $60
08:58 PM Joco[m]: getting a steel fixture plate prepped on the big mill ready to be mounted on the cnc and a LOT of holes to be drilled. Followed by a LOT of thread milling
08:59 PM * Joco[m] uploaded an image: image.png (913KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/jaAzQmHKjXfvXqJBCTKWxCCq >
09:01 PM Lcvette1: nice!
09:02 PM Joco[m]: just getting the mounting holes sorted so can mount it on the cnc table and get it aligned with an indicator. Will have a reamed 10mm hole smack in the center that will be used the datam
09:02 PM Joco[m]: I can indicate off that to get cnc dialed in for the prog to run
09:03 PM Joco[m]: plate is some mild steel I had. is about 400mm long, ~196mm wide and about 15mm thick
09:05 PM Joco[m]: its going to have a number of reamed holes for registering dowel pins and a LARGE number of M6 holes for fixtures. Given the realtively small parts it will be used for M6 will be plenty big enough I think.
09:05 PM Joco[m]: small/light-weight parts
09:06 PM Joco[m]: But I can still change the design if I need to. But evey time I look at M8 screws they just look OTT for what I will be using it for.
09:06 PM Joco[m]: here is the current pin cushion design
09:08 PM * Joco[m] uploaded an image: image.png (416KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/pHmYtSIBdLODdzBPUUvAhBlH >
09:09 PM Joco[m]: And some modelling working out standoffs and pulley designs and how they will fit/mount to the spindle driving collar.
09:09 PM * Joco[m] uploaded an image: image.png (99KB) < https://matrix.org/_matrix/media/r0/download/matrix.org/oqsDRIeAxuvvkmzlfWUqCwMp >
09:34 PM Lcvette1: Looking good
09:34 PM Lcvette1: How's the model compared top the bf20 so far?
09:36 PM Lcvette1: Hazzy, i remember we discussed using the index pulse from the servo encoders for homing for super rechargeable homing, i never set that up but i would like too
09:36 PM Lcvette1: When your back from vacation i would be grateful if you could help me set it up
09:39 PM Joco[m]: model in the head has some differences. I think the core dimensions from the back mount plat are ok. But this head has more casting in front of the cylinder than on the BF20 from what I can see. Once I have done the holes in the fiture plate I'm going to do some more measurements. For the important stuff, spindle components, screw hole locations and the key dimensions from the back plate its looking good.