00:14 <set_> Dang it. One last driver and some wire-re...

01:31 <mattb00ne> zmatt can you add some data to your repos so I can cite them properly?

01:31 <mattb00ne> https://coderefinery.github.io/github-without-command-line/doi/

01:38 <set_> Hello. I found this idea(s): https://libguides.brown.edu/citations/styles

01:41 <set_> mattb00ne: Use MLA, i.e. as it is easier. Or...one could just plagarize?

01:41 <set_> Ha.

01:41 <set_> I once quoted some guy at his house but I had to put the source.

01:42 <set_> They wanted like 25 sources. After reading and getting ideas, I finally could not find the last quote, e.g. hence the last quote from a stranger's home!

01:43 <set_> Yikes...

01:43 <set_> Anyway, good luck w/ your citing. I like MLA, i.e. as I am not doing things w/ APA style much or ever.

01:44 <set_> Psychiatric stuff has its up and downs, ha, but even Debian, NO ARMHF stuff (sad to say), has their own take on it!

01:45 <set_> I tried to put the debian psych stuff on the BBB. No go.

01:45 <set_> aarch64!

01:49 <set_> Just a heads up here, it will send you down some dark, not-so-friendly tunnels. I kept searching for some good stuff. Um, I never made it to good stuff but I will tell you one thing...

01:49 <set_> The med stuff may be easier on the senses. Those older tests on people and animals is taking it too far.

01:54 <set_> easy-peasey: https://www.psychopy.org/

01:54 <set_> No armhf. Blah.

01:57 <set_> or...was that neurodebian. Hmm. oh well. Sleep-me-to-sensory-overload Captain!

07:23 <set_> Nope.

07:23 <set_> I checked the motor. The software runs (as expected). Driver damage most likely.

07:24 <set_> Dang it.

07:24 <set_> Time to pull this pup apart!

08:04 <set_> I am not finding any issues w/ the driver outside of the chip on it. It may be burn-a-did up. Not sure right now...aw.

16:40 <zmatt> mattb00ne: I disagree conceptually with what they're suggesting there. they're creating an identifier for a specific published dataset, while for citation you'd want to reference the project itself, at least in this case. your code may care about using a specific version of py-uio, but that would be best solved using git submodules (if your code is in a git repository)

16:42 <zmatt> mattb00ne: regardless, py-uio has no actual release (yet) and I don't particularly want to just randomly declare its current state to be a release

19:05 <mattb00ne> ok

19:06 <mattb00ne> I wil use the generic citation then

19:39 <Guest4494> On the beaglebone black, does the u-boot code live in the BBB's firmware or is it on the storage device, e.g., eMMC or uSD card?

21:21 <zmatt> I wonder what he event meant by "the BBB's firmware"

21:21 <zmatt> *even

21:23 <zmatt> set_: one of your pastes has Pwm('/1/b/')

21:26 <zmatt> set_: that's definitely wrong, it should either be a full path or it should be relative to /dev/pwm which is where the symlinks are on the current stable image, e.g. Pwm('ehrpwm1a') is short for Pwm('/dev/pwm/ehrpwm1a')

21:27 <zmatt> set_: if the image you're using puts symlinks in /dev/bone/pwm/ then you need to write it out in full

21:28 <zmatt> also, if the argument starts with a / it's always interpreted as absolute path

21:33 <zmatt> in most cases you should also initialize your pwm output when creating it, by providing the desired frequency and initial value (usually 0)

21:33 <zmatt> e.g.: pwm1a = Pwm('/dev/bone/pwm/1/a/', frequency=2000, value=0)

21:35 <zmatt> in the rest of your code just change pwm1a.value, don't mess with frequency nor with enabled except to disable it at the end

23:00 <set_> Thank you!

23:01 <set_> I will reread what you have listed here and take a breathe but later!

23:01 <set_> I cannot breathe right now.

23:01 <set_> ha. No joke. I am clogged.

23:02 <set_> @zmatt: They have these things now.

23:02 <set_> It is called /dev/bone/*

23:02 <set_> For some reason, everything is located at /dev/bone/pwm/ and etc.

23:02 <set_> .../dev/bone/i2c/ and on and on.

23:03 <set_> But okay.

23:03 <set_> I will try it later once my breathing is back unclogged.

23:55 <zmatt> set_: also, you still seem to be using two pwm channels and I don't understand why. your motor driver has only one pwm input (PUL)

23:59 <zmatt> set_: btw I've made some improvements (mainly better sanity-checking) to https://pastebin.com/R70P1wAn ... hopefully without introducing new bugs ;)

23:59 <zmatt> it should give more useful errors when misused