00:14 <set_> I saw it. I will look it over some more.

00:14 <set_> Thank you...

00:15 <set_> Everywhere I read, even by TI's SDK, it seems the math part is simple but then complicated because of different sources returning different examples of so-said math.

00:17 <set_> I mean. I made up this one: https://pastebin.com/HaAbF8Hv

00:18 <set_> I have changed it many times since that initial testing.

00:18 <set_> My latest-greatest seems to nail down the inches and mm aspect to the maxbotix sonar senser.

00:18 <set_> But...

00:19 <set_> It has bugs in it. It is like every so often, there is some glitch. I report back 01 or another odd value.

00:20 <set_> It should be 1 and not 01. So, something like blah()[1:-1] would alleviate that but...

00:20 <set_> Just every so often, something odd happens. It is running slowly so I can catch it. Every 4.5 seconds or so or less it prints.

00:21 <set_> Anyway, Let met get my latest.

00:22 <set_> I do something with foot = 1 && inch = (foot / 12) && mm = inch * 25.4.

00:24 <set_> here: https://pastebin.com/HG8QwJac

00:25 <set_> What do you say that source would read back on the MaxBotix or some sonar that promotes sonar in a sensor package?

00:39 <set_> ADC = (1.8 / 512) / inch && ADC_mm = (1.8 / 512) / mm <<< These lines in the source may not be right.

00:39 <set_> I say that because inch is not well defined.

00:39 <set_> If inch is not defined well enough, mm is out of whack too.

00:39 <set_> But...

00:40 <set_> The MaxBotix people saw in their EZ papers/datasheet that (v / 512) / inch.

00:40 <set_> I guessed at v.

00:41 <set_> I just say 1.8 since the high as it can go is 1.8v.

00:41 <set_> Oh.

00:41 <set_> I better watch it.

00:42 <set_> Less is good and I do not dictate what is less. More is bad since it can report higher than 1.8v. Hmm. I am clueless.

00:43 <set_> Maybe, they were saying v as in 3.3v.

00:48 <set_> Dang it.

00:48 <set_> 3.3v! vref

00:49 <set_> oops.

00:49 <set_> Luck of the draw...

00:50 <set_> So, 4094 with blah()[1:-1] <<< ?

00:52 <set_> I wonder. Is / divided by inch or is it / per inch?

00:52 <set_> Blah.

00:53 <set_> it is not vref. It is vcc.

00:59 <set_> I think ut oh'ed it.

00:59 <set_> Dang it.

01:00 <set_> I am at 2.20 on the ADC now. Argh...

01:15 <set_> Hey @zmatt: I tested the source. can I use it? No. Can I keep trying? Yes. Look at this reading: channel is: raw(0)0.06422466422466422

01:46 <set_> D = Vin * (2^n - 1) / Vref

01:47 <set_> That is what I got from TI's site.

01:48 <set_> So, if I had a POT to use, I could signify the voltage of Vin.

01:48 <set_> Anyway...up, up, and Otay.

08:05 <zmatt> set_: my code already converts the adc value to a voltage... that's why the method is named "voltage" :P

23:20 <cappie> hello I am trying to get GPIOs to toggle on a beaglebone ai64 with gpiod.  I have been trying with P8_07 which gpioinfo says is chip 1 offset 15.  However gpioset 1 15=1 doesn't bring the pin high.  It just stays floating around 0.7V and setting it low doesn't seem to do anything either.  I have configured it as an output and that is reflected

23:20 <cappie> in gpioinfo.  Am I missing a step?