#robotics | Logs for 2016-08-14

Back
[00:15:20] <z64555> you... soldered the terminals of the lipo together?
[00:16:15] <rue_shop2> er?
[00:16:57] <rue_shop2> :)
[00:18:07] <theBear> it's ok, i'm a qualified ninja coloured belt soldering master
[00:18:32] <z64555> Ok. I guess you don't intend to recharge it, then
[00:18:53] <theBear> rue_shop2, the pile of heavy metal and dolphin killers is gettin too big, and you know as well as anyone how much more wallop a pair of little modern lipo's contains than a shitty square 9v
[00:18:58] <theBear> 9v batt clip
[00:19:26] <theBear> the meter hasnt' been touched apart from xssnipping a little bit of plastic stops that used to fill the space so the 9v didn't bounce around
[00:19:58] <theBear> tho you get 1000points if you pick the previous repair/upgrade(mods are for people with too much spare time :] ) inside the meter
[00:22:44] <z64555> soldering the terminals together gives you 0 balancing options of each cell, though
[00:25:12] <theBear> aww c'mon, you can see the balance "connection" as well as i can... it's either end of the diagonal wire <grin> tho shockingly (to me,) after more like 18 months than 6 months of having their first trial-run in the cheapy meter that lives propped near the scope these days (didn't have a batt handy, but it is small and i couldn't make them fit with the batt-lid on <grin>) from a single charge, thoroughly unmonitored, and ignored, they were WELL
[00:25:12] <theBear> within 2 matching decimals of each other just sitting as in these pics, same soldering/wires even
[00:25:55] <z64555> the cells. not the packs.
[00:26:16] <theBear> but from saved-from-landfill/tip spares massive pile (also free pile) that i already got around, to usefull free meter batts in a decade i don't seem to have 9v's around again (seems to alternate with decade give or take :] ), that's a damned good jump i think
[00:26:23] <theBear> oh, they fone batts, only one cell
[00:26:34] <z64555> ah, ok
[00:26:56] <z64555> wonder why there's several terminals then
[00:27:22] <theBear> i know a very few rare ones jam in 2 or more cells for some stupid reason or other, but it's VERY rare, and i had a LOT of these around over the years for some reason (not nearly enough dead ancient samsung fones to explain it) and seen their insides, nice simple, single cell, single chip and minimal support style protection pcb
[00:27:55] <z64555> maybe it was a standardized connector
[00:28:15] <theBear> i should really know that, but i can't quite remember if (old)samsung did just a temp sense direct to the pins like old nicad packs (drills for example) or had proper i2c/similar capable gasgauge chips in the protection that really talked
[00:28:38] <theBear> i can't think of EVER seeing a mobile phone with only 2 connections to a single cell/batt package
[00:28:40] <z64555> gotcha
[00:29:25] <theBear> but yeah, generally laptops this century and all post analog mobiles, 3rd and maybe 4th pins on batts are that kinda thing, almost alawys 1 of the 2 if you expand i2c to include 1wire and other similar serial/bussey things
[02:27:06] <Jak_o_Shadows> theBear, what has adding a LiPo done?
[02:37:44] <z64555> lets him use some cellphone batteries that otherwise are collecting dust?
[02:49:14] <theBear> Jak_o_Shadows, got a lipo off the pile, and early results suggest increased life up from the 9v crappy old style rectangle batt by unbelievable amounts... kinda thing you find yourself looking at the meter and wondering how many chunks of 6months it had been running on that single charge and pair of old junkpile batteries
[02:50:22] <theBear> there still more than a few batts in the pile without fones or much apparent use/aging in em, even ones that sat in the pile uncared about for several years in many cases, tho some need a little tickle to get up above min-voltage cutout when yer first resurrect em
[03:28:36] <Jak_o_Shadows> ah, ok
[03:28:49] <Jak_o_Shadows> So far, i haven't had to replace battery in DMM
[03:28:57] <Jak_o_Shadows> I just moved to my next cheap DMM :D
[04:32:25] <theBear> heh
[09:09:12] <LiohAu> anybody can explain me why in this picture : https://cdn.sparkfun.com/assets/learn_tutorials/1/4/7/LogicLevelFixed.png the low voltage comes from the connected board, while in this one : https://cdn.sparkfun.com/assets/9/b/c/b/4/5266e578757b7f484d8b456f.png it comes from the arduino ?
[09:10:40] <LiohAu> SpeedEvil: I'm sure you know ^^
[09:11:18] <SpeedEvil> yeah - I'm not doing that
[09:11:48] <LiohAu> you mean you don't do it like this?
[09:11:50] <SpeedEvil> That requires me to work out where the stupid wires go, to look up all of teh involved boards pinouts and specs
[09:12:05] <SpeedEvil> No, draw a circuit diagram.
[09:12:41] <SpeedEvil> you might use the above to go from circuit diagram to implementation, but the diagram is how you understand it
[09:12:53] <SpeedEvil> Or explain it to others.
[09:13:30] <LiohAu> sorry I should have explained that it is a logic level converter
[09:13:44] <LiohAu> this kind of llc : https://learn.sparkfun.com/tutorials/bi-directional-logic-level-converter-hookup-guide
[09:14:49] <LiohAu> from what they wrote, converting 5v to 3.3v voltages is a common issue, and their board solves this
[09:15:55] <LiohAu> so as expected there's one side of the board for high voltage and the other 1 one for low voltage, and on each side there are 2 pins dedicated to reference voltage and ground
[09:17:44] <LiohAu> the thing I don't understand, is why in some cases the two reference voltage low/high are provided by a unique board while in other cases the 2 references voltages are provided by the 2 boards being connected through the LLC
[09:19:03] <LiohAu> I understood the reason while I was writing.
[09:19:27] <LiohAu> It's because some boards can provide the reference voltage because they also have their own power source
[09:19:32] <LiohAu> and some other don't
[09:19:44] <LiohAu> that was easy :(
[13:48:27] <rue_shop4> theBear, oh click, those meters run on 3V
[13:48:31] <rue_shop4> or 6
[13:48:39] <rue_shop4> 3.7?
[13:49:04] <rue_shop4> The_Jester, I'll try casting those extruder gears in aluminum today
[13:49:29] <rue_shop4> The_Jester, did the pizza destroy your sleep?
[13:56:20] <Tom_itx> rue_shop4, how's your casting success been?
[14:12:41] <rue_shop4> good so far
[19:07:32] <rue_shop4> hmm, I dont know what I got done today
[19:07:36] <rue_shop4> cast some more aluminum
[19:22:23] <rue_shop4> mowed part of the lawn
[19:22:52] <rue_shop4> damnit its not saturday
[19:29:55] <Tom_itx> shop for food?
[20:35:24] <rue_shop4> YES!
[20:35:41] <rue_shop4> I got the TLC5940 working, without the microcontroller having to manually operate the clock lines
[20:35:59] <rue_shop4> (I used a 4060 to generate the clock and blanking signal)
[20:36:16] <Tom_itx> good stuff
[20:36:39] <rue_shop4> every 4096 clock cycles you have to send a reset for the pwm counter
[20:36:46] <rue_shop4> without it the counter does NOT just rollover
[20:36:50] <rue_shop4> !?!?!?!?!??!!!!?
[20:37:14] <rue_shop4> so, whatever, its an extra chip in my project
[20:40:06] <rue_shop4> yaaay, its not being anal about synchonization
[20:40:58] <rue_shop4> OH NO! I PULLED THE POWER OUT OF MY PROJECT AND IT STOPPED WORKING! WHAT DO i DO WHAT DO i DO!!!!!
[20:45:46] <z64555> ?
[20:46:16] <z64555> how the hell did you pull power?
[20:46:33] <z64555> are you Dr. Manhattan?
[20:48:17] <rue_shop4> It happened when I disconnected the programmer!
[20:51:16] <z64555> lol.
[20:54:17] <Snert> I put 2 pieces of bread in the toaster and pushed the handle down.
[20:54:28] <Snert> Out popped toast! What's wrong?
[20:55:05] <rue_shop4> huh, the digital scope has issues measuring duty on pulses more than 80% and less than 10%, dont get that...
[20:55:22] <rue_shop4> Snert, oh got!!! I had the SAME THING HAPPEN
[20:55:32] <rue_shop4> I WANT TO KNOW WHERE MY BREAD WENT!!!!
[20:55:41] <orlock> Replace it with some quality Tektronix gear :P
[20:55:51] <rue_shop4> AND EVERY THURSDAY SOMEONE STEALS THE GARBAGE FROM MY GARBAGE CAN!!!!
[20:55:57] <Snert> rumor has it that bagels act much the same way when subjected to this test.
[20:56:19] <rue_shop4> why dont they TEST these things before they put them to MARKET!!!!!
[20:56:27] <rue_shop4> (I do?)
[20:56:58] <rue_shop4> I have the 5940 outputting 600Hz pwm all on its own
[20:57:00] <rue_shop4> this is nice
[20:57:39] <rue_shop4> the chip, of course is screaming bloody murder cause its got led faulires on all 16 channels
[21:00:15] <rue_shop4> oh confusion
[21:00:33] <rue_shop4> the channels get different ... wtf..
[21:00:50] <rue_shop4> all channels shoudl get the same value...
[21:02:56] <z64555> led failures? what's going on?
[21:03:59] <rue_shop4> its a 16 channel, 12 bit pwm led driver
[21:04:26] <rue_shop4> this is odd tho, I'm sending the same pwm value 16 times, once for each channel
[21:04:44] <rue_shop4> but the channels are getting the values at... different... rates...
[21:07:03] <rue_shop4> oh wait
[21:07:08] <rue_shop4> for( temp = 4096; temp != 0; temp >>= 1) {
[21:07:08] <rue_shop4> if ( (bits & temp) != 0 ) { SendOne();
[21:07:08] <rue_shop4> } else { SendZero();
[21:07:08] <rue_shop4> }
[21:07:08] <rue_shop4> }
[21:07:15] <rue_shop4> I'm supposed to sending 12 bits
[21:08:32] <Tom_itx> no kibbles?
[21:08:55] <rue_shop4> its sunday
[21:09:38] <rue_shop4> wtf, thats msb first
[21:09:53] <rue_shop4> oh, yea, thats right
[21:20:08] <z64555> most significant bit is always first :P
[21:43:54] <rue_shop4> so, I have it ramping the brightness of all the channels at once
[21:44:06] <rue_shop4> each channel is sent the same value of the ramp for that cycle
[21:44:21] <rue_shop4> but the frist 4 leds ramp as different speeds
[21:44:56] <rue_shop4> unless its a digital scope artifact
[21:47:37] <rue_shop4> k, wait, this might be an avr C quirk
[21:53:14] <rue_shop4> yea, from channel 1, the ramp speed doubles on every channel
[21:54:32] <rue_shop4> 192 bits split over 16 registers
[23:27:00] <rue_shop4> ok I worked soemthing out
[23:27:33] <rue_shop4> every 4096 cycles, you have to send a BLANK signal to zero the pwm counter,
[23:28:01] <rue_shop4> RIGHT AFTER that BLANK pulse, it overwrites the serial register values with the system status
[23:28:21] <rue_shop4> so, you HAVE to lock the data update to the pwm counter
[23:28:49] <rue_shop4> otherwise your pwm data is overwritten with status info and sent to the pwm value registers
[23:29:28] <rue_shop4> so, I'm targeting 300Hz update, I can use the BLANK signal as an interrupt to the controller, and have it send the pwm values then
[23:32:22] <rue_shop4> no I'm wrong
[23:34:41] <rue_shop4> "All OUTn with grayscale values equal to counter values are switched off"
[23:35:13] <rue_shop4> so, if the value changed in such a way to skip over the value of the counter, it wouldn't trip properly