mattb0ne has quit [Ping timeout: 246 seconds]
<set_> Hello again...thank you!
<set_> I can finally learn about PSDK, TISCI, and the TRM in coordination.
<set_> For some reason, I never witnessed the TISCI pages.
<set_> anyway, thank you and stuff.
vagrantc has quit [Quit: leaving]
vagrantc has joined #beagle
mattb0ne has joined #beagle
<mattb0ne> thanks static!
starblue has quit [Ping timeout: 248 seconds]
<mattb0ne> though looking at the manual I do not see much about setting the trigger voltage to 5V vs 24V
starblue has joined #beagle
<mattb0ne> ok I want to use PWM to control a stepper
<set_> Hmm.
<set_> is that doable?
<set_> I thought you would use four GPIO pins. I may be wrong. What driver are you using?
<mattb0ne> I have a driver the CL86T
<mattb0ne> I need to feed it a pulse train
<mattb0ne> I am worried about using the PWM since that is a way to get a range of voltages
<mattb0ne> I need the level to be 5V but play with the pulse frequency
<mattb0ne> ahh nm zmatt has a pulse train example
<mattb0ne> woohoo
<mattb0ne> zmatt: what pin does the pulse train use
<mattb0ne> @zmatt: does r14 mean pin 14?
<set_> Oh.
<set_> Okay.
<set_> I have not read the CL86T datasheet yet.
<set_> It is getting late. Maybe another day I can read it and help out...
<set_> I will go and research the datasheet in a day or two. Who knows? I may find some valuable in it.
<set_> Oyostepper has something about hunting. It got me spooked. I will try again later.
<set_> Odd.
<set_> Very peculiar.
<set_> The look up of the cl86t for the datasheet gets spookier the more I research it.
Shadyman has joined #beagle
nslu2-log has quit [Ping timeout: 240 seconds]
nslu2-log has joined #beagle
Cocus has quit [Quit: Client closed]
vagrantc has quit [Quit: leaving]
mattb0ne has quit [Ping timeout: 240 seconds]
nslu2-log has quit [Ping timeout: 264 seconds]
<zmatt> argh mattb0ne keeps doing drive-by questions and then leaves again
nslu2-log has joined #beagle
mturquette has quit [Ping timeout: 250 seconds]
mturquette has joined #beagle
<zmatt> mattb0ne: just curious, have you at any point considered buying products that suck less?
<zmatt> (hopefully you'll read the irc log)
<zmatt> like, this thing is an intelligent closed-loop stepper position controller with encoder feedback, yet instead of being able to give it commands on where to go its control interface requires individual pulses again (like a dumb stepper driver would require)
<zmatt> and the product has a V3 and V4 but the shop page doesn't specify which one you're buying and the product photos are a mix of V3 and V4... are they implying the version you get is random? :P
CrazyEddy has quit [Ping timeout: 250 seconds]
nslu2-log_ has joined #beagle
nslu2-log has quit [Read error: Connection reset by peer]
nslu2-log_ is now known as nslu2-log
Guest75 has joined #beagle
<Guest75> hi
<Guest75> I am facing no space left on the begal bone black device. how to free up some space
Guest75 has quit [Quit: Client closed]
011AAEBMJ has joined #beagle
renrelkha has quit [Quit: bye]
renrelkha has joined #beagle
nslu2-log has quit [Remote host closed the connection]
nslu2-log has joined #beagle
Shadyman has quit [Remote host closed the connection]
mattb0ne has joined #beagle
<mattb0ne> back
<mattb0ne> I am not going to lie I am a bit dissappointed with these closed loop steppers in terms of interfacing with them
<mattb0ne> I bought them because they had a manual but I should of read the manual before purchasing
<mattb0ne> doh
<mattb0ne> it would be nice to not have to deal with pulses
<mattb0ne> but here I am
<mattb0ne> i realized my PWM question was somewhat dumb
<mattb0ne> but I am confused on how I can make the PWM logic behave like the pulse train code you have
<mattb0ne> @zmatt I was hoping to just drive the stepper motor in a similar way
mattb0ne has quit [Ping timeout: 268 seconds]
<zmatt> mattb0ne: I wouldn't use a PWM output, I'd use a PRU core to drive the stepper (and using the CW/CCW mode seems more convenient than the PUL/DIR mode, but either could be made to work)
mattb0ne has joined #beagle
xet7 has joined #beagle
<mattb0ne> @zmatt when you say use the PRU to drive the stepper
<mattb0ne> like your pulse train example
<zmatt> I have no idea what my pulse train example is
<mattb0ne> in the py-uio pru example
<zmatt> ?
<mattb0ne> or is there something more direct
<mattb0ne> preferably in C so I can understand it a bit more
<zmatt> lol I don't even remember making that example
<mattb0ne> are you saying just toggle the pin up and down
<mattb0ne> i was thinking of using the PWM and just varing the frequency at 50% duty
<mattb0ne> and I can just move it up and down as needed since I will be constantly sending movements to the stepper
<mattb0ne> just changing the direction and speed
<zmatt> mattb0ne: https://pastebin.com/haYV8W8m I mean something like
<zmatt> and then the other PRU core can set the target value
<zmatt> essentially just turn the PRU core into a dedicated peripheral for this control interface
<zmatt> having said that, the load cell is so slow that you can easily send a few hundred pulses to the stepper in between two load cell measurements
<zmatt> if that's enough then you don't even need the second pru core
<zmatt> but using separate cores means you don't have to think about it
<mattb0ne> i could just increase the delay to compensate?
<zmatt> ??
<zmatt> what delay?
<mattb0ne> the wait
<zmatt> what wait?
<mattb0ne> so wait 100 us
<zmatt> and to compensate for what?
<zmatt> what are you talking about?
<mattb0ne> for the fact that the load cell is slow
<mattb0ne> I guess since it will not do anything that is dumb
<mattb0ne> forget what I said lo
<mattb0ne> lol
<zmatt> what's there to compensate? the load cell just doesn't support a sample rate higher than 1200 samples per second
<mattb0ne> right
<zmatt> so you've got 833 μs to process each load cell measurement
<mattb0ne> i guess my other question is regarding the stepper motor and the PRU sending pulses to fast
<mattb0ne> I think the max frequency is 300 kHz
<mattb0ne> so 3us
<zmatt> you probably need at most a few μs to receive, parse, and filter the load cell measurement and compute the new target value for your stepper, so that'll leave you with more than 800 μs to send pulses
<zmatt> 500 kHz max iirc the datasheet said
<zmatt> 1us pulse time, 1us between pulses
<mattb0ne> at 5VDC logic
<mattb0ne> but I have no idea what the rotary switch thing means
<zmatt> right, which I assume you're using
<zmatt> it means there's a rotary switch, if you have the V4 at least
<zmatt> to select 5V vs 24V input
<mattb0ne> right but I am looking at the controller
<zmatt> do you have a V3 or V4 ?
<mattb0ne> and I do not see the switch
<mattb0ne> V4
<mattb0ne> page 5 talks about setting the current
<mattb0ne> for the motor but I cannot find where they talk about setting the control logic
<zmatt> apparently it's "on top" .. where the SW1-SW8 dip switches are also located I guess?
<zmatt> on the front panel I see a marking there (right of SW1) that says 5V and 24V
<zmatt> which sounds like it's a label for the switch
<zmatt> unfortunately this is the only photo of the V4 I've been able to find
<zmatt> the rest is all V3
<zmatt> never mind, there's more V4, but not one of the top
<mattb0ne> I see what you mean, but there isnt like a physical swwitch like for the microstepping
<zmatt> what's there then?
<mattb0ne> I will need to get a mini screwdriver maybe to toggle something
<zmatt> photo?
<mattb0ne> let me take a pic one moment
<mattb0ne> need to get back to my desk
<zmatt> btw I saw they do also have a version of this thing that can be given commands via modbus (over rs485), but it's 3.5x as expensive
Stat_headcrabed has joined #beagle
<zmatt> a bit weird that they're suggesting PUL/CW/CCW are active-low signals, I somehow doubt that's true
<zmatt> maybe the signal diagram is actually for PUL-/CW-/CCW- assuming you're using common-anode
<zmatt> yeah, that must be it, since they're showing ENA as active-high while that's definitely false, it's active-low (i.e. it's actually a disable-signal, not an enable-signal)
mattb0ne has quit [Ping timeout: 268 seconds]
<zmatt> god I hate linker scripts
mattb0ne has joined #beagle
<mattb0ne> my internet is terrible today
<mattb0ne> ok so in retrospect
<mattb0ne> it is rather obvious now that you point out the markings on the front
<mattb0ne> but in the moment I was reading manual where it was referencing a rotary switch
<mattb0ne> so that is my defense
<zmatt> yeah that switch isn't very rotary
<zmatt> looks pretty linear to me
<mattb0ne> ok I think i have a plan
<mattb0ne> I will waste a PRU but i think I am going to go with having that snippet dedicated to doing the pulses
<mattb0ne> on the other the filtering which is TBD
<zmatt> here's some further experimenting I've done: https://pastebin.com/QveJ2hYA
<zmatt> I'm still not sure what the best way is to get shared variables allocated at a fixed location such that the compiler generates efficient access
<mattb0ne> question for you though why do you think CW/CCW control is better than PUL/DIR
<zmatt> easier to control
<zmatt> doesn't require a 2ms delay when changing direction
<zmatt> 2us
<zmatt> as for filtering, a simple 2nd order low-pass filter (like the IIR filters used by the EM100) are super simple, but I don't exclude the possibility there might be better filters
<zmatt> but afk for a bit
mattb0ne has quit [Ping timeout: 240 seconds]
mattb0ne has joined #beagle
ikarso has joined #beagle
<mattb0ne> also I see the EM100 will do a bit of filtering even at 1200 samples/s with the FIR mode so I will see how I look with that.
jfsimon1981_b has joined #beagle
jfsimon1981 has quit [Remote host closed the connection]
mattb0ne has quit [Ping timeout: 268 seconds]
jfsimon1981_b has quit [Remote host closed the connection]
jfsimon1981_b has joined #beagle
Guest72 has joined #beagle
<Guest72> Hi all. Beagle Play has CSI camera connector. Are supported MIPI-CSI2 cameras ? And libcamera ?
jfsimon1981_b has quit [Remote host closed the connection]
jfsimon1981_b has joined #beagle
vagrantc has joined #beagle
mattb0ne has joined #beagle
Guest72 has quit [Quit: Client closed]
mattb0ne has quit [Ping timeout: 240 seconds]
CrazyEddy has joined #beagle
<NishanthMenon> http://bbb.io/discord
<NishanthMenon> Guest72: CSI2 / beagleplay: https://git.beagleboard.org/beagleplay/beagleplay/-/blob/main/test-reports/dvt/test-procedure/test_camera.md -> MIPI-CSI2 smart sensors work the best. I have best results with ov5640
PJimAFK is now known as PhotoJim
Cocus has joined #beagle
mattb0ne has joined #beagle
Stat_headcrabed has quit [Quit: Stat_headcrabed]
mattb0ne has quit [Ping timeout: 265 seconds]
noahm has quit [Quit: reboot]
noahm has joined #beagle
mattb0ne has joined #beagle
mattb0ne has quit [Ping timeout: 240 seconds]
mattb0ne has joined #beagle
mattb0ne has quit [Ping timeout: 240 seconds]
mattb0ne has joined #beagle
<mattb0ne> would two PRUs accessing the same location in shared memory constitute a race condition?
ikarso has quit [Quit: Connection closed for inactivity]
mattb0ne has quit [Ping timeout: 246 seconds]
vagrantc has quit [Quit: leaving]
mattb0ne has joined #beagle
vagrantc has joined #beagle
Cocus has quit [Ping timeout: 245 seconds]
<mattb0ne> @zmatt how do I know what pin is what in r30
vagrantc has quit [Quit: leaving]