**** BEGIN LOGGING AT Thu Jan 02 02:59:58 2020 Jan 02 09:44:14 @zmatt: i really appreciate your help so far, thank you very much you just made exploring BBB so easy. I compiled the code with no errors but on tring to run it i get this open /sys/class/gpio/gpio60: No such directory Jan 02 11:41:25 it should be there on a fresh system Jan 02 11:41:51 unless you changed settings in a way that has caused it to be not there Jan 02 11:51:47 @zmatt: i exported the pin(gpio60) manually even afterwards i still got same result that is" No Such directory" Jan 02 11:53:37 manual exporting should not be needed, it should already be exported by default Jan 02 11:54:13 and maybe there's a bug in the code, like I said I didn't test it other than to verify it compiles, although it's based on code that *is* tested... but it's possible I fucked something up in the translation to C Jan 02 12:03:01 @zmatt: i just rebooted the BBB and tried running it again and now its responding when theres a HIGH and LOW but the issue now is its kind of translating it into some sort of gibberish more like its printing in bytes Jan 02 12:42:59 whats the best way to set up and start off using the beagle bone AI? Jan 02 13:07:16 m-blasie: eh should just be printing 0 or 1 Jan 02 13:07:45 m-blasie: *it should be Jan 02 13:08:21 ah no, my bad! Jan 02 13:08:37 I'll fix the source Jan 02 13:09:05 easiest fix would be to change (in main): Jan 02 13:09:07 printf( "%c\n", gpio_read( &gpio ) ); Jan 02 13:09:08 to Jan 02 13:09:16 printf( "%c\n", '0' + gpio_read( &gpio ) ); Jan 02 13:09:20 or Jan 02 13:09:27 printf( "%d\n", gpio_read( &gpio ) ); Jan 02 13:09:31 the latter is probably nicer Jan 02 14:04:51 @zmatt: you are amazing,i works perfectly well now.thanks alot, now i just have to figure out how to implement this such that it can read through several pins. Thanks once again Jan 02 14:08:08 yes the gpio_wait_event is basically just meant as example, showing you simply wait for a POLLPRI event on the fd... waiting for events on multiple fds is also supported by poll(), and relatives like epoll and select, but typically you'd use some event loop library that will abstract this away for you (and also provide other useful features like timers) Jan 02 14:10:30 e.g. when using sd-event (libsystemd) you could use sd_event_add_io( SD_EVENT_DEFAULT, NULL, fd, EPOLLPRI, callback, userdata ) to arrange for a callback to be invoked whenever the gpio has detected an edge Jan 02 15:10:23 @zmatt: okay am actually lost right now, like my legs are still shaky on Linux, i recently just fell in love with it although my interest rate has appreciated +100% Jan 02 16:50:09 m-blasie: event loops aren't exactly a linux-specific thing, they're used on every platform Jan 02 16:53:03 https://pastebin.com/Y5y7aLa1 example using sd-event (but note that there's nothing specific about sd-event here, there are plenty of alternatives) Jan 02 21:12:49 zmatt do you know if PCLK is still active during the blanking period for the LCD? Jan 02 21:13:33 Regarding the BBB LCD controller output. I am looking through the documentation. Jan 02 21:19:13 never mind found it 13.3.1.1 Pixel Clock (LCD_PCLK) Jan 03 01:56:59 Is there such a thing as duty_cycle in the MotorBridge.py file here at https://github.com/Seeed-Studio/MotorBridgeCapeforBBG_BBB/blob/master/BBG_MotorBridgeCape/MotorBridge.py? Jan 03 01:57:29 Okay...I know there is not but how could, if you have time, I set up the duty_cycle for the Servo Motors in the MotorBridge.py file? Jan 03 01:57:38 it's an argument to DCMotorMove Jan 03 01:57:45 Oh. Jan 03 01:57:57 So, I can use DCMotorMove in the Servo source? Jan 03 01:58:28 no, for servo you don't directly control the duty cycle, you specify the desired angle Jan 03 01:58:43 I understand. Jan 03 01:59:02 Why can I not control duty cycle like in the Adafruit_BBIO.PWM library? Jan 03 01:59:28 Well. Jan 03 01:59:32 I get why. Jan 03 01:59:42 Aw. Jan 03 01:59:44 Do not mind m e. Jan 03 02:01:01 I mean, I'm not terribly familiar with servos, but I'm pretty sure the angle is a way to express the duty cycle, with some scaling factor, it's just a more user friendly to take angle as parameter than duty cycle Jan 03 02:03:36 OKay. Jan 03 02:03:39 I understand. Jan 03 02:03:39 especially since the angle is determined by the pulse width, not the duty cycle, so if you specified a duty cycle then all your values would become wrong if you'd ever change the frequency Jan 03 02:04:18 I have been trying to catch up on ideas relating to servos. They are more complicated then regular motors in my view. Jan 03 02:04:21 So far. Jan 03 02:10:09 http://www.toptechboy.com/tutorial/beaglebone-black-lesson-12-control-a-servo-from-python-using-pwm/ is what I was watching online. Jan 03 02:10:35 Some video w/ text at the bottom. There was some basic math and some slope formulas. Jan 03 02:11:24 brb Jan 03 02:30:07 https://docs.google.com/drawings/d/1lWe-R2buaWqaUmbDp5T3a5mYN25duEwtYaDRlWi6Yoo/edit?usp=sharing is something I came across. Jan 03 02:31:05 I got it from http://www.python-exemplary.com/index_en.php?inhalt_links=navigation_en.inc.php&inhalt_mitte=raspi/en/servomotors.inc.php but it is for the Rpi instead of BBB stuff. I can translate the info. to BBB libraries but not to the MotorBrige.py source. **** ENDING LOGGING AT Fri Jan 03 03:00:23 2020