#linuxcnc Logs

Feb 12 2023

12:00 AM DrewnabobberBCCA: Haven't really noticed anything amiss. I haven't used LinuxCNC on anything other than RPI4.
12:10 AM TurBoss8676[m]: 👍
12:10 AM DrewnabobberBCCA: We will see how far we can take it. Can always run Axis or Gmoccapy.
12:10 AM TurBoss8676[m]: sure
12:10 AM DrewnabobberBCCA: Just saw the chatter about Remora so thought I'd post about what's going on, I don't think it is dead or anything.
12:10 AM DrewnabobberBCCA: We have made some updates to support a static hardware config (on flexi all IO is pretty fixed function in hardware - an input is an input, a stepper is a stepper etc) and we had to add some function to allow for setup/hold delay between step/dir signals.
02:08 AM Deejay: moin
03:27 AM solarwind: Absolutely LOVE my new torque screwdriver 0.05 - 0.60 N·m
03:27 AM solarwind: spot on agrees with my electronic model with the 0.30 - 6.00 N·m range
03:28 AM solarwind: that super low 0.05N·m range is essential for plastic screws, small electronics M2 screws, etc.
04:56 AM JT-Cave: morning
04:57 AM travis_farmer[m]: G'Morning
05:19 AM Tom_L: morning
05:52 AM pere: yay, <URL: http://linuxcnc.org/docs/devel/html/fr/ > is taking shape.
06:34 AM sensille: i think i would really love to have a history of coordinate offests
06:35 AM sensille: i would serve 2 purposes: a) post-mortem analysis to see where i went wrong when a part comes out bad b) "undo" when i accidentaly zero the wrong axis
06:52 AM jpa-: sensille: yeah - i have also been thinking about adding a "log" tab which would log every coordinate system change and maybe overrides etc. info
07:03 AM mrec: https://streamable.com/d10r0b DIY SMD Feeder
07:18 AM sensille: strange. i have the impression that i have to hit the axis zero/set button twice sometimes (in qtdragon hd)
07:18 AM sensille: after the first time it ends up at some random looking value
07:40 AM unterhaus: I wonder how Drewnabobber got probe basic working on a pi. seems like opengl on pi's isn't up to it
09:32 AM Lcvette[m]: TurBoss: 😲
09:33 AM Lcvette[m]: * Drewnabobber, BC, CA#9657 TurBoss : 😲
09:33 AM Lcvette[m]: Using a different backplate for probe basic?
09:36 AM Dusty[m]: That looks promising. You say "still chasing". Is setting up Remora a weekend project, or a new way of life?
09:38 AM Lcvette[m]: s/backplate/backplotter/
09:41 AM Lcvette[m]: Dusty: hahahaha... hopefully they can sort it all out, I get bombarded with rpi4 support requests for robe basic
09:42 AM Lcvette[m]: s/robe/probe/
09:42 AM Lcvette[m]: Ans new backplotter options are great
10:02 AM JT-Cave: Lcvette[m], what backplotter are you using now?
10:16 AM DrewnabobberBCCA: Whole point of using the sbc is that we can publish an image that anyone can just flash and use.
11:06 AM perry_j1987: mornin
11:06 AM Dusty[m]: Awesome. That's exciting. Does the Quartz64 board "just work"? I couldn't find any mention of Remora+Quartz64 on the internet.
11:06 AM perry_j1987: got my homing switches mounted on this new taig
11:07 AM perry_j1987: now to wire them up
11:08 AM DrewnabobberBCCA: No, it does not just work, the remora comp needs to be modified away from the BCM driver. We are not the only ones working on it, and once the comp uses SPIDEV it should be easier to move to other platforms as well.
11:14 AM Dusty[m]: So, if I'm not a developer and I want to get started today, would the best way would be just to buy an RPi, or is that stuff documented somewhere? Or, if I'm not in a hurry, should I wait a few months and try again "once the comp uses SPIDEV"?
11:17 AM DrewnabobberBCCA: There is zero posted schedule here. You should only every buy anything based on what it does today. I have watched 3 users now bring up CNC machines from zero using FlexiHAL/Remora with our posted RPI4 images and firmware. That's all I can say.
11:17 AM DrewnabobberBCCA: s/every/ever/
11:18 AM DrewnabobberBCCA: I think that most of our issues (I am not really the main LinuxCNC developer here) are around the backplotter in Probe Basic. If you can use Axis I think you will have a smoother experience in general.
11:18 AM DrewnabobberBCCA: (I am the designer of FlexiHAL)
11:19 AM DrewnabobberBCCA: When I say they brought it up from zero, I mean that, this was their first time working with LinuxCNC or OS CNC at all.
11:19 AM DrewnabobberBCCA: This was our goal (to make things more accessible).
11:28 AM Dusty[m]: I'm not using any backplotter. I'm making non-standard machines and building a custom GUI on top of the Python Interface. I just need LinuxCNC for motor control and coordination. I'm fine using PC's for now, but would like to migrate to RPi's in the future. But, if it wouldn't throw up a bunch of hurdles, I'd rather migrate sooner than later.
11:31 AM perry_j1987: tough to get rpi's now of days sure you want to go with them?
11:31 AM Dusty[m]: No, I'd rather not. That's why I was asking about the Quartz64 boards.
11:31 AM Dusty[m]: I want to use 3d printer boards. Remora is the path to that, I understand.
11:32 AM perry_j1987: what are you making
11:32 AM perry_j1987: i have machines here with mesa setups and machines with simple BOB parports
11:33 AM Dusty[m]: Right now a sort of macro-photography device, but I'm a professional glassblower looking to build some helpers.
11:34 AM perry_j1987: just an axis control?
11:34 AM Dusty[m]: No, it's got... uh.. I guess 4 axes, right now, and maybe one more coming.
11:35 AM perry_j1987: can you do with with grbl?
11:35 AM JT-Woodshop: I like http://www.qtpyvcp.com/ for building a gui
11:35 AM JT-Woodshop: you can make what ever you want
11:36 AM JT-Woodshop: http://www.qtpyvcp.com/tutorials/basic_vcp/index.html
11:36 AM Dusty[m]: I've been working on a grbl wrapper to do it with FluidNC (grbl fork). It's going to work, for sure, but grbl isn't going to work for everything I want to do.
11:37 AM JT-Woodshop: nap time here
11:42 AM Dusty[m]: * I've been working on a Python grbl client to do it with FluidNC (grbl fork). It's going to work, for sure, but grbl isn't going to work for everything I want to do.
11:43 AM Dusty[m]: * I've been working on a Python grbl client to do it with FluidNC (grbl fork). It's going to work, for sure, but grbl isn't going to work for everything I want to do, due to limitations with realtime interactivity.
12:00 PM Dusty[m]: * Drewnabobber, BC, CA (@_discord_717888255890161689:jauriarts.org) I'm not
12:23 PM CaptHindsight[m]: Quartz64 Model B = Quad-Core Rockchip RK3566
12:23 PM CaptHindsight[m]: https://www.pine64.org/quartz64b/
12:26 PM CaptHindsight[m]: https://forum.linuxcnc.org/media/kunena/attachments/31446/20min-test.jpeg rk3588 boards latency test
12:26 PM CaptHindsight[m]: https://forum.linuxcnc.org/media/kunena/attachments/31446/1hrtest.jpeg
12:29 PM CaptHindsight[m]: Dusty: are you planning on using LCNC for glassblowing?
12:37 PM CaptHindsight[m]: I've found that most glass workers don't think that a CNC glass lathe is possible
12:39 PM Dusty[m]: Yes, I'm planning to. Yeah, they're probably right. I mean, you can find examples of CNC glass lathes, but they turn out remarkably simple products, and I think they take a fair amount of tinkering and "don't touch it, it's finally working" to get that program set up.
12:41 PM CaptHindsight[m]: most shops can't afford a CNC lathe for glass anyway
12:41 PM Dusty[m]: Those tests say... 22ms jitter, or something? I haven't done enough of this for it to mean much to me. I ran a test on my machine last night, and ended up with a max of ~22k steps per second.
12:43 PM CaptHindsight[m]: Dusty: uS of jitter
12:43 PM Dusty[m]: Right. I'm doing something kind of different. I made a CNC lathe, and it didn't cost much, but it's not a machine I'm happy with, just to the nature of CNC lathe. I've put a lot of years into educating myself and prototyping. I may not ever be able to automate finished products, but I will have assistans doing prep work.
12:44 PM CaptHindsight[m]: the prep lathe ended up being more complicated than a working lathe
12:45 PM CaptHindsight[m]: IF you want to automate tube feeding and unloading prepped tubes
12:47 PM perry_j1987: any of you guys familar with xylotex boards?
12:47 PM Dusty[m]: Right now, I'm just trying to be able to work without RSI, so I'm not worried about that level of automation.
12:47 PM CaptHindsight[m]: had to also develop a low cost automated chuck
12:49 PM CaptHindsight[m]: http://xylotex.netfirms.com/OSCommerce/catalog/index.php
12:49 PM CaptHindsight[m]: perry_j1987: ^^
12:49 PM Dusty[m]: That sounds neat. I'd like to have a low cost automated chuck. But, the machines that I'm making aren't really anything like glass lathes.
12:50 PM perry_j1987: this taig i picked up has a xylotex 4.02 board in it
12:50 PM perry_j1987: someone labeled the outside of the enclosre gecko g540 lol
12:50 PM perry_j1987: oddly enough they have the same pinouts apparently cause i amde a stepconf with gecko g540 in the dropdown and got things working
12:51 PM CaptHindsight[m]: perry_j1987: looks like they use machinekit
12:51 PM CaptHindsight[m]: and BBB
12:51 PM perry_j1987: just mounted homing switches to the machine this morning and took the controller box apart and looking where to add them now
12:51 PM perry_j1987: no this is an older 2004+ board
12:51 PM perry_j1987: it looks like a precursor to the gecko g540 same size/layout
12:52 PM perry_j1987: 4 axis, connectors in same spots as the gecko
12:52 PM perry_j1987: just this uses phoenix terminals for the stepper connectors instead of db connectors like the gecko g540
12:52 PM CaptHindsight[m]: Dusty: i working on an automated dotter for boro. Puts dots on boro tubes, ~1k/hour
12:54 PM Dusty[m]: So, could I interpret those tests as ~22us max jitter? Which would mean somewhere north of steps at 20khz, if using a fast stepper driver? And, is it hard to set up the Quartz64 to get to the point of having it do that and having it run motors?
12:54 PM CaptHindsight[m]: handling hot boro is fun
12:54 PM Dusty[m]: Neat. That's a part of what I'm intending.
12:55 PM CaptHindsight[m]: Dusty: when using an external FPGA or micro over SPI or Ethernet one uses a servo thread and jitter only has to be <300uS
12:56 PM CaptHindsight[m]: 22uS is good enough to use a base thread and generate steps with GPIO
12:57 PM CaptHindsight[m]: but ARM boards have issues with development of the firmware and RT kernels
12:57 PM Dusty[m]: Are you going to sell machines or glass?
12:57 PM CaptHindsight[m]: most of the work is just ugly patches like the Rpi's
12:58 PM CaptHindsight[m]: Dusty: I make machines
12:58 PM Dusty[m]: I'm not familiar with any of that. Most of the work for me would be learning, I think.
12:59 PM CaptHindsight[m]: I skipped over the Quartz64
01:00 PM CaptHindsight[m]: but it looks like there is u-boot source for the RK3566 used on them
01:01 PM CaptHindsight[m]: so IF somebody configures u-boot and build a stable RT kernel they should be great for use with Remora or Mesa boards
01:04 PM CaptHindsight[m]: BUT what generally happens is people blindly just try stuff until it somehow works until it doesn't
01:04 PM CaptHindsight[m]: it just needs u-boot configured for real time, so no speed stepping or power management
01:04 PM Dusty[m]: Yeah, I'm tired of that path. So many "success mirages".
01:05 PM CaptHindsight[m]: and then it just needs a RT kernel
01:05 PM Dusty[m]: I mean, the "works until it doesn't".
01:05 PM CaptHindsight[m]: the armbian devs are a great example
01:05 PM CaptHindsight[m]: of "works until it doesn't"
01:06 PM Dusty[m]: That sounds like more I want.
01:06 PM Dusty[m]: * like more trouble than I want.
01:07 PM CaptHindsight[m]: i think it's all volunteers
01:08 PM CaptHindsight[m]: so just be aware of the quality
01:08 PM Dusty[m]: So, if I want something stable, it would be best to stick with a PC?
01:08 PM Tom_L: probably for now yes
01:10 PM Tom_L: you can get an rpi to work but it hasn't set the world on fire yet
01:11 PM CaptHindsight[m]: we usually estimate a couple months work for an experienced dev to build a proper u-boot and RT kernel on a new ARM SOC after the kernel is ready for mainline
01:11 PM CaptHindsight[m]: so about a year after the boards are available
01:12 PM CaptHindsight[m]: even worse for the rk3588 since parts shortages added another year to availability
01:14 PM CaptHindsight[m]: Dusty: Debian is probably the worst part with x86 since you might have to use non-free packages
01:15 PM Dusty[m]: Ah, I didn't even consider that the blobs might affect realtime performance. I guess I should have done the non-free install, and hoped for the best.
01:15 PM Dusty[m]: * Ah, I didn't even consider that the blobs might affect realtime performance. I guess I should *not* have done the non-free install.
01:17 PM CaptHindsight[m]: might make RT better
01:18 PM CaptHindsight[m]: the main issue with x86 is the BIOS, you never know what you'll get
01:19 PM Dusty[m]: CaptainHindsight (@_discord_702231000050040894:jauriarts.org) I don't think x86 is relevant to me, in hindsight. I'm pretty sure I'm using x64 architecture?
01:20 PM CaptHindsight[m]: x86/am64
01:21 PM Tom_L: somewhat where proprietary controls have an advantage but definitely not free
01:21 PM CaptHindsight[m]: Rpi's get lots of hype, even now when you can't even find a Rpi4 at a reasonable price
01:21 PM Dusty[m]: Just, generally, do you think picking up LinuxCNC is a wise choice? GRBL was mostly fine, but for realtime non-planned control, it has a minimum of like 150ms response time (unless you're stopping or starting).
01:22 PM Tom_L: lcnc is far more robust
01:22 PM Dusty[m]: It ought to be, it's a beast, lol.
01:22 PM CaptHindsight[m]: GRBL is fine for more simple CNC
01:22 PM Dusty[m]: I've never spent so long installing anything.
01:22 PM Tom_L: it takes some willpower :)
01:23 PM CaptHindsight[m]: LCNC usually has way more features than you need and it's easier to customize
01:24 PM Tom_L: just depends what the end goal is
01:24 PM Dusty[m]: Yeah. That was why I was looking this way, was ease of use. I figured out that I was making all of these work arounds that had flaws, and they took forever, and LinuxCNC just had a Python Interface with all of that stuff built in.
01:24 PM Tom_L: it takes some time to get it set up but is rather powerful
01:25 PM CaptHindsight[m]: LCNC gets snubbed by lots of *duino users and anti-PC people
01:25 PM Tom_L: plenty of help available
01:25 PM CaptHindsight[m]: but they usually don't know what they don't know yet about CNC
01:27 PM CaptHindsight[m]: https://yewtu.be/watch?v=ib4MXfZPTGg why LCNC vs GRBL
01:27 PM Dusty[m]: Yeah. I originally looked at the docs and balked. Come back a year or two later, and I'm like, "that stuff is built in... for free?" It looked like going 10 years in the past, back then, and now it looks like jumping 10 years into the future.
01:29 PM Tom_L: learning curve is a bit higher
01:31 PM unterhausen: I think the main problem with LCNC is that people immediately want something fancier than just 3 axis machining
01:32 PM unterhausen: lcnc is pretty trivial to set up for the capabilities that grbl will give you
01:35 PM Dusty[m]: Yeah, it's basically an appliance if you're setting up a 3 axis CNC. I set it up before I knew anything, and didn't have any trouble that was LinuxCNC's fault.
01:35 PM Dusty[m]: * knew anything, about 10 years ago, and didn't
01:38 PM Dusty[m]: Could you tell me any more about your glass machine? Would love to see the chucks you came up with, or anything at all.
02:04 PM CaptHindsight[m]: unterhausen: What stands out to me is the objection to using PC's, like people were abused by them at church
02:04 PM Lcvette[m]: for any hal experts, i posted a thread here because i could not find any information regarding home index pulse on non feedback step/dir configurations. this utilizes new firmware that PCW made to work specifically with linuxcnc 2.9. if you know how to configure the hal and have a few moments to copy and tweak the existing supplied config there and paste the correct configuration, I am sure many people moving to this setup would be as
02:04 PM Lcvette[m]: appreciative as myself!
02:04 PM Lcvette[m]: https://forum.linuxcnc.org/24-hal-components/48222-hal-help-for-home-to-index-with-stepgen-firmware-update#264372
02:04 PM CaptHindsight[m]: how have PC's gotten themselves into such a bad light?
02:12 PM JT-Woodshop: https://youtu.be/Q02EG5y4bBk?list=PLB00JHoTw1TeX82Qw8hoFLRJI89Us_jMw&t=860
02:13 PM XXCoder: lol interesting indeed
02:20 PM perry_j1987: got all 3 switches triggering wohoo
02:20 PM perry_j1987: now to get the sequence setup right
02:21 PM CaptHindsight[m]: Lcvette: I don't have answer for you. How did he intend that feature to be used? Without feedback what is an "index pulse"?
02:21 PM CaptHindsight[m]: i just have questions
02:23 PM JT-Woodshop: I'm not sure what they are for either
02:35 PM Lcvette[m]: CaptHindsight: thats what the firmware does apparantly
02:35 PM JT-Woodshop: firmware or hm2?
02:36 PM Lcvette[m]: it has a stepgen index pulse and the encoder input index pulse and it uses software i guess to reset the counter?
02:36 PM JT-Woodshop: hmm must be in the firmware
02:36 PM * Lcvette[m] posted a file: (130KiB) < https://libera.ems.host/_matrix/media/v3/download/matrix.org/IFZngCcSEgGFNCRSTGTsYwNX/7i92_chris%20(1).zip >
02:36 PM JT-Woodshop: but I might be wrong lol
02:36 PM Lcvette[m]: yes, its new firmware from Peter
02:37 PM Lcvette[m]: but im not sure how it all works myself as i could not find an example
02:37 PM CaptHindsight[m]: just wondering
02:38 PM Tom_L: custom firmware for you?
02:39 PM Lcvette[m]: yes
02:39 PM Lcvette[m]: posted above
02:40 PM * Lcvette[m] posted a file: (333KiB) < https://libera.ems.host/_matrix/media/v3/download/matrix.org/QoSFkepNCIpygWJOHDePesRy/7i92_chris.bit >
02:40 PM * Lcvette[m] posted a file: (5KiB) < https://libera.ems.host/_matrix/media/v3/download/matrix.org/PSvuVfwlIszChgrgTUKwgwYa/7i92_chris.pin >
02:40 PM * Lcvette[m] posted a file: (10KiB) < https://libera.ems.host/_matrix/media/v3/download/matrix.org/lPQlaUwoNBruKtVlaghENWsc/PIN_7I77_7I76_2SDIPD_34.vhd >
02:40 PM Lcvette[m]: there unzipped may be easier to open
02:42 PM Lcvette[m]: JT-Woodshop: you are correct, the firmware is specific to this method, but i searched every index pulse thread i could get returned and never found anyone actually using it so im flying a bit blind
02:42 PM JT-Woodshop: it's something new it seems
02:42 PM Lcvette[m]: figured i would make the thread i linked above in the Lcnc hal section in the event someone in the future needs an example
02:42 PM Lcvette[m]: yeah
02:49 PM * Lcvette[m] uploaded an image: (638KiB) < https://libera.ems.host/_matrix/media/v3/download/matrix.org/VIOarWcelobspeOuEzmANARZ/image.png >
02:50 PM Lcvette[m]: lol
02:50 PM Lcvette[m]: /o\
02:50 PM Tom_L: HM2DPLLTag MuxedQCountSelTag don't look familiar to me but i haven't looked at one in a long time
02:51 PM Tom_L: what's the pulse supposed to gain you?
02:51 PM travis_farmer[m]: the firmware Peter made for me has DPLL too
02:51 PM Tom_L: that i've seen
02:52 PM Lcvette[m]: the index pulse from the motor encoder is much more repeatable than the proximity switches for homing
02:52 PM Tom_L: so once it's in range the firmware looks for the pulse?
02:52 PM Tom_L: sounds about right
02:52 PM Lcvette[m]: my drives diod not like being run in feedback mode with Lcnc so i run open loop
02:53 PM Lcvette[m]: but have the board and encoders and want the advantage of the index pulse homing
02:53 PM Tom_L: you're running servos
02:54 PM Lcvette[m]: i often run pallets of parts and it sucks having to reset multiple offsets everytime i fire the machine up in the morning
02:55 PM Lcvette[m]: but the proximity sensors just are off just enough from day to day homing that I have too
02:55 PM Tom_L: the bit file indicates you're running steppers
02:55 PM Lcvette[m]: im running servos in open loop step direction
02:55 PM Tom_L: ok
03:13 PM XXCoder: very nice frank howarth video today
03:38 PM sensille: looking for a small dust collector for my 6040. could 550W be enough?
04:44 PM pcw---home: Lcvette[m]: There is a LinuxCNC forum thread on stepgen index but it may be for a step/dir controlled spindle
04:44 PM JT-Woodshop: what is the stepgen index for?
04:45 PM Lcvette[m]: pcw---home: ok, I may have skipped it if it said spindle
04:46 PM Lcvette[m]: i will go back and find
04:46 PM pcw---home: It behaves exactly the same as encoder index does for encoders but for stepgens
04:46 PM JT-Woodshop: cool
04:48 PM pcw---home: that is, when stepgen index-enable is set true and a hardware index event is detected, two things happen: the index enable is set false (to inform LinuxCNC) and the position is set to 0
04:50 PM * JT-Woodshop takes notes
04:50 PM Lcvette[m]: pcw---home: is it still using the encoders index pulse?
04:50 PM pcw---home: There are a couple people using it (there's a 7I85S config that has this feature)
04:50 PM Lcvette[m]: and how does it all tie together
04:51 PM pcw---home: Yes, its piggybacked on the same hardware pin if that's what you mean.
04:52 PM Lcvette[m]: homesw > encoder index pulse > stepgen index pulse > reset counter > record overshoot > move back to index pulse > set homed
04:52 PM Lcvette[m]: ?
04:53 PM pcw---home: it could be a separate pin but sharing the pin means that you have you choice of using encoder feedback or stepgen feedback
04:54 PM Lcvette[m]: so it is one or the other and not both used?
04:55 PM Lcvette[m]: if it is just stepgen, then what is the physical basis for the home position?
04:55 PM pcw---home: Its described in the LinuxCNC homing docs (only difference is you use stepgen index enable rather than encoder index enable)
04:56 PM Lcvette[m]: ie is it still using the inaccurate home switch to as the starting point?
04:57 PM pcw---home: Yes, search for switch, then search for index
04:57 PM Lcvette[m]: ie the encoder input is a physical locator
04:58 PM pcw---home: you need to search for the switch on rotary encoders since you get 1 index per turn
04:58 PM Lcvette[m]: ok, so it is still using the encoders physical index pulse output
04:59 PM pcw---home: also best to set the switch actuation point 180 degrees from index
04:59 PM Lcvette[m]: yup, saw that in my reading
04:59 PM pcw---home: to allow most margin
04:59 PM Lcvette[m]: give it room on both sided of the pulse
05:00 PM pcw---home: other wise you could get off by 1 turn
05:03 PM Tom_L: what vfd feature enables this index?
05:05 PM Tom_L: vhd* sry
05:08 PM pcw---home: Its encoded in the stepgen version
05:08 PM pcw---home: normal = ver 02
05:08 PM Tom_L: i see a "C2" would that be it?
05:08 PM pcw---home: swapable step/dir = ver 0x42
05:09 PM pcw---home: swapable+idx step/dir = ver 0xC2
05:09 PM Tom_L: looking at the vhd you made for Lcvette[m]
05:09 PM Tom_L: nice
05:10 PM Tom_L: is the HM2DPLLTag included in all the new bit files now?
05:10 PM pcw---home: Should be (if it fits)
05:10 PM Tom_L: yeah
05:11 PM pcw---home: Lcvette[m]'s config barely fit
05:11 PM Tom_L: are these functions documented anywhere?
05:11 PM pcw---home: every LUT used
05:11 PM Tom_L: besides the source
05:11 PM pcw---home: hostmot2 manual
05:11 PM Tom_L: ok
05:41 PM Lcvette[m]: 😲
05:41 PM Lcvette[m]: my firmware is fully loaded!
05:41 PM Lcvette[m]: 😄
07:20 PM Tom_L: seems appropriate in some way :)
07:23 PM Lcvette[m]: pcw---home: do you by chance remember anything else about that thread? I am 40 pages deep and have not found anything definitive on what the hal connections should look like
07:23 PM Lcvette[m]: or if im even in the correct thread
07:24 PM Lcvette[m]: seems the solutions should be posted to the topic starter thread to make searches easier
07:24 PM Lcvette[m]: also is there a way to just have one thread be displayed as a search result?
07:26 PM Tom_L: Lcvette[m], did you look at the hostmot2 man page?
07:27 PM Tom_L: on an encoder the index is a bidirectional pin fwiw
08:45 PM Lcvette[m]: Tom_L: i looked but im still very unsure of how to write whats needed out
08:46 PM Lcvette[m]: i get by in hall mainly through examples and can understand how it works but when there is something completely new i do not know how to build or write it
08:47 PM Lcvette[m]: i rely heavily on the config builders to geve me something close to whats needed and then usually fill in the blanks by other found examples
08:47 PM Lcvette[m]: so i will just revert back until i can find one
08:48 PM Lcvette[m]: unless any of you guys would mind showing the lines needed and i will gladly update the thread
08:52 PM Tom_L: Lcvette[m], for the bidirectional signal?
08:53 PM Tom_L: i don't know what pin the index is output to
08:53 PM Lcvette[m]: me either
08:53 PM Lcvette[m]: /o\
08:54 PM Lcvette[m]: i think its all internal stuff
08:54 PM Tom_L: for mine on the encoder it is like this:
08:54 PM Lcvette[m]: and thats the least comfortable place for me
08:54 PM Lcvette[m]: lol
08:54 PM Tom_L: net spindle-index-enable <=> hm2_[HOSTMOT2](BOARD).0.encoder.01.index-enable
08:54 PM Tom_L: net spindle-index-enable <=> spindle.0.index-enable
08:55 PM Lcvette[m]: thats how mine is now currently
08:55 PM Tom_L: so the ouput from the encoder index goes to the spindle index-enable
08:55 PM Tom_L: for an axis i dunno
08:55 PM Lcvette[m]: net x-index-enable joint.0.index-enable <=> hm2_7i92.0.encoder.00.index-enable
08:55 PM Tom_L: there you go
08:56 PM Lcvette[m]: i don't have to change anything?
08:56 PM Lcvette[m]: or add anything for the stepgen thing PCW was talking about?
08:56 PM Tom_L: on the encoder one, once the signal is sent it needs a reset that's the bidirectional part
08:56 PM Tom_L: i don't know. this is a new feature he wrote into it
08:57 PM Tom_L: pcw---home, ?
08:59 PM Tom_L: i don't find joint.x.index-enable in the docs yet
09:00 PM Lcvette[m]: Joint.0
09:00 PM Tom_L: i know
09:00 PM Lcvette[m]: oh you mean that line?
09:00 PM Tom_L: any joint
09:00 PM Lcvette[m]: yeah, i dunno, thats what has been in my config for 5 years now..
09:00 PM Lcvette[m]: not sire what it does
09:01 PM Lcvette[m]: or if its correct
09:01 PM Lcvette[m]: 😲
11:01 PM * Lcvette[m] posted a file: (1929KiB) < https://libera.ems.host/_matrix/media/v3/download/matrix.org/TXiQBMFWNBHynDGsKhqbEwxQ/Mesa%207i76%20Pinout%20Chart.xlsx >
11:02 PM Lcvette[m]: not sure if this may help anyone else, but i put it together for myself to help make machine connections
11:02 PM Lcvette[m]: it has come in handy for me quite a bit on little machine builds with most of the information needed to build a little no line pinout schematic