**** BEGIN LOGGING AT Thu Dec 07 03:00:01 2017
Dec 07 09:57:07 <Charlestx> I try to update my BBG, the sd card updated but as I try to update to eMMC, there's problem.
Dec 07 09:58:06 <Charlestx> I can not link to 192.168.7.2 without sd card.
Dec 07 10:00:44 <Charlestx> with sd card on BBG, I try to putty 192.168.7.2 with root as user and <enter> as psw but Access Deny
Dec 07 10:01:17 <Charlestx> Can anyone help?
Dec 07 10:01:35 <tbr> if you have an anywhere near up to date image, then loggin in as root via ssh should *not* be allowed by default
Dec 07 10:02:41 <Charlestx> Where can i find the username and psw for that?
Dec 07 10:03:51 <tbr> if it's a default installation then it should be something like "debian" and "tmppwd"
Dec 07 10:05:35 <Charlestx> it is Debian 9.2 2017-10-10 4GB IoT
Dec 07 10:10:15 <Charlestx> still Access denied
Dec 07 10:10:59 <tbr> no idea, you could always just reflash the emmc
Dec 07 10:12:05 <Charlestx> THX
Dec 07 13:34:56 <Mani__> Hello, We are using Beagle Bone Black for an IoT project, We are looking for a cape with WiFi and BLE
Dec 07 13:35:15 <Mani__> Do you have any recommendation
Dec 07 13:40:49 <tbr> I guess at least for wifi I'd go with USB
Dec 07 13:41:33 <tbr> also there's a beaglebone black wireless nowadays, I think.
Dec 07 13:42:58 <Mani__> We are using USB to connect with a Zigbee module
Dec 07 13:43:38 <tbr> then use an USB hub
Dec 07 13:43:49 <Mani__> We need the Ethernet connection since our customer will not allow us to use their WiFi
Dec 07 13:45:58 <Mani__> In our requirement, I need to use USB(Zibbee) ethernet for network connectivity and trying to use WiFi for setup
Dec 07 18:32:11 <LifeIsABone> Hi, I am trying to get my wifi up on a BBG
Dec 07 18:35:16 <LifeIsABone> I have an edimax dongle, which i saw was compatible on the wiki page. I am getting an wpa_supplicant daemon failed to start error when I try and bring up the wireless adapter
Dec 07 18:36:52 <carbon-cabron>  hello, how can the 4th encoder input on the BB Blue be connected on a non eQEP pin?
Dec 07 18:37:05 <carbon-cabron>  i mean, the two pins that are meant to be the 4th quadrature decoder pins are not in any of the 7 modes related to the eQEP module
Dec 07 18:37:05 <carbon-cabron>  pin ball U13 on the BeagleBone Blue named 'PRU_E_B' has 7 modes
Dec 07 18:37:05 <carbon-cabron>  gpmc_ad15, lcd_data16, mmc1_dat7, mmc2_dat3, eQEP2_strobe, pr1_ecap0_ecap_capin_apwm_o, pr1_pru0_pru_r31_15, gpio1_15
Dec 07 18:37:05 <carbon-cabron>  which one should i use to be able to decode the encoder signal
Dec 07 18:38:00 <LifeIsABone> the journalctl is hard to read and is cut off but i get the message failed to initialized control....you may have another WPA_suppl ... left by an unclean ....
Dec 07 18:38:18 <carbon-cabron> the strawsn desigh robotics cape fails to read the position, does it mean i am only limited to 3 encoders
Dec 07 19:22:54 <zmatt> carbon-cabron: I'm pretty sure that one is meant to be decoded via pr
Dec 07 19:22:56 <zmatt> pru
Dec 07 19:24:00 <zmatt> since it's explicitly marked as quadrature decoder I'd assume the pru firmware to do so is included but I've never looked into it
Dec 07 19:24:19 <zmatt> (I don't have a blue and I'm not doing anything with robotics)
Dec 07 19:30:23 <carbon-cabron> no pru software
Dec 07 19:30:51 <carbon-cabron> and the modes i listed above are from the am3358 datasheet
Dec 07 19:31:21 <carbon-cabron> and for one pin of the 4th encoder input only
Dec 07 19:32:18 <carbon-cabron> looks like you I have to come up with my own design for the eQEP for the 4th encoder.
Dec 07 19:32:38 <carbon-cabron> not really nice to advertise 4 encoder inputs
Dec 07 19:33:02 <carbon-cabron> and have only 3 of them working with the recommended software
Dec 07 19:34:50 <zmatt> it would seem very strange to me it would be advertised as encoder input without software support for this... you may want to ask on the mailing list
Dec 07 19:36:19 <zmatt> "The PRU in the beagelbone blue is used to support 8 servo/ESC(s) and an additional encoder"
Dec 07 19:36:33 <carbon-cabron> well it seems obvious when u take a look at the connections and the pin/ball info in the datasheet
Dec 07 19:36:53 <zmatt> yes it is obvious to me is it designed to be decoded by PRU
Dec 07 19:37:19 <carbon-cabron> and checking the mode the pin gets w/ the device tree overlay
Dec 07 19:37:37 <carbon-cabron> doesnt make any sense
Dec 07 19:38:13 <carbon-cabron> ok
Dec 07 19:38:33 <carbon-cabron> that sounds good
Dec 07 19:39:08 <zmatt> as for why this firmware+driver isn't being automatically loaded in your case I don't know... I don't have a blue and don't really know anything about its firmware
Dec 07 19:43:09 <carbon-cabron> zmatt where did you read about 8servos/ESC
Dec 07 19:43:10 <carbon-cabron> ?
Dec 07 19:43:32 <carbon-cabron> ok i see it
Dec 07 19:43:36 <carbon-cabron> sry
Dec 07 20:23:55 <zmatt> LifeIsABone: you can use left-right arrows to scroll horizontally in the journalctl output, or add the --no-pager flag
Dec 07 20:33:41 <LifeIsABone> How does one fix ifup failing to up wlan0 but you can see wlan0 if you run iwconfig
Dec 07 20:34:03 <zmatt> ifup? you've removed connman ?
Dec 07 20:34:57 <zmatt> ifupdown is not used by default on the standard beaglebone images (I have no idea why it's even installed by default)
Dec 07 20:35:06 <zmatt> please don't send private messages
Dec 07 20:35:12 <carbon-cabron> zmatt
Dec 07 20:35:47 <carbon-cabron> there is indeed a pru software included in the Robotics Cape software package for the last 4th encoder
Dec 07 20:35:51 <carbon-cabron> thanks
Dec 07 20:36:00 <zmatt> you're welcome
Dec 07 20:36:20 <zmatt> anyway, gotto run to do some shopping, will be back soon
Dec 07 20:40:10 <LifeIsABone> I did not remove conman or at least I think I didn't. I just got BBG yesterday all I have managed so far is to boot from SD and have the file system span the disk.
Dec 07 20:41:52 <zmatt> then wifi is being managed by connman... anyway, really afk now
Dec 07 20:45:20 <LifeIsABone> OK
Dec 07 20:50:39 <LifeIsABone> i launched connmanctl and i can scan but cannot connect I get the following error - Method "Connect" with signature "" on interface "net.connman.Service" doesn't exist
Dec 07 20:51:03 <LifeIsABone> I am trying to connect to my cell phones hotspot for the time being.
Dec 07 21:23:06 <zmatt> I really don't know anything about connman, I don't use it myself (I use systemd-networkd)
Dec 07 22:05:31 <LifeIsABone> I managed to get it to work
Dec 07 22:05:37 <LifeIsABone>  Thanks for the help ZMatt
Dec 07 22:08:12 <w1jp> hi all, anyone know of an updated guide for macOS 12.13.1 hosting internet over USB on pocket beagle running latest debian iot image?
Dec 07 22:08:40 <w1jp> I can screen in fine, but cannot ping on the PB
Dec 08 01:10:05 <shiva> Hi :). I had connected both my motor and pump to a motor bridge cape (http://wiki.seeed.cc/Motor_Bridge_Cape_v1.0/) on the BBB. It suddenly stopped working. I verified that the motor and pump work when connected directly to the battery. What do you think is wrong? Thanks!!
Dec 08 01:10:52 <shiva> I2C bus 2 0x4B. i2cdetect -y -r 2 shows 4b.
Dec 08 01:14:08 <djlewis> diagnostics time. you may have blown the motor driver
Dec 08 01:16:19 <djlewis> @shiva your link was dead for me
Dec 08 01:17:21 <shiva> @djlewis Google motor bridge cape
Dec 08 01:18:07 <shiva> @djlewis OMG :(. How can I check if I blew the motor driver? (It is a cape in this case)
Dec 08 01:19:39 <djlewis> found it
Dec 08 01:21:03 <djlewis> a DC volt meter on the terminals where the motor connects should show varying level f you are sending variable level.
Dec 08 01:21:33 <djlewis> cant tell if there is a fuse on the board.
Dec 08 01:23:23 <shiva> 'Motor 2' outlets work with my script. 'Motor 3' and 'Motor 4' stopped working :(. I  switched the motor number and physical connections to check
Dec 08 01:23:51 <shiva> @djlewis Can you access http://wiki.seeed.cc/Motor_Bridge_Cape_v1.0/ ?
Dec 08 01:24:03 <djlewis> surely you checked the standby / working switch
Dec 08 01:25:40 <shiva> @djlewis It is in working mode
Dec 08 01:25:54 <djlewis> I had to ask
Dec 08 01:28:44 <shiva> Why did some outlets stop working suddenly? @djlewis
Dec 08 01:29:44 <djlewis> did Murphy walk into the room?  ;)
Dec 08 01:31:04 <djlewis> with some test equipment you can isolate whether it is a missing vbat or failed otherwise failed board.
Dec 08 01:31:14 <djlewis> a very simple circuit.
Dec 08 01:33:10 <djlewis> you are off to a good start having tested the motors already.
Dec 08 01:36:41 <djlewis> I am presently on a old 2010 Ubuntu 10.4 system I found in a closet. Not so compatible with the pdf schematic.
Dec 08 01:37:10 <djlewis> top of circuit missing.
Dec 08 01:37:21 <shiva> Oh
Dec 08 01:41:04 <djlewis> I see your board oes have a 3A fuse.
Dec 08 01:44:49 <shiva> The fuse is fine
Dec 08 01:47:18 <djlewis> then, checkint the motor out volts and control signals is the way to go. Could it be your software quit?
Dec 08 01:49:06 <shiva> I do not see any signals at the terminals
Dec 08 01:49:30 <shiva> Probable 150mV oscillating. But it should be about 11V instead
Dec 08 01:49:49 <shiva> I rebooted my BBB several times too
Dec 08 01:50:42 <djlewis> you should measure voltages along the signal path, or use a logic analyser.
Dec 08 01:52:16 <shiva> Oh
Dec 08 01:52:20 <shiva> I will do it. Thanks
Dec 08 01:52:34 <djlewis> may the force be with you.
Dec 08 02:06:05 <LifeIsaBone> Anyone had any experience dealing with wpa_supplicant daemon not starting, I am trying to connect to a wpa2 router
**** ENDING LOGGING AT Fri Dec 08 03:00:02 2017