**** BEGIN LOGGING AT Sat Jun 20 03:00:22 2020
Jun 20 03:40:32 <set_> I am using vue.js w/ node.js to promote video findings on the BBB. No luck so far!
Jun 20 03:40:50 <set_> I think my html is messed up so far.
Jun 20 03:44:46 <set_> no errors, just blank!
Jun 20 03:50:30 <set_> Anyway. I will keep checking.
Jun 21 00:46:01 * set_ sorry for the mishap yesterday w/ my questionable PWM-analog reference. It is digital and has "square" like waves on the oscilloscope. My bad!
Jun 21 00:46:24 <MattB0ne> not a problem
Jun 21 00:46:29 <set_> Like you did not know!
Jun 21 00:46:33 <set_> Sheesh.
Jun 21 00:46:37 <MattB0ne> i was confused
Jun 21 00:46:44 <set_> Oh. I was dead wrong!
Jun 21 00:46:49 <MattB0ne> and I was desparate to avoid having to buy something else
Jun 21 00:46:55 <MattB0ne> so hoping there was a way
Jun 21 00:47:01 <set_> Too much work makes Jack a dull boy.
Jun 21 00:47:31 <set_> MattB0ne: I hope you have found those pins to be of some use, i.e. those leftover pins you are to use.
Jun 21 00:48:02 <set_> Did you find a chip yet?
Jun 21 00:48:25 <set_> DRV or L298 or something similar?
Jun 21 00:49:07 <set_> Also, like people say, you can always just GND all the leftover pins on the L298 instead of utilizing them.
Jun 21 00:50:13 <set_> I read that "fact" over on many books and articles. I actually first heard it from @zmatt and then read it in Molloy's book about the BBBW and PocketBone.
Jun 21 00:50:58 <set_> Sorry. PocketBeagle.
Jun 21 00:52:44 <MattB0ne> https://www.amazon.com/NOYITO-High-power-2-Channel-Instantaneous-Capability/dp/B082VS65BZ
Jun 21 00:52:50 <MattB0ne> got this one
Jun 21 00:54:45 <set_> Okay. I am off to look at it.
Jun 21 00:57:09 <set_> That seems simple enough. It shows a 12v output.
Jun 21 00:57:30 <set_> I saw that it supposedly works w/ 3.3v and 5v signaling.
Jun 21 00:57:43 <MattB0ne> which is good
Jun 21 00:57:58 <MattB0ne> though i have a level shifter if needed
Jun 21 00:58:13 <MattB0ne> now what I am stuck on is getting my load cell digitizer to work
Jun 21 00:58:17 <set_> Right but you have to remember that if the current reverses into the BBB, you need to be protected.
Jun 21 00:58:30 <MattB0ne> why would it reverse
Jun 21 00:58:33 <set_> load cell digitizer? Let me go and look that one up.
Jun 21 00:58:37 <MattB0ne> pwm is one way
Jun 21 00:59:40 <set_> It would reverse for many reasons.
Jun 21 00:59:50 <set_> Let me get my book again.
Jun 21 01:00:34 <MattB0ne> em100g
Jun 21 01:00:40 <MattB0ne>  from flintec
Jun 21 01:00:47 <MattB0ne> my weights are all off
Jun 21 01:01:17 <MattB0ne> so if I put a 50g weight the reading is 1
Jun 21 01:01:24 <MattB0ne> and 100g is 2
Jun 21 01:01:35 <MattB0ne> 500g is 10
Jun 21 01:01:38 <MattB0ne> 1kg is 20
Jun 21 01:01:50 <MattB0ne> so it is consistent but consistently wrong
Jun 21 01:06:59 <set_> Heat, power, saturation, um, there are many reasons why current can "invade" in reverse.
Jun 21 01:07:38 <set_> I keep finding that water analogy.
Jun 21 01:07:49 <set_> I do not like the water analogy.
Jun 21 01:08:43 <set_> Water goes towards the lowest portion of space b/c of gravity. Electricity is more like a mosh pit at a large concert.
Jun 21 01:09:04 <set_> One cell bounces against another cell.
Jun 21 01:09:11 <MattB0ne> well I will keep an eye on it
Jun 21 01:09:27 <MattB0ne> right now I need to focus on these load cell readings
Jun 21 01:09:50 <set_> Hey. I will go and look up load cell. Who knows? I may find something interesting you and I can use.
Jun 21 01:10:09 <zmatt> MattB0ne: btw you realized the jrk has a pwm input, so you can control it using a pwm pin instead of using the serial protocol?
Jun 21 01:10:44 <MattB0ne> zmatt: I did not I will take a look again. I gave a cursory look at the manual
Jun 21 01:11:10 <set_> Load cell, like a weight management scale?
Jun 21 01:11:56 <set_> So, if someone stomps on a specific section of house, bars block 'em in?
Jun 21 01:12:01 <set_> Ha.
Jun 21 01:12:15 <MattB0ne> i have planar beam load cells that are not weighing incorrectly like I typed earlier
Jun 21 01:12:22 <set_> Oh.
Jun 21 01:12:34 <set_> I just sold one.
Jun 21 01:12:42 <set_> Those things go like hot cakes.
Jun 21 01:12:54 <zmatt> MattB0ne: I assume you read the manual thoroughly to check if it needs to be calibrated or something?
Jun 21 01:13:12 <set_> Anyway...PWM stuff always needs to be "calibrated" from the Pololu stuff.
Jun 21 01:13:26 <set_> They have that Windows interface for that idea.
Jun 21 01:13:50 <MattB0ne> i have
Jun 21 01:14:03 <MattB0ne> now granted that does not mean much
Jun 21 01:14:18 <MattB0ne> i have been messing with the calibration for a bit
Jun 21 01:14:24 <MattB0ne> let me ask you this zmatt
Jun 21 01:14:37 <MattB0ne> does it make sense for a digitizer to always be reading ADC counts
Jun 21 01:14:42 <MattB0ne> even with nothing on the load cell
Jun 21 01:14:46 <set_> I am the same way. Sometimes I read so much, I just cannot get clarity.
Jun 21 01:15:04 <zmatt> MattB0ne: I have no idea what you're asking
Jun 21 01:15:38 <set_> "counts" mean what?
Jun 21 01:16:14 <zmatt> also the load cell manual even has a section titled "Calibration" in the Getting Started chapter
Jun 21 01:16:21 <set_> Oh. You mean that "counts" is the weight displayed.
Jun 21 01:16:36 <MattB0ne> if I have nothing on the load cell it should not give a signal right
Jun 21 01:16:46 <MattB0ne> like no reading
Jun 21 01:16:59 <zmatt> ??
Jun 21 01:17:16 <zmatt> it'll give a reading if you ask for one
Jun 21 01:17:25 <set_> I think you can have it read back on a display or terminal many things.
Jun 21 01:17:30 <zmatt> why would it matter if anything is on the load cell?
Jun 21 01:17:43 <zmatt> if you ask for a reading, you obviously want a reading, including if that reading is zero
Jun 21 01:18:04 <MattB0ne> well I am expecing zero
Jun 21 01:18:08 <MattB0ne> but that is not what I get
Jun 21 01:18:12 <set_> lbs?
Jun 21 01:18:20 <zmatt> okay, did you calibrate it correctly?
Jun 21 01:18:37 <MattB0ne> well this is before even calibrating
Jun 21 01:18:41 <zmatt> also, a reading of zero is not the same as "no reading"
Jun 21 01:18:59 <zmatt> right, so that means the numbers probably mean very little
Jun 21 01:19:12 <set_> So far!
Jun 21 01:19:40 <zmatt> calibration involves both setting a zero-point and measuring a known weight
Jun 21 01:20:06 <set_> I know it has memory, right? So, if you place something on the load cell at some point, it may remember by way of a section of memory.
Jun 21 01:20:09 <zmatt> if the zero-point isn't calibrated correctly, you won't get 0 when there's nothing on the scale
Jun 21 01:20:19 <zmatt> yes calibration is stored persistently
Jun 21 01:20:20 <MattB0ne> right and when I do the calibration
Jun 21 01:20:28 <set_> Okay.
Jun 21 01:20:31 <MattB0ne> I get the behavior I described above
Jun 21 01:20:49 <set_> So, there should be a way to remove the memory.
Jun 21 01:20:54 <zmatt> MattB0ne: you haven't really described any behaviour, at least not in a way that's intelligible
Jun 21 01:20:56 <MattB0ne> internally consistent 50 = 1, 100 = 2
Jun 21 01:21:06 <zmatt> okay, well then you probably did osmething wrong
Jun 21 01:21:12 <MattB0ne> I know struggling
Jun 21 01:21:18 <MattB0ne> since it is not obivious
Jun 21 01:21:24 <MattB0ne> to me at least
Jun 21 01:21:33 <MattB0ne> trying to get symetric as you say
Jun 21 01:21:52 <MattB0ne> but I lack an axis of symetry =)
Jun 21 01:22:29 <zmatt> the manual says your calibration weight should become "5000"... e.g. if you use a 500g weight for calibration then its readings will be in units of 0.1g
Jun 21 01:22:29 <set_> So, this load cell needs to be accounting for weight and the weight displayed is there w/out any weight.
Jun 21 01:23:15 <zmatt> so I'm not sure why you're getting such small values
Jun 21 01:24:27 <set_> Show the source and show the load cell if you dare...
Jun 21 01:24:42 <set_> or are you two making source in C/C++?
Jun 21 01:25:03 <MattB0ne> I am using the software package since this is more of a hardware issue
Jun 21 01:25:17 <MattB0ne> it basically a gui for sending commands though
Jun 21 01:25:29 <MattB0ne> it does have a terminal for commands
Jun 21 01:25:35 <set_> Oh. Okay. So, it is not open source?
Jun 21 01:25:37 <MattB0ne> let me try again maybe my units are wrong
Jun 21 01:25:45 <MattB0ne> this span thing
Jun 21 01:25:49 <zmatt> ah never mind, what I just said was just an example they give
Jun 21 01:26:02 <zmatt> you can configure a different span for the output values
Jun 21 01:26:36 <set_> So, time plays a role in this too?
Jun 21 01:26:42 <zmatt> no?
Jun 21 01:26:49 <set_> span == time, no?
Jun 21 01:26:52 <zmatt> no
Jun 21 01:26:57 <set_> Oh.
Jun 21 01:27:03 <MattB0ne> I think so
Jun 21 01:27:11 <MattB0ne> maybe that is what I am messing up
Jun 21 01:27:12 <zmatt> a time span is a span of time
Jun 21 01:27:20 <set_> Right.
Jun 21 01:27:26 <zmatt> I'm not talking about time
Jun 21 01:27:29 <set_> and span in this case is what?
Jun 21 01:27:35 <zmatt> range of output values
Jun 21 01:27:38 <set_> Oh!
Jun 21 01:28:12 <set_> So, our span, range of output values, is needing a source set up?
Jun 21 01:28:27 <set_> Or does that go back to the calibration part?
Jun 21 01:29:24 <set_> Oh and just for reference, that damn BBBlue and the ArduPilot stuff beat me after one lift off. The damn thing only flips now. Blah.
Jun 21 01:29:51 <set_> I am going to use ArduRover instead and see if I can get that working. I am not a flight expert.
Jun 21 01:30:19 <zmatt> anyway, I'm off to bed
Jun 21 01:30:24 <set_> No!
Jun 21 01:30:55 <set_> Fine.
Jun 21 01:32:09 <set_> MattB0ne: If you get ideas, let me know. I will brb. I need to handle something.
Jun 21 01:40:00 <set_> I know I really do not know what you two are doing but it sounds interesting. Godspeed!
Jun 21 01:43:54 <MattB0ne> i will figure it out
Jun 21 01:43:56 <MattB0ne> I am close
Jun 21 01:44:02 <set_> Okay!
Jun 21 02:30:33 <set_> That BBGG sold out quickly. Sheesh.
Jun 21 02:53:26 <set_> I have been reading /i2c/smbus-protocol from the kernel docs to figure out this darn ServoCape. Has anyone successfully made motion w/ this Cape thus far?
**** ENDING LOGGING AT Sun Jun 21 02:59:58 2020