**** BEGIN LOGGING AT Tue Aug 04 16:58:21 2020 **** ENDING LOGGING AT Tue Aug 04 17:02:41 2020 **** BEGIN LOGGING AT Tue Aug 04 17:16:18 2020 **** BEGIN LOGGING AT Tue Aug 04 18:09:00 2020 Aug 04 19:04:10 oi Aug 04 19:04:18 hi Aug 04 19:06:00 I'm having trouble sharing internet via the USB port. do the configuration of the gateway, but does not ping the server other than 8.8.8.8. Can someone help me? **** BEGIN LOGGING AT Tue Aug 04 19:56:21 2020 **** BEGIN LOGGING AT Tue Aug 04 21:11:48 2020 **** BEGIN LOGGING AT Tue Aug 04 23:53:34 2020 Aug 05 00:45:16 What does a GPIO pin on a scope supposedly look like currently? Aug 05 00:45:37 I have no reference. No joke. Aug 05 00:47:08 ----------------- Aug 05 00:47:11 something like that Aug 05 00:47:17 Dang. Aug 05 00:47:19 Okay. Aug 05 00:47:32 I had an abnormal looking wave then. Aug 05 00:47:36 unless your vertical scale is bogus and all you're seeing is noise Aug 05 00:47:44 Oh. Maybe so. Aug 05 00:47:52 @zmatt: Would you take a gander? Aug 05 00:48:18 Anyway, I will post it like earlier today. Aug 05 00:48:28 make sure your vertical scale is such that 0V - 3.3V fits on screen (with comfortable margin) Aug 05 00:48:57 https://imgur.com/kbdk2j0 is my scope doing ITS thing. I am still trying to master this little bugger. Aug 05 00:49:18 your vertical scale is definitely bogus Aug 05 00:49:23 Hmm. Aug 05 00:49:24 Okay. Aug 05 00:49:55 So, a flat waveform is what I am looking to attain? Aug 05 00:50:05 you've set it to 5 mV (i.e. 0.005 V) per gridline Aug 05 00:50:28 an appropriate value would be 500 mV (0.5 V) per gridline Aug 05 00:50:37 Okay. I can do that. Aug 05 00:51:07 What would 500 mV per gridline be appropriate? Aug 05 00:51:28 "What" ? did you mean to type "Why" ? Aug 05 00:51:45 Sorry. I just read that over. Why would 500 mV per gridline be appropriate? Aug 05 00:51:56 Yes. Why. Aug 05 00:53:20 because your scope's screen is 8 grid divisions high, so at 0.5V/div you have 4V of range vertically Aug 05 00:53:34 in which you can fit 0V-3.3V with some margin Aug 05 00:53:41 Sorry. I am asking b/c I am getting odd sequences in sentences on my RM (reference manual). Aug 05 00:53:42 1V/div would be fine too Aug 05 00:53:42 Okay. Aug 05 00:53:46 Thank you. Aug 05 00:53:52 you're getting... what? Aug 05 00:54:03 Would you like to read this ref. man? Aug 05 00:54:07 that sentence looks like a word salad Aug 05 00:54:10 Ha. Aug 05 00:54:26 I get it. You are tired of me. The ref. man. is a bit awkward for me to digest. Aug 05 00:54:30 I keep going over it. Aug 05 00:54:46 Yelling at literature is not fun. Aug 05 00:54:52 You know! Aug 05 00:54:59 what are you trying to observe with the scope in the first place? Aug 05 00:55:04 GPIO HIGH. Aug 05 00:55:07 On p9.12 Aug 05 00:55:49 I am going to set up two BBBs w/ a UART connection to test it later. Aug 05 00:55:50 that sounds like something for which a digital voltmeter/multimeter would be more appropriate but okay. this gpio is definitely not high Aug 05 00:55:59 Oh? Aug 05 00:56:01 Hmm. Aug 05 00:56:32 it looks like it's almost perfectly 0V Aug 05 00:56:58 Every time it goes "high," the waveform shows its presence on the scope. Then, when the next 15 secs. hit the software, the waveform disappears. Aug 05 00:57:01 (ignoring that you've zoomed in 100x too much, causing some high-frequency noise to be visible) Aug 05 00:57:09 Ha. Okay. Aug 05 00:57:24 I was trying to get it to scale. Aug 05 00:57:34 It does not show well on this scope up close. Aug 05 00:57:46 use 0.5V/div or 1V/div Aug 05 00:58:08 Okay. My probe has a 1x and 10x atenuation. Aug 05 00:58:37 either is fine, just make sure the scope knows which setting is used Aug 05 00:58:37 0.5v/div or 1V/div. Okay. Aug 05 00:58:42 Right. Aug 05 00:58:45 Okay. Aug 05 00:58:54 (should be in the setup menu for the channel) Aug 05 00:59:03 Okay. THank you, sir. Aug 05 00:59:14 two channel! Aug 05 00:59:35 I feel like I made a mistake getting this thing but learning about it is fun (at times). Aug 05 01:00:01 1x is probably more appropriate than 10x Aug 05 01:00:07 Yes. I am familiar w/ those options. Okay. 1x. Aug 05 01:01:56 I will test the 1x later and at 1V. Aug 05 01:02:38 10x will have higher impedance (useful when measuring very sensitive circuits) and tolerates a larger voltage range (useful when measuring voltages that would otherwise be outside the range tolerated by the scope), but it will be noisier Aug 05 01:02:47 less accurate Aug 05 01:04:31 Also, the p9.12 pin seems to be set up, at least on my machine w/ your show-pin utility, as << hi Aug 05 01:04:42 Should I need this pin to be set up as >> hi? Aug 05 01:05:15 if it's saying << hi (i.e. input-high) yet you've seeing it as low on your scope, then you're somehow measuring wrong Aug 05 01:05:24 I can always use another pin and search for the pin that has this >> hi pin availability. Aug 05 01:05:48 >> vs << just indicates whether the gpio is configured as input (<<) or output (>>) Aug 05 01:05:53 all gpios are input by default Aug 05 01:05:54 Oh. Aug 05 01:05:57 Oh. Aug 05 01:05:59 Oh. Aug 05 01:06:01 Okay. Aug 05 01:06:40 So, when I use source to bring on/1/high/whatever, it is showing as >> (output) on the scope side? Aug 05 01:06:54 ??!??!?? Aug 05 01:06:57 Sorry. Aug 05 01:07:19 nothing in that sentence makes any sense Aug 05 01:07:37 I can't even begin to guess what you could possibly mean by it Aug 05 01:07:51 Just stop for a second. Aug 05 01:07:53 Please. Aug 05 01:07:57 I am trying here. Aug 05 01:08:42 When P9.12 goes HIGH as an output, does your script show >> instead of < There is no way to catch it, right? Aug 05 01:09:12 yes, it would show "hi >>" indicating output-high Aug 05 01:09:16 Okay. Aug 05 01:09:30 Sorry. Aug 05 01:09:35 I wanted to ask. Aug 05 01:09:44 "catch it" ? Aug 05 01:09:57 My first "question" was obliterated by lack of thought. Aug 05 01:10:08 I'm still confused by what you're trying to do/test in the first place Aug 05 01:10:10 Oh. "Catch it"... Aug 05 01:11:07 Like, it would just be a "figment" right? The >> marks next to Hi are just presumably there and not visually there if I was to run show-pins | sort. Aug 05 01:11:34 ??????? Aug 05 01:12:16 I understand that those marks, the >>, would be there in the script but is there a way to catch those marks visually? Aug 05 01:12:35 By command or by viewing the show-pins | sort command? Aug 05 01:12:56 I just don't understand even the slightest bit what you're trying to ask Aug 05 01:13:04 Okay. No issue. Aug 05 01:13:20 My ideas are running wild w/ what I am going to do tonight w/ that darn scope. Aug 05 01:13:26 I am just excited, I guess. Aug 05 01:14:12 You know this, man. I only make so much sense. Aug 05 01:15:12 for any gpio, show-pins will show whether it's configured as input (<<), output-low (lo >>), or output-high (hi >>), and for an input it will show whether the pin is measured as low (<< lo) or high (<< hi) Aug 05 01:16:17 (in rare cases " Oh. Aug 05 01:18:54 I got all my GPIO pins showing << hi Aug 05 01:19:20 I set it to output in the source. Aug 05 01:19:56 well apparently not, since they're not configured as outputs Aug 05 01:20:21 I configure then as outputs in the source instead of w/ config-pin. Aug 05 01:20:38 I know. There is a missing piece here I do not understand. Aug 05 01:21:07 the most likely explanation is that your code is wrong :P Aug 05 01:21:44 It is a simple Adafruit_BBIO.GPIO as GPIO setup. It works. I can test the LED is necessary. Aug 05 01:21:52 is = if Aug 05 01:22:19 if it worked, then show-pins would show the pin to be configured as output Aug 05 01:22:39 I never ran show-pins while the output was HIGH. Aug 05 01:22:46 That is not what I was saying. Aug 05 01:23:22 I ran show-pins | sort at the onset of testing only and w/out output equally HIGH. Aug 05 01:23:39 equally = equaling. Aug 05 01:24:15 Sorry. I must have missed a sentence explaining myself better. Aug 05 01:24:16 so what's your question? Aug 05 01:24:51 What does a GPIO look like on a scope while attached to GPIO as an output when HIGH? Aug 05 01:24:52 if you haven't configured it as output at the time you run show-pins, then obviously show-pins will show it as input (since all gpios are inputs by default) Aug 05 01:25:03 Right. I understand. Aug 05 01:25:19 I was unaware of show-pins working like you just described until you described it. Aug 05 01:26:22 I understand now. Aug 05 01:26:46 in general an output that's "low" will be close to 0V while one that's "high" will be close to the I/O supply (3.3V in this case). the exact meaning of "close to" will vary, and an output voltage will vary depending on how much current is drawn from or injected into the pin. Aug 05 01:27:19 Right. That is what I have concluded from the past readings and the scope. Aug 05 01:27:34 I fully believe that idea. Aug 05 01:27:46 for an output on the BBB, provided that the current does not exceed 4 mA, output-low should be below 0.45 V and output-high should be above 2.85 V Aug 05 01:28:09 see also https://pastebin.com/YxbLF7Gi Aug 05 01:28:13 Oh. I was unaware of that idea. Aug 05 01:29:13 That is more helpful than you think. Aug 05 01:30:09 From the past to right now, I am sure I have made mistakes in wiring things to and from the BBB w/out that knowledge. Aug 05 01:33:28 I mean...I read things (word of mouth). I have read other items online and books outside of things (word of mouth) but I never had that much of a bunch on the BBB in such a short. Aug 05 01:33:35 Neat-o! Aug 05 01:35:20 Okay. I disable the output w/ LOW at a specific TIME and then I enable the output w/ HIGH at a specific TIME. Aug 05 01:35:30 Is that correct or is that not correct? Aug 05 01:35:44 "disable the output w/ LOW" that makes no sense Aug 05 01:35:49 Okay. Aug 05 01:35:58 Does disable mean low? Aug 05 01:36:01 no Aug 05 01:37:29 a pin can be output-disabled (aka "input") or output-enabled (aka "output"), and if it's output-enabled then it's either output-low or output-high Aug 05 01:37:30 Okay. So, the pin(s) are enabled/disabled and then you have to bring the pin HIGH or LOW. Aug 05 01:37:48 Okay. Aug 05 01:37:49 Sory. Aug 05 01:38:09 so you have three states in total: output-disabled (aka input), output-low, and output-high Aug 05 01:38:09 That makes sense. Is there any way around those facts? Aug 05 01:38:18 Okay. Aug 05 01:39:20 I know for someone like you to reiterate those facts cannot be easy. Thank you. Aug 05 01:39:58 I now can say input is output-disabled. Aug 05 01:40:14 I know this sounds funny to you but that is trickery to me. Aug 05 01:40:14 technically they're not synonymous, but linux does treat them as such Aug 05 01:40:20 Oh. Aug 05 01:40:21 Okay. Aug 05 01:40:58 So, if I was to read some linux jargon, I would come across some ideas as output-disabled at times. Aug 05 01:41:04 since 'output-disabled" just means the BBB is not driving the pin, while "input" means the BBB is measuring the pin state Aug 05 01:41:12 Oh. Aug 05 01:41:16 Okay. I get that part. Aug 05 01:41:47 input on the BBB means I get to measure what is going on from an outer source. Aug 05 01:41:49 you can, and it technically does, do both at the same time... but in that case the input will always measure the value you're driving as output Aug 05 01:42:10 That is more complicated than I thought. Aug 05 01:42:12 you can also do neither, if it's output-disabled and input-disabled Aug 05 01:42:30 Hmm. Is that where I would write an error source bit? Aug 05 01:43:08 there's no way to disable the input of a gpio using config-pin so you will never be in that scenario Aug 05 01:43:10 For instance, I could hold some arguments and call them errors in software. Aug 05 01:43:13 there's rarely a good reason to disable the input Aug 05 01:43:16 Okay. Aug 05 01:43:32 I jumped ship for some reason. I am sorry. Aug 05 01:43:34 other than that, what you just said is again a word-salad and I can't even begin to guess what you mean Aug 05 01:43:41 Ha. Aug 05 01:44:26 I know. You like to know things about this subject. I am basically a joke in it still for the lack of funds I have right now. I cannot get mor edu. in the software/electrical engineering field right now. Aug 05 01:45:03 It is interesting. EE and SE is very interesting. It was always something that was astounding to me. Aug 05 01:47:27 I am reading this book and it is free (well, I am trying to read it): "Programming for Computations (Linge, Langtangen 2020)." Aug 05 01:47:41 They are some people from Norway. Aug 05 01:47:49 One of them died, though. I am not sure why. Aug 05 01:48:09 But, Langtangen seems to know his stuff. He has published many works. Aug 05 01:49:54 Anyway, I will leave you all be for now. I need to figure things out. **** BEGIN LOGGING AT Wed Aug 05 02:49:23 2020 **** ENDING LOGGING AT Wed Aug 05 02:59:57 2020