<zmatt>
set_: it's now also a "context manager" which means you can use a with-statement to automatically disable the pwm: https://pastebin.com/hWrNVeHS
<zmatt>
(your script only disabled it on KeyboardInterrupt but not e.g. if some other error occurred)
balrog has quit [Read error: Connection reset by peer]
balrog has joined #beagle
<set_>
Oh.
<set_>
Oh.
<set_>
I changed the source to handle the two GPIO outputs to the driver and the PWM channel to the driver.
<set_>
I was using /dev/bone/pwm/1/b/enable for whatever reason.
<set_>
I will try another way.
<set_>
I will try /dev/pwm instead
<zmatt>
???
<set_>
I am on kernel 5.10.x. I think it is 5.10.x and it is now located at /dev/bone/pwm/.
<zmatt>
yes that's fine
<zmatt>
then you'd use e.g. Pwm('/dev/bone/pwm/1/b', frequency=20000, value=0)
<zmatt>
(using whatever pwm frequency and initial value is appropriate for the situation)
<set_>
oh. Okay, I thought something was up. Okay.
<set_>
20000 for frequency?
<set_>
Okay.
<zmatt>
I don't know, I saw you were using that in some of your code
<set_>
2000
<set_>
I thought it should be 50 or 60?
<set_>
or 40?
<zmatt>
yeah actually since this is a stepper motor driver it should almost certainly be way way lower than 20000
<zmatt>
the two-digit values you just mentioned sound more plausible, but I have no idea what is reasonable for a stepper
<set_>
Okay. I am not sure how the Hz/freq. should qualify as "correct" in this situation either. I mean...
<set_>
I mean...for i2c, I use some premade value having to do w/ some math equation just like in this instance.
<zmatt>
googling a bit it seems steppers maybe do support a few kHz
<set_>
Hmm.
<zmatt>
regardless, it depends on the specs of the stepper motor (and possibly the stepper motor driver)
<set_>
Let me go and check this one out in a bit. Right.
<set_>
I understand. There is literally no info. on the stepper driver but now the page I found is "admitting" to an IC onboard.
<set_>
This is good news.
<set_>
I can search the IC datasheet for ideas.
<zmatt>
also depends on how much torque you need... at higher speeds the motor will have less torque
<set_>
I read motor theory at times. I keep forgetting it, i.e. I can have something to read again and again!
<zmatt>
ah and there will also be a particular speed (the resonance frequency) you want to avoid (typically by staying above it)
<zmatt>
hmm, a pwm output isn't particularly ideal for driving steppers
<set_>
Oh?
<zmatt>
well for one, steppers are normally used because you want to be able to reach a particular position, which means you need to be able to specify the number of pulses you want... which is impossible to do with any sort of accuracy when using a pwm output
<set_>
Hmm.
<set_>
I thought pwm was exactly what is needed for drivers to interface w/ motors (stepper in this case).
<set_>
I mean...
<zmatt>
and you probably want to maintain a 50% duty-cycle while changing the frequency, which is not something you can do with linux' pwm interface (in a glitch-free way)
<set_>
I see that GPIO can be used to handle four pins.
<set_>
I noticed.
<set_>
I noticed that the glitch part is prone.
<zmatt>
I doubt that
<set_>
Not in the sense you understand...of course.
<set_>
We do not understand the same thing, i.e. theory, facts and so on.
<zmatt>
so far it sounds to me like your setup is entirely broken, while the problem I'm talking about is a subtle glitch you're almost certainly never going to notice because you can't accurately pulse-count anyway
<set_>
Ha.
<set_>
Probably.
<set_>
Where is all this info?
<set_>
I mean, you have been properly informed somehow.
<zmatt>
"drivers to interface w/ motors (stepper in this case)" ... different types of motors require different kinds of control, steppers in particular are totally different from everything else
<set_>
I am missing a major context that did not "pass my desk."
<set_>
Oh.
<set_>
Okay.
<set_>
I agree.
<set_>
I mean...
<set_>
If one was to theorize how many ways one could interface from driver to motor, it is unstoppable and elongated in text.
<zmatt>
afk
<set_>
For instance, I...fine.
xet7 has quit [Quit: Leaving]
brook has quit [Remote host closed the connection]
brook has joined #beagle
Shadyman has joined #beagle
starblue has quit [Ping timeout: 252 seconds]
starblue has joined #beagle
brook has quit [Remote host closed the connection]
brook has joined #beagle
vagrantc has quit [Quit: leaving]
mattb00ne has quit [Ping timeout: 268 seconds]
Stat_headcrabed has joined #beagle
mattb00ne has joined #beagle
starblue has quit [Ping timeout: 276 seconds]
starblue has joined #beagle
wiagn has joined #beagle
Stat_headcrabed has quit [Ping timeout: 255 seconds]
wiagn is now known as Stat_headcrabed
brook has quit [Remote host closed the connection]
brook has joined #beagle
AKN has joined #beagle
brook has quit [Ping timeout: 260 seconds]
ikarso has joined #beagle
wiagn has joined #beagle
Stat_headcrabed has quit [Ping timeout: 265 seconds]
wiagn is now known as Stat_headcrabed
mattb00ne has quit [Ping timeout: 268 seconds]
mattb00ne has joined #beagle
brook has joined #beagle
wiagn has joined #beagle
Stat_headcrabed has quit [Ping timeout: 265 seconds]
wiagn is now known as Stat_headcrabed
xet7 has joined #beagle
mattb00ne has quit [Ping timeout: 248 seconds]
wiagn has joined #beagle
Stat_headcrabed has quit [Ping timeout: 252 seconds]
wiagn is now known as Stat_headcrabed
wiagn has joined #beagle
Stat_headcrabed has quit [Ping timeout: 255 seconds]
wiagn is now known as Stat_headcrabed
otisolsen70 has joined #beagle
wiagn has joined #beagle
Stat_headcrabed has quit [Ping timeout: 265 seconds]
wiagn is now known as Stat_headcrabed
AKN has quit [Ping timeout: 265 seconds]
starblue has quit [Ping timeout: 268 seconds]
starblue has joined #beagle
mattb00ne has joined #beagle
wiagn has joined #beagle
Stat_headcrabed has quit [Ping timeout: 276 seconds]
wiagn is now known as Stat_headcrabed
mattb00ne has quit [Ping timeout: 265 seconds]
Stat_headcrabed has quit [Client Quit]
ft has quit [Quit: leaving]
AKN has joined #beagle
starblue has quit [Ping timeout: 250 seconds]
starblue has joined #beagle
rob_w has joined #beagle
zjason` is now known as zjason
Posterdati has quit [Ping timeout: 276 seconds]
outrageous has quit [Remote host closed the connection]
Posterdati has joined #beagle
florian has joined #beagle
otisolsen70_ has joined #beagle
otisolsen70 has quit [Ping timeout: 246 seconds]
otisolsen70__ has joined #beagle
otisolsen70_ has quit [Ping timeout: 255 seconds]
Posterdati has quit [Ping timeout: 246 seconds]
Posterdati has joined #beagle
Shadyman has quit [Quit: Leaving.]
starblue has quit [Ping timeout: 252 seconds]
starblue has joined #beagle
otisolsen70_ has joined #beagle
otisolsen70__ has quit [Ping timeout: 268 seconds]
otisolsen70__ has joined #beagle
otisolsen70_ has quit [Ping timeout: 276 seconds]
starblue has quit [Ping timeout: 264 seconds]
starblue has joined #beagle
mattb00ne has joined #beagle
Guest4494 has joined #beagle
<Guest4494>
I notice that since Jan. 23, the logs of this channel have been zero bytes, i.e., logging isn't happening.
brook has quit [Ping timeout: 250 seconds]
mattb00ne has quit [Ping timeout: 264 seconds]
brook has joined #beagle
mattb00ne has joined #beagle
<jfsimon1981_c>
Hi,
<jfsimon1981_c>
Are some of you running Beagleboards for very long time continusouly ? I'm looking for how reliable is the Flash storage in long time continuous run.
<jfsimon1981_c>
I've been using some of them for about 2 years almost non stop, there doesn't seem to have any issue at the moment
<jfsimon1981_c>
Projection is more like 8 years or more.
brook has quit [Ping timeout: 268 seconds]
brook has joined #beagle
<Guest4494>
When I'm in u-boot, i.e., at the => prompt, is that code that's running at that point from the BBB's ROM?
brook_ has joined #beagle
brook has quit [Ping timeout: 268 seconds]
brook_ has quit [Read error: Connection reset by peer]
brook has joined #beagle
brook has quit [Ping timeout: 260 seconds]
mattb00ne has quit [Ping timeout: 255 seconds]
mattb00ne has joined #beagle
brook has joined #beagle
florian has quit [Quit: Ex-Chat]
starblue has quit [Ping timeout: 264 seconds]
starblue has joined #beagle
otisolsen70__ has quit [Quit: Leaving]
AKN has quit [Read error: Connection reset by peer]
mattb00ne has quit [Ping timeout: 250 seconds]
brook_ has joined #beagle
brook__ has joined #beagle
brook has quit [Ping timeout: 276 seconds]
brook_ has quit [Ping timeout: 248 seconds]
mattb00ne has joined #beagle
starblue has quit [Ping timeout: 265 seconds]
starblue has joined #beagle
xet7 has quit [Ping timeout: 264 seconds]
vagrantc has joined #beagle
brook__ has quit [Remote host closed the connection]
brook has joined #beagle
ikarso has quit [Quit: Connection closed for inactivity]
starblue has quit [Ping timeout: 256 seconds]
CrazyEddy has quit [Ping timeout: 248 seconds]
otisolsen70 has joined #beagle
CrazyEddy has joined #beagle
starblue has joined #beagle
otisolsen70 has quit [Quit: Leaving]
Guest4494 has quit [Quit: Client closed]
rob_w has quit [Quit: Leaving]
ft has joined #beagle
vagrantc has quit [Quit: leaving]
brook_ has joined #beagle
ikarso has joined #beagle
brook has quit [Ping timeout: 250 seconds]
brook_ has quit [Ping timeout: 246 seconds]
brook has joined #beagle
xet7 has joined #beagle
starblue has quit [Ping timeout: 246 seconds]
KevinP has joined #beagle
buzzmarshall has joined #beagle
<zmatt>
jkridner: could you tweak https://beagleboard.org/chat to make it clearer that the whitequark.org link is where current logs are (since 2021-05-27) and the nslu2-linux.org link is only for really old logs (until 2021-06-02)
<zmatt>
I wonder if there's a way to get the old logger to stop producing logs but I don't know who is responsible for it
<zmatt>
Guest4494: in case you do end up reading the right logs, u-boot is not in ROM, it's loaded from eMMC (or from SD if there's no u-boot on eMMC or if you've powered on while holding down the S2 button)
brook has quit [Remote host closed the connection]
starblue has joined #beagle
mattb00ne has quit [Ping timeout: 252 seconds]
<KevinP>
Can anyone clear up my confusion regarding the buffer length parameter when doing a continuous read on the ADC? For example if I set the buffer length to 1024, does that mean 128 readings for the 8 AINs?
<zmatt>
no I don't think so
<zmatt>
pretty sure it just means 1024 samples
<zmatt>
note that the AINs are sampled sequentially, not simultaneously
outrageous has joined #beagle
<KevinP>
zmatt, I believe that it meaning samples is the conclusion that I am coming to as well.