**** BEGIN LOGGING AT Thu Sep 20 03:00:01 2018 Sep 20 03:01:55 I did not have to perform config-pin on that MotorCape set up. Yea boy! Sep 20 03:02:10 And...I erased the .dtbo file. Sep 20 03:24:14 Magic on 42nd St. Yes! Sep 20 03:38:39 Do I need a radio for WiFi from the BBBW if I was to control motors via an online application? Sep 20 03:40:45 I am asking b/c the software works but the Flask application does not show if I am plugged in via barrel jack. Sep 20 04:11:09 How can I change the WiFi on the BBBW to accept commands from a web page? Sep 20 04:15:54 I have been reading about daemons and apache2. I am not close yet. Sep 20 04:59:55 The web page came up and as soon as I clicked a button, the whole page failed. It must be having to do w/ the .service file. Sep 20 04:59:57 Sheesh. Sep 20 05:01:08 Off to read more. Sep 20 05:01:32 It does reload but it does not respond. Sep 20 05:01:42 The web page, that is. Sep 20 05:49:04 Believe in yourself, set_ Sep 20 05:49:05 you can do it Sep 20 06:18:39 Otay! Sep 20 08:40:03 Hi the beaglebone is openware does this mean that we can use it in our product and still sale them ?I found an answer on a pdf on your website but i would like a more offical source for my company. thanks for your help :D Sep 20 08:41:00 Bruce1495: you mean, you want to use it as the compute module in some whatever product that you sell? this is definetively allowed (i'd even say, intended) Sep 20 08:42:12 its more like a communication module using CAN port on BBB but yes that 's the answer i was looking for :) Sep 20 08:42:16 Bruce1495: things might be different if you want to keep the beagle name/logo/whatever Sep 20 08:43:03 ok thanks LetoThe2nd ;) Sep 20 09:30:56 btw, reminds me that I want to check what the license says about reusing the BBB design and spinning it into own hardware Sep 20 09:37:53 tbr: this is interesting for me too... Sep 20 09:44:18 the wireless seems to be cc-by 4.0 Sep 20 09:44:28 can't find it for the BBB right now Sep 20 09:45:50 found it https://github.com/beagleboard/beaglebone-black/wiki#terms-of-use Sep 20 09:46:48 I'm not quite sure why it then references cc-by 3.0 Sep 20 09:46:54 LetoThe2nd: i can pull down the white beagle label from the PB board when applied to own hardware :-) Sep 20 09:47:15 tbr: hmmmm Sep 20 10:12:05 Found this: "We do not encourage the use of the board that we manufacture under the BeagleBoard.org logo in commercial products." Sep 20 10:13:09 But this means sure not prohibited... thinking... Sep 20 10:27:25 dg7sgq: I read that as a statement by CCo a long defunct company Sep 20 10:29:07 dg7sgq: there are also 'industry grade' versions of the BBB by other manufacturers. IIRC they don't have HDMI and maybe something else. No clue if they are much better RFI-wise. If you put it in a product, be prepared to shield well. :) Sep 20 10:29:53 or you might end up in QRM-hell Sep 20 11:21:00 tbr: FCC and CE is always hell, with or without QRM! :-) Sep 20 11:22:37 zmat thanks but I had already figured that out too :) Sep 20 12:46:39 m Sep 20 18:52:49 any suggestions for heatsinks for a beagleboard X15? Sep 20 19:17:25 Hello. Sep 20 19:18:26 Does a .service file prevent a BBBW from running a Flask App in Python via an online web app? Sep 20 19:18:34 For instance... Sep 20 19:19:51 I am using the MotorCape. Does the attachment of MotorCape to the BBBW create an issue for running applications online? Sep 20 19:19:52 ... Sep 20 19:21:41 Please hold for pastebin. Sep 20 19:27:26 https://pastebin.com/7k7Asved is the software for the Python/Flask app. Sep 20 19:27:32 The HTML is another story. Sep 20 19:30:09 The app works when the BBBW is plugged in via USB. Sep 20 19:30:53 But b/c of the MotorCape needing me to plug the BBBW in via barrel jack, I cannot test the motors via USB. Sep 20 19:33:01 .. Sep 20 19:33:02 ... Sep 20 19:33:38 Scratch what I am saying. I think the software is a bit off right now b/c of Capes interface instead of a direct line to the L298 driver. Sep 20 19:38:02 https://pastebin.com/MjhvWYee should do it! Sep 20 19:57:27 ehm Sep 20 19:59:23 you're just turning motors on and then immediately off again, hence nothing will happen Sep 20 19:59:55 except, confusingly, when the state is "S" for Stopped where you do in fact turn the motors on Sep 20 20:01:23 Oh. Sep 20 20:01:25 I see. Sep 20 20:02:10 GPIO.HIGH is on, right? Sep 20 20:03:17 also it's a bit confusing you call the motors leds, and I'd suggest also using named constants for the motor direction pins to increase clarity Sep 20 20:03:52 Okay. Sep 20 20:04:31 Sir, I am more worried about my crashing app than the software example right now. Sep 20 20:05:18 For some reason, I cannot get the board booted w/ the software running w/out crashing. The app just closes and states, "Err cannot connect." Sep 20 20:05:26 ... Sep 20 20:06:29 Oh. PWM starts and stops the motor. Then, GPIO controls the direction? Sep 20 20:07:00 yes, which is why I named those pins mX_dir (for X=1..4) Sep 20 20:07:09 Okay. Sep 20 20:07:45 I guess now is time to change the software. I will get to the booting process w/ the .service file later. Sep 20 20:08:59 zmatt: Can I put in negative values for moving another direction? Sep 20 20:09:07 for PWM? Sep 20 20:09:47 when the mX_dir gpio is LOW (default), the motor will be in forward direction when enabled (i.e. the mX+ terminal will be 12v and the mX- terminal will be 0v) Sep 20 20:10:03 when the mX_dir gpio is HIGH, the motor will be in reverse direction when enabled (i.e. the mX+ terminal will be 0v and the mX- terminal will be 12v) Sep 20 20:10:13 no, pwm must be in range 0-100 Sep 20 20:10:24 a negative pwm value makes no sense Sep 20 20:10:37 Okay. Sep 20 20:10:44 of course it would be possible to make a wrapper to do so Sep 20 20:10:58 Hmm. Sep 20 20:13:47 Okay. Everything is changed and easier to read/understand. Sep 20 20:14:04 I got what you were saying. I switched up the software to suit those needs of "future" readers. Sep 20 20:16:07 Off to test it w/ the vdd_5v now! Sep 20 20:19:41 Yep. I was making the motors turn on, turn off, and this was done basically right away. PWM should not be set to 0 unless I want things to come to a halt. Sep 20 20:20:40 in regards the the MotorCape. Sep 20 20:23:21 ... Sep 20 20:25:35 I've updated https://pastebin.com/ypQ3hpVb with a simple wrapper for the motors Sep 20 20:28:19 I saw the software. Sep 20 20:28:28 Nice! Sep 20 20:28:56 Hey zmatt: Have you ever served an app online via .service file and the BBBW? Sep 20 20:29:33 Or...is there a better way? Sep 20 20:29:54 that question is simply weird Sep 20 20:30:15 there is nothing hardware-dependent about making a service Sep 20 20:30:36 I know but I cannot figure out why my .service file is making my app fail. Sep 20 20:30:51 what do the logs say? Sep 20 20:30:59 Which logs? Sep 20 20:31:07 journalctl -u your-app.service Sep 20 20:31:14 Oh. Please hold. Sep 20 20:33:25 https://pastebin.com/tNWnL2z6 is all it states. Sep 20 20:35:31 and you don't get this error when running the app manually? (which of course you have already tried, since I've repeatedly told you to test your application standalone before attempting to run it as a service) Sep 20 20:35:44 Right! Sep 20 20:36:56 I had run this software before having difficulties w/ the .service file. Since the making the .service file available, my app no longer starts w/out having it run as a .service file. Sep 20 20:37:00 But... Sep 20 20:37:14 This does not work when plugged in via barrel jack for some reason. Sep 20 20:37:28 https://pastebin.com/6tzDjyNm is the service file. Sep 20 20:37:51 Let me go and try to run the app manually again. Sep 20 20:38:05 also why are you specifying an ip to listen on? that's a really fragile thing to do. I suggest using host="0.0.0.0" instead Sep 20 20:38:14 Okay. Sep 20 20:38:22 I never got the Flask apps to work that way. Sep 20 20:38:32 I will try it anyway. Sep 20 20:38:46 and I very sincerely doubt that this error is dependent on how the beaglebone is being powered Sep 20 20:39:01 That is what I thought, too. Sep 20 20:39:08 I cannot figure things out just yet. Sep 20 20:39:31 more likely it is because your service runs before it has acquired an ip, hence it is unable to open a listening socket on 192.168.1.18 Sep 20 20:39:49 which is fixed by opening a listening socket on 0.0.0.0 (meaning "any ip address") instead Sep 20 20:40:42 the alternative option would be if the port is in use (which *I think* gives the same error, not 100% sure), but then running the app standalone (not as service) would also fail Sep 20 20:41:08 The app is running now. Sep 20 20:41:35 Standalone as is, for now, the runs but how do I open the app online on a separate computer? Sep 20 20:41:39 ... Sep 20 20:41:52 0.0.0.0:5000? Sep 20 20:43:06 I don't understand the question Sep 20 20:43:21 nothing changes about the way you connect to the service Sep 20 20:43:40 I know. I goofed up. So, on my computer, not the BBBW, how would I change the IP address and make things work? Sep 20 20:43:52 nothing changes about the way you connect to the service Sep 20 20:43:59 I am going to a web page online on my personal computer while running an app on the BBBW. Sep 20 20:45:10 personal computer: -> http://0.0.0.0:5000 to serve this app? Sep 20 20:45:33 Okay. Ten-four about the service. It is okay. I got it. Sep 20 20:46:03 http://0.0.0.0:5000 is nonsense, and is not how you previously connected to the app Sep 20 20:46:18 Right! Sep 20 20:46:34 So, I would just type in my ip address and the port: 5000? Sep 20 20:46:51 even though the host name is different. Okay! Sep 20 20:48:04 again, running a server on "0.0.0.0" means "any ip", hence you can connect to any ip that belongs to the server (the beaglebone) Sep 20 20:48:14 You are right, as usual. So, the app works again w/ that host name 0.0.0.0. I was mistaken. Sep 20 20:48:16 Oh. Sep 20 20:48:31 Okay. Sep 20 20:48:56 Any IP that the bbb has under wlan0 can be used. Got it. Sep 20 20:49:44 Let me set up the .service file again to make sure that the systemctl status shows enabled in green. Sep 20 20:50:54 Loaded: loaded && Active: failed Sep 20 20:51:00 I have to set up this file again. Sheesh. Sep 20 20:53:49 And... Sep 20 20:54:20 just waiting until the board starts up and boots. Sep 20 20:54:38 Then, it is on to testing the site w/ the buttons. Sep 20 20:56:12 I do not know S#$%. I do not believe it was about that "0.0.0.0" instead of my personal IP. Sep 20 20:56:20 dang host names. Sep 20 20:56:36 It works! Sep 20 20:56:42 My first server! Sep 20 20:56:49 it's alive!! Sep 20 20:56:58 I feel happy. Thank you and yes...IT IS ALIVE! Sep 20 20:57:37 Now, onto building more. Sep 20 20:57:55 If I still had hair, I would have waved it and flicked it about. Sep 20 20:57:56 Ha! Sep 21 00:03:10 If I was using a GitHub.com repo and mentioned BeagleBoard.org and GHI for producing the MotorCape, would this be okay by way of the .org's ideas? Sep 21 00:03:11 ... Sep 21 00:15:44 Is it just the icon we cannot use or the name also? Sep 21 00:37:10 I mean, look, I am not going around flashing badges of the dog icon or saying I am in anyway helping this .org. Sep 21 00:37:11 ... Sep 21 00:37:40 I just thought I could use the name BeagleBoard.org to signify to people who is making the MotorCape w/ GHI people. Sep 21 00:50:47 https://github.com/beagleboard/beaglebone-black-wireless/blob/master/LICENSE is where this info. is located. Sheesh. Finally. Sep 21 00:51:00 So, mentioning the BBB.org foundation is okay. Good! Sep 21 01:02:38 What is the name of the dog icon? Sep 21 01:02:59 I have looked! Wait. Let me check google. Sheesh. Sep 21 01:04:46 Nope. Sep 21 01:19:52 Bowzer? Sep 21 01:20:16 Oh well. I will back down for now. Sep 21 02:39:22 hi all Sep 21 02:40:04 Hello! Sep 21 02:40:13 Anyone got any advice on whether my BBB is dead or not? I get a blip from the power LED on the board but nothing afteards Sep 21 02:40:34 Oh. Not me. Did you try a new image? Sep 21 02:41:34 yassyass: brb Sep 21 02:41:43 Maybe someone will help you by the time I get back. Sep 21 02:41:45 Sorry. Sep 21 02:42:00 yassyass: it's dead Sep 21 02:42:41 yassyass: (assuming you don't have external hardware connected to the expansion headers that could be causing problems) Sep 21 02:44:18 yassyass: the power led blip means that during the power-up sequence the PMIC detects a fault and powers the system off again Sep 21 02:45:40 a common cause for such a fault would be an internal short-circuit inside the SoC caused by a damaged I/O cell Sep 21 02:45:46 usually damaged by overvoltage Sep 21 02:49:52 I learned not to plug in or take out leads while the BBB is on. Sep 21 02:54:00 that can be a useful precaution Sep 21 02:54:38 Yes...who knows what types of loads are connected and when. Sep 21 02:54:49 Better safe than sorry. Sep 21 02:55:09 also when applicable (which is almost always), connect ground lead first Sep 21 02:55:18 Trust me! I made one faulty move once. I am still p 'od about it Sep 21 02:55:21 Oh! Sep 21 02:56:05 Good idea. Ground first except for batteries. Sep 21 02:56:17 it goes dead positive to live positive. Sep 21 02:56:26 uhh what Sep 21 02:56:29 Yep! Sep 21 02:56:34 ground first, including for batteries Sep 21 02:56:39 What? Sep 21 02:56:41 No way. Sep 21 02:56:49 Serious? Sep 21 02:57:12 it's typically not hugely important for batteries which terminal you connect first though Sep 21 02:57:20 My batteries always spit juice when I put the lead to the ground first. Sep 21 02:57:30 ........ Sep 21 02:57:37 what the f are you doing? Sep 21 02:57:40 Right at when I place the lead to + after -. Sep 21 02:58:02 Just putting in leads to battery terminals. Sep 21 02:58:14 w/ the respective connectors. Sep 21 02:58:37 if you connect a load to a battery there's always a risk of a small spark when you make the final connection, regardless of which lead is connected first Sep 21 02:58:43 It happens that way w/ multimeters too. Sep 21 02:58:46 Okay. Sep 21 02:58:52 Agreed. Sep 21 02:58:58 if you're seeing a spark on a multimeter then there's something very very very wrong Sep 21 02:59:09 iirc, besides short circuits, plug in is bad for high capacitive loads, but digital mosfet capacitive loads are low. Taking out is bad for inductive loads, but again, almost none. Sep 21 02:59:41 Sparks from the battery once I check it w/ the multimeter has happened before. Sep 21 02:59:52 has done happened! **** ENDING LOGGING AT Fri Sep 21 03:00:01 2018