**** BEGIN LOGGING AT Thu Dec 27 02:59:59 2018 Dec 27 03:31:48 killer SD cards what will they make next? Dec 27 08:35:54 Hello Dec 27 08:36:02 Good Morning Dec 27 08:36:46 Please send to me your representative or Branch Detail in China,Hong Kong and Germany Dec 27 08:37:03 i from Germany Dec 27 08:37:16 and your Products intrested for me Dec 27 08:37:48 we have some business and Customer in worldwide and good Relationship with them Dec 27 08:38:08 please send to email address:sanaraghi@outlook.com Dec 27 21:53:34 is anyone using rc_test_servos right now from Yoder's PRU Cookbook ideas for the BBBlue? Dec 27 21:53:48 I am trying to make this servo work but have come up empty. Dec 27 21:57:58 Supposedly, the librobotcontrol software is already typed up and done. About the BBBlue, the PRU Cookbook author states, "It should just work." Dec 27 21:57:59 ... Dec 27 21:58:11 He was talking about w/ the BBBlue and the set up/config. Dec 27 22:05:46 https://pastebin.com/qTgJimkj shows my error for the lack of rc_adc_init. Dec 27 22:15:30 set_: what does rc_test_drivers say? Dec 27 22:17:24 error: ADC iio driver not loaded. Dec 27 22:17:31 same for PRU. Dec 27 22:17:51 rproc. Dec 27 22:19:02 I am going to reboot. I just put it on blinky again. Dec 27 22:24:48 blinky is not working. I have no red LED flashing at all. Dec 27 22:29:29 Hold on. Dec 27 22:30:17 Oh well. Dec 27 22:30:40 bbl...I need to compile w/ make or something. I am unware of what ave. to take. Brb. Dec 27 22:41:34 well, I performed a make install and make. Notta. My issues are still in front of me. Dec 27 22:54:26 I am missing a .h files for a current program. I will search for it. Dec 27 22:55:08 Humpelst1lzchen: I am having errors still w/ the pru_rproc and adc iio. Dec 27 22:59:05 set_: did you change anything on the default image regarding the hardware setup? e.g. changing kernel, bootloader, devicetree... Dec 27 22:59:14 Not yet. Dec 27 22:59:42 set_: what image are you running? Dec 27 23:00:05 Linux beaglebone 4.14.71-ti-r80 Dec 27 23:00:31 BeagleBoard.org Debian Image 2018-10-07 Dec 27 23:00:59 rc_version works so far. Dec 27 23:01:32 1.0.4 Dec 27 23:04:12 I know the software refuses to run unless battery power is ported to the jack on the BBBlue. Dec 27 23:04:35 I just figured adc iio and pru_rproc would show signs of life w/ the cmd you gave me. Dec 27 23:04:35 set_: you sure this is an unmodified image? Afaik it worked for me on the vanilla image. Dec 27 23:04:43 Yes. Dec 27 23:04:46 I am positive. Dec 27 23:04:56 set_: maybe try updating with apt-get Dec 27 23:05:00 Okay. Dec 27 23:06:49 those two drivers are not loaded. Dec 27 23:06:52 Still. Dec 27 23:10:37 there is no file called rc_adc_init. I think my system keeps looking for this file. Dec 27 23:10:45 to run servos. Dec 27 23:11:21 sorry. no = a Dec 27 23:12:27 I will go get the battery. Dec 27 23:14:22 Now, the battery must be connected to run just one servo motor, right? So, I can add the battery and USB? Dec 27 23:15:24 scratch that. Dec 27 23:15:39 I attached the battery and USB. All is well. Dec 27 23:16:49 Same issue. Dec 27 23:26:48 ... Dec 27 23:27:25 Humpelst1lzchen: Should I change the dpkg-reconfigure section of librobotcontrol to blinky or another option? Dec 27 23:27:43 set_: that should be don't care Dec 27 23:28:14 Oh. You do not care or am I missing something? Dec 27 23:29:29 set_: It should not matter if the leds blinks or not Dec 27 23:29:49 Oh. Okay. I chose existing again. Dec 27 23:31:22 set_: are you booting from sd card or eMMC ? Dec 27 23:32:05 SD Dec 27 23:32:44 bootloader? Dec 27 23:32:45 do you care about the current contents of eMMC? if not, erase it using: sudo blkdiscard /dev/mmcblk1 and reboot Dec 27 23:32:48 No. Dec 27 23:32:55 Okay. Please hold. Dec 27 23:33:59 yeah, some googling shows these errors indicate DT problems, and inexplicable DT problems on a recent image in fresh state almost certainly implies you're getting messed over by the bootloader stored in eMMC Dec 27 23:34:20 I cannot believe that is what I forgot to do. Dec 27 23:34:26 Sorry Humpelst1lzchen. Dec 27 23:35:23 Okay. That did it. Dec 27 23:35:28 I have a battery issue now. Dec 27 23:35:36 No issue. I need to charge it. Dec 27 23:35:40 * Humpelst1lzchen did not thought of that... Anyway why does it need to change that often? Dec 27 23:36:11 I usually update the eMMC and then boot from SD. Dec 27 23:36:32 the root cause is the transition to u-boot overlays Dec 27 23:36:42 yeah updating the eMMC works too Dec 27 23:36:50 or bypassing it by powering on with the S2 button held down Dec 27 23:37:06 Right. I rarely use the S2 button. Dec 27 23:37:25 Staying up to date is not easy. Dec 27 23:37:32 it's not very convenient, but it's the only option that's non-destructive to the eMMC Dec 27 23:37:43 Oh. Dec 27 23:37:50 as in, to the data on eMMC Dec 27 23:37:51 sorry Dec 27 23:37:54 bad choice of words Dec 27 23:38:21 I got you, man. Heh? I think the charger is broken. Off to test the charger. Dec 27 23:38:38 mo' funny, mo' problems. Dec 27 23:39:29 hey zmatt: Can I use the 12v battery connector to run motors, i.e. Lead Acid? Dec 27 23:39:46 instead of the LiPo? Dec 27 23:39:55 for the BBBlue? Dec 27 23:40:13 and if you ever find yourself needing the S2 button a lot and get tired of pressing that tiny fiddly button, you can instead connect a resistor (about 1K to 10K is fine) between P8.43 and ground (this is equivalent to pressing the S2 button) Dec 27 23:40:30 sounds like a bad idea Dec 27 23:40:34 I highly doubt it Dec 27 23:40:43 set_: yes, motors just don't run on USB power for obvious reason Dec 27 23:41:03 he knows that, he's asking if you can use lead-acid instead of lipo Dec 27 23:41:16 But in the barrel jack and not the LiPo section? Dec 27 23:41:25 section = connector. Sorry. Dec 27 23:41:25 oh like that Dec 27 23:41:29 Yes. Dec 27 23:41:56 So, I am assuming yes. That is good news. I have a new connector to try out. Dec 27 23:42:10 This is working out just nicely. Dec 27 23:43:15 any power source that's in the right voltage range (I forgot what the actual voltage range is supported by the blue's barrel jack) and doesn't have too high internal resistance or other weird dynamic behaviours should be fine Dec 27 23:44:39 12v Dec 27 23:44:50 BBBlue has a 12v barrel jack. Dec 27 23:45:26 Okay. I am off to test. Should I reply once things are geared up and moving? Dec 27 23:45:28 yeah but it doesn't require *exactly* 12v Dec 27 23:45:33 Oh. Dec 27 23:45:39 9-18V according to the fancy blue image Dec 27 23:45:40 which is good, since a battery's voltage isn't stable Dec 27 23:45:47 Right. Dec 27 23:46:03 That is smart. I thought it was from 7 - 15 for some reason. Dec 27 23:46:18 9 - 18, good. Dec 27 23:47:37 that image: https://github.com/beagleboard/beaglebone-blue/blob/master/docs/BeagleBone_Blue_balloons.pdf Dec 27 23:48:33 balloons? Oh...I remember someone used Corel to make those "balloons." Dec 27 23:49:35 Yep. Dec 27 23:49:40 9 - 18v. Dec 27 23:49:50 12v battery here I come. Dec 27 23:53:54 the lipo charger's datasheet input voltage range is 4.5V-12V if you're using one-cell lipo or 8.75-12V if you're using two-cell lipo (which the blue is) Dec 27 23:53:58 sorry, -18V Dec 27 23:54:27 of course going lower than the minimum specified just means you can't charge the lipo, which doesn't matter if you're not using one Dec 27 23:54:38 got it. Dec 27 23:55:35 so the actual min voltage will be determined by the other user of the input power: the main 5V regulator Dec 27 23:57:03 Either I am on servo 1 or servo 8. I made the BBBlue understand to turn the servo w/ that rc_servo_send_pulse_normalized function. Dec 27 23:57:07 ... Dec 27 23:57:16 The servo has not turned yet but the software works now. Dec 27 23:58:40 I honestly can't tell from the ap1509 datasheet what its min input voltage is Dec 27 23:59:10 The servo is on Servo1. The software told me that 6v servo power rail is on. Dec 27 23:59:12 anyway, yeah you should be able to run it on a lead-acid battery Dec 27 23:59:17 I guess it is. Dec 27 23:59:30 Okay. I figured this should work. Thank you. Dec 27 23:59:39 the 6V servo regulator is powered from the lipo battery Dec 27 23:59:49 Oh. Dec 27 23:59:56 oh yeah, if you don't have a lipo battery you're going to run into some limitations Dec 28 00:00:09 Okay. Dec 28 00:00:18 the H-bridge motor drivers won't work and the 6V supply output won't work Dec 28 00:00:31 Is there a work around for the servo rail? Dec 28 00:00:50 So, no motor drivers and no servo rail. Yikes! Dec 28 00:01:05 That is okay. I will charge this battery one day. Dec 28 00:01:13 ? Dec 28 00:01:43 I have a 12v Lead Acid but I need to charge my 2s LiPo battery to make those work. Dec 28 00:02:04 eh? Dec 28 00:02:09 Nothing. Dec 28 00:02:14 also the blue should be able to charge the lipo Dec 28 00:02:19 Oh. Dec 28 00:02:20 ! Dec 28 00:03:07 you didn't realize the beaglebone blue has a built-in lipo charger? Dec 28 00:03:13 it is charging now. Dec 28 00:03:18 Yea. I forgot. Dec 28 00:05:13 zmatt: Do you know what the BBBlue does when the LiPo is done charging? Dec 28 00:05:27 what do you mean "does" ? Dec 28 00:05:49 Does the BBBlue stop blinking or stop the LEDs? Dec 28 00:06:21 The LEDs show all red? Dec 28 00:07:44 there's a green led to indicate the battery is charging Dec 28 00:08:01 I have a green on chrg. Dec 28 00:08:04 Right. Dec 28 00:08:10 when it's done charging (or more generally, when it stops charging for any reason) the led turns off Dec 28 00:08:45 oh. I figured I can see the difference in completion of the charge w/ the LEDs turning red at each interval. Dec 28 00:09:10 There are supposedly four intervals, i.e. 25, 50, 75, 100. Dec 28 00:10:31 yeah but when the last led turns on, it probably just means something like "close to 100%" or even "closer to 100% than to 75%" Dec 28 00:11:38 Okay. Dec 28 00:11:50 I had just noticed the LEDs on it. Dec 28 00:12:59 those leds are under software control and presumably guesses the battery charge based on voltage (since I don't see any logic for actually tracking the state of charge of the battery), which is known to be very inaccurate Dec 28 00:13:17 aw Dec 28 00:40:57 rcn-ee[m]: your 4.19 kernels (both -ti and -bone) are missing CONFIG_UIO_PRUSS=m Dec 28 00:50:00 charger is up and running. BBBlue is on the way to freedom. Dec 28 01:04:17 rcn-ee[m]: ah I see, neither uio-pruss nor remoteproc-pru has been forward-ported to 4.19 yet Dec 28 01:11:23 Okay. How can I use a cmd to set the servo in use w/ the LiPo battery plugged in? Dec 28 01:11:24 ... Dec 28 01:11:28 I tried this... Dec 28 01:12:08 sudo rc_test_servos -f 10 -c 1 -p 1.1 Dec 28 01:12:37 Oh. I probably need to subtract (s) in servo(s). Dec 28 01:12:50 Nope. Dec 28 01:14:03 The software seems to work but servo motion. Dec 28 01:14:33 your servo specifies a 10 Hz signal should be used? Dec 28 01:14:49 Yep. Dec 28 01:15:03 I tried 55 Hz, too. Dec 28 01:15:26 have you tried using sweep? Dec 28 01:15:34 Not yet. Dec 28 01:15:39 (on all channels, just to be sure) Dec 28 01:16:06 Oh. Okay. I will test it. Dec 28 01:16:10 e.g. rc_test_servos -s 1 Dec 28 01:16:20 Aw! I will test it. brb Dec 28 01:16:22 -f 10 -s 1 I mean Dec 28 01:16:28 if the servo wants 10 Hz Dec 28 01:16:28 Got it. Dec 28 01:16:40 please hold. Dec 28 01:18:03 The software read back that it should make a task completed but the servo did not turn. Dec 28 01:18:38 check connections? check with multimeter if the supply voltage to the servo is okay? Dec 28 01:18:52 Alright. Please hold. Dec 28 01:22:20 I tested volts on the servo rail. It seemed to fluctuate around 6v (over and under) a percent of xxxxx. Dec 28 01:22:54 At least on servo2. Dec 28 01:23:42 Just to make sure, GND on the BBBlue for the Servo Rail is near the USB port and away from the dc motor inputs, correct? Dec 28 01:23:43 they all share the same 6v rail Dec 28 01:23:47 Oh. Dec 28 01:23:48 Okay. Dec 28 01:23:53 uhh what? Dec 28 01:23:58 * zmatt checks schematic Dec 28 01:24:03 Wait. I can check. Dec 28 01:25:10 schematic says for each servo there are three pins: ground, power (6v), and signal Dec 28 01:25:31 Okay. Dec 28 01:25:40 I see that. Dec 28 01:25:47 ohh, you mean the pin position on the connector? Dec 28 01:26:01 I was confused, I thought you meant you were pulling ground from some random place on the pcb Dec 28 01:26:18 Yes. Dec 28 01:26:34 Not pulling GND from some random pin/connector. Dec 28 01:26:40 I can't tell from the schematic what the pinout looks like. isn't it marked on the pcb? or documented on the wiki? Dec 28 01:26:44 I know. Dec 28 01:26:55 Hold. I will look. Dec 28 01:27:30 PCB...no way to tell. Off to look at the Wiki. Dec 28 01:27:39 yeah it's marked on the pcb, in a slightly confusing way ("-", "+", and a pulse-shape) Dec 28 01:28:54 https://cdn.sparkfun.com//assets/parts/1/3/2/1/2/14920_-_358-BBBLUE.jpg in this orientation, the three pins from left to right are: ground, power, signal Dec 28 01:30:05 Crud. Dec 28 01:30:11 Let me poweroff. Dec 28 01:30:18 I probably ruined that pin. Dec 28 01:31:30 no, fortunately for you the servo outputs are protected against short-circuits Dec 28 01:32:34 I actually tried this yesterday after making arduCopter ready on my BBBlue. The board would not boot. I later found out that their software, the .dtb file insertion on a specific github page, makes the BBBlue not operate. Dec 28 01:32:50 ... Dec 28 01:33:03 It had nothing to do w/ the servo. I figured that out. Dec 28 01:33:05 sheesh. Dec 28 01:33:46 Yep. It works just fine. Dec 28 01:34:06 I put it on pinout2. Dec 28 01:34:17 I should try the pinout1 again. Dec 28 01:34:37 -s for sweep is nifty. Dec 28 01:36:28 Now...machines! Dec 28 01:43:28 so, zmatt: Just to make sure, the servo rail WILL NOT work if I plug in a Lead Acid, 12v battery in the barrel jack. Right? Dec 28 01:45:02 servo rail will not work if no lipo battery is present, regardless of whether a 12v supply is provided Dec 28 01:46:11 (the board doesn't know or care whether you get that 12v from an ac adapter or a lead acid battery) Dec 28 01:49:01 Oh. Okay. I got it. Dec 28 01:49:03 ... Dec 28 01:50:03 So, a lightweight battery supply could ultimately power the LiPo b/c of a charger on the BBBlue too? Dec 28 01:50:26 I don't understand the question Dec 28 01:50:55 I guess I am just having trouble understanding how the charger works for now. No issue. I just thought, oh. Dec 28 01:50:56 ... Dec 28 01:51:34 The barrel jack via battery or the barrel jack via adapter can supply a charge to the LiPo once it is out of power? Dec 28 01:51:35 12v (or rather 9v-18v) via barrel jack powers the lipo charger Dec 28 01:51:42 Got it. Dec 28 01:52:06 Sorry for the confusion. Dec 28 01:58:52 and either 12v or the lipo can power the main 5v regulator, which indirectly powers nearly everything on the board. if both 12v and lipo are present, 12v is preferred for powering the board (but it'll automatically switch to, or supplement from, the lipo if the 12v disappears or dips) Dec 28 02:02:40 Oh. Dec 28 02:03:03 I think, this was my original questioning, the 12v should feed the LiPo. Dec 28 02:03:23 via the lipo charger ic yes Dec 28 02:03:34 but that's unrelated to powering the rest of the board Dec 28 02:04:09 oh! Dec 28 02:04:11 hm Dec 28 02:04:15 no never mind Dec 28 02:04:21 I got it now. So, everything will take presedence of 12v barrel jack batteries over LiPo. Dec 28 02:04:21 ? Dec 28 02:05:02 ignore me, I had a silly thought, and then realized it was a really silly thought Dec 28 02:05:10 Okay. No issue. **** BEGIN LOGGING AT Fri Dec 28 02:18:13 2018 **** BEGIN LOGGING AT Fri Dec 28 02:29:10 2018 Dec 28 02:46:44 set_: https://photos.app.goo.gl/6SyBtF3oUzcwn5G98 Dec 28 02:47:32 set_: this is the (surprisingly complicated) block diagram of the 5V-and-higher parts of the beaglebone blue's power supply Dec 28 02:55:04 something to be careful of: the PMIC only controls the parts I've drawn in blue, i.e. when you shut down only those parts will actually be unpowered. the rest of the diagram only depends on external power (12V or lipo) and always remains powered Dec 28 02:59:05 (e.g. if you actually make the mistake of using pin 5 of the GSM header to power a gsm module, then if you shut down the board the gsm module would remain on and drive its serial data into the processor, which could easily end up being damaged as a result) **** ENDING LOGGING AT Fri Dec 28 02:59:58 2018