RaspberryPi3 & PiXtend: New attempt to get RS232 working. Following some docs, I need to adjust settings. But seeming contradiction causes confusion on how and what. In the end, I create a file using 2 libraries, but will I see something in minicom? Also, the power connection needs to be more robust. Click the image to watch the video.
ESP32: First focus is on the microphone. I finally find out what's wrong, but is there a fix? Then the buzzer. Is that the same issue? Click the image to watch the video.
Hand: After finding a big problem in the algorithm (only doing the hand-pitch), I should change something. The yaw can only work with some distance. But how to achieve that? Modify the switch? Then: testing all, what does work and what doesn't? And why? Click the image to watch the video.
Mydfir: Focus again on line detection and function calling of lijn_volgen. By close observation of the robot riding in circles, I notice a location problem. This worries me, because why does it happen? If I can't fix this somehow, it may never work. And why is one function never called? Click the image to watch the video.
RI-BASIC: Focus is on solving the sonar & speed problem, but I need to get feedback to debug. So introducing the RS232 connection to minicom for showing printed output. This shows valuable info. But how do I solve the software problem? In the end it's solved, but there's still the question: why did it happen? Click the image to watch the video.
Discovery: Doing some more tests, that do not go well. But the datalog doesn't really reveal info, so I need to add more. Then there's confusion about some variables. Back to the beginning: what's the distance in the first part? I need to get clarity, but info on the functioning of methods() is scarce. Click the image to watch the video.
Arduino Mega2560 S2: Improving the graphs leads to the find of a little mistake but also the range needs to be larger. What's the difference with the RL circuit fully connected again? Click the image to watch the video.
RaspberryPi2: A new attempt to control and read from electronics and fischertechnik using C, C++ and Bash via wiringpi. Using the info from the website, I find that some ideas aren't possible. And I make a small mistake. Also, batteries need to be charged. Oops. But will the result be for the button and phototransistor? Bash via the mac. Click the image to watch the video.
BeagleBoard & rollertrack: First focus is the curve after the looping. It needs to change, but how? Next is the track end with chain: how to get a single ball wait at the end so a magnet picks it? Finally, why doesn't the wormgear switch work? Click the image to watch the video.
15 March (Playlist) Blog 314
RaspberryPi3 & PiXtend: I discover that the PiXtend chip needs to be reseated, but why? Then: time for some demos, with some nice (dry) results. The interface easiest to use is RS232. Time to wire and check, but what are the settings? The search for an example gives a nasty surprise. Click the image to watch the video.
ESP32: Focus again on the buzzer and microphone. What's with the signals? The gpio's should be ok. Some changes to the microphone code reveals an apparent difference between ANSI & AVR C. I decide to make more use of the LCD and have a little oops. Click the image to watch the video.
Hand: First, I've added a power-distributor so I need only 1 adapter. Then the hand-detection switch needs a fix. But how? Next, the algorithm needs to be changed for both switch and yaw. But why does the diagnose say yes and Python say no? Click the image to watch the video.
RaspberryPi: Again: the Digital-Analog-Converter MAX522. What goes wrong? Analyzing the algorithm, I change a few things such as byte size and baudrate. But will that help? Searching for more info reveals that a website has changed contentsno more help. What to do? End of experiment? Click the image to watch the video.
Mirft2: Starting with an (long) intro, I want to set up a connection and meet with Mr. Murphy's Law. Then, continuing with the RGB-HSV conversion tool, I manage to compile it after changing the code a bit and adding link-options. Finally, using Blender3D again, I have to re-model and add more colour to the frame because of a mistake I made. Click the image to watch the video.
Mydfir: Testing the algorithm and checking the datalog, I find that the algorithm lacks some continuity. But after fixing this, Murphy visits and logic is far away. Or is it? Click the image to watch the video.
RI-BASIC: Focussing on the problem with the sonar and power-motor: what's wrong with the algorithm. An example shows several differences, but doesn't explain why the small distance is acting up. And it seems I have to change to old-school connectivity. Click the image to watch the video.
Discovery: More testing on turning at impact, this time with ROBOPro. This shows it's speed-related. Oops. Also: does the counter work? There's a need to change the algorithm. How about the counter and distance at the start? Is there a 0 or reset? Click the image to watch the video.
Arduino Mega2560: More tests using Octave for data acquisition. Putting data into graphs, why are the data so different and similar? Function check reveals I may change thinking. But should I? Click the image to watch the video.
RaspberryPi2: New attempts to get it working after adding a motor. This shows differences between Bash and C/C++ but why? Having an idea with rewiring it works, sort of. Again, why? Click the image to watch the video.
BeagleBoard & rollertrack: Checking with the problems: magnet sometimes at start and end, curve support and looping. The curve support needs a modification, the end needs some distance and the looping is too large. So does this fix everything? Click the image to watch the video.
8 March (Playlist) Blog 313
RaspberryPi3B & PiXtend: After last time, I have to fix a few bad contacts, a missing jumper, find a power solution and get a new Linux image. I also find how to fix the mount for the RPi3. With all set & done, I can power the PiXtend...and I can get in. But what do I find? What works, and what doesn't? Click the image to watch the video.
ESP32: A new attempt to get the buzzer checked.. with weird signal timing. Rewiring prompts for a look at the manual. Another look at the microphone, 7segment display and servomotor. What's going on? Click the image to watch the video.
Hand: After last time, I have to check the motor direction in Python. Starting to change the algorithm, things don't match up and cause confusion. By adding print statements, the confusion only get bigger until I finally notice a mistake in the algorithm. But then I also notice another mistake with the switch. Time for another reconstruction. Click the image to watch the video.
RaspberryPi: Focus again on the SPI signalling to the MAX522. First, a big oops before I even start: reboot. Then the question is why I see so few signals. I decide to do a rewiring. Can I solve the signals by timebase or by timing? Just for fun: another view by Android and Mac. Click the image to watch the video.
Mirft2: Continuing with OpenCV: how can I get the good values? Using darktable I get some RGB values, but how to convert to OpenCV HSV? Search delivers a tool with source code but compilation goes oops. Twice. Then modelling with Blender: observation with colours reveals I made a mistake repeatedly. Oops. Click the image to watch the video.
Mydfir: Focus again on the line detection during driving in circles. What's wrong? Values? Conditions? Structure? In the end, the datalog reveals some code is not executed. But why? Click the image to watch the video.
RI-BASIC: After adding support for the motor, I try to add another (power)motor and a sonar. Wiring is no problem, but how to program the sonar? The manual gives some clues but something isn't working quit well. Why? Click the image to watch the video.
Discovery: Focussing on the difference between covered distance and counter, I decide to add sonar. And again, the robot seems to have its own ideas on what (not) to do. Click the image to watch the video.
Arduino Mega2560 S2: Going further on plotting the vectors in Octave, I realize I need to change the way the time is used. Also, subplots are better, but when the "while" has to be changed. In the end, graphs are plotter and changes become more clear. But what's the solution? Click the image to watch the video.
RaspberryPi2: Focus again on wiringPi and C: can I get the GPIO working? Using the knowledge of pin 0, I count to 12 and try. If it works, I can count the rest of the green pins. Would it work using C++? What's that 4th output again? A motor? Click the image to watch the video.
BeagleBoard & rollertrack: Time to test, which reveals a problem leading to a reconstruction. Then running the algorithm, something goes wrong. But what? When the cause is finally traced, yet another problem returns. Now what to do? Click the image to watch the video.
1 March (Playlist) Blog 312
RaspberryPi3B & PiXtend: Time to finish construction, mount the RPi3 and get started. First cutting the wires, correcting bad solderpoints, placing the ICs. Then the long awaited mount with spacers, to find out that screws are missing?! Also: Raspbian is the wrong Linux to start with? Power has a wire connector...for 2 wires. OOPS. Click the image to watch the video.
ESP32: Time to check out the buzzer, signal, algorithm via oscilloscope. A decision to rewire leads to a discovery that may set things into a different light. Back to the microphone, I check again for the difference between ANSI and AVR C. Also, is my ESP32 the same as the book shows? Click the image to watch the video.
Hand: After all the fixes last time, it's now time to fix the algorithm in Python: adding the motor and switch in conditions switch on and off. After some indentation struggle, something isn't quite right yet. A rewire should fix it, but does it? And then there's the arm-pitch and a hand-pitch. Another oops? Click the image to watch the video.
RaspberryPi: With probing the signals to and from the MAX522 DAC, I try to figure out how to change the algorithm to get the LED work the way I want. But why do the piscope and oscilloscope not go synchronous? Or is it the timing, again? Click the image to watch the video.
Mirft2: New attempts to use HSV in OpenCV and checking values with darktable. This gives some results which don't work out. Finding a mistake in the end, will a 'fix' make it better? Counting gear cycles shows somw consistency. Finally, modelling with Blender3d. Adding more colour reveals some errors. Click the image to watch the video.
Mydfir: To find out why the robot looses track, I decide to add the line sensor input to the datalog. After a few mistakes, I find that it happens way too fast. And not in a consistent way. So what next? Click the image to watch the video.
RI-BASIC: Continuing from last time: can I add a switch and LED? How can I check the wiring? I find that BASIC really isn't Python.. but also the diagnose lets me down in an unexpected way. Click the image to watch the video.
Discovery: Continuing from last time, I add counters from both motors to all sonar-IFs, except the last. When analyzing the datalog, the results are not what I hoped, but also not logical. So where's there cause of the problems? Firmware? API? Click the image to watch the video.
Arduino Mega2560 S2: Going on with Octave: I've enlarged the size of v1. Can I do the same for the other vectors? If so, what does it show? Can I plot it? Click the image to watch the video.
RaspberryPi2: Being familiar to control the GPIO using Bash and Python, but failing using C/C++, I want to find out. So I decide to take another chance and in the end finding some info that raises a big question. Click the image to watch the video.
BeagleBoard & rollertrack: Time to reconstruct the wormgear. How can I make it stick to the axle? The solution seems simple, but needs a relocation of the motor and some more action. Will everythng work then? Or will it go oops somehow? Click the image to watch the video.
22 February (Playlist) Blog 311
RaspberryPi3 & PiXtend: Placing the last jumper, the voltage-regulater and the battery. Then checking out CODESYS on the laptop. This leads to 2nd thoughts about it. Also: PiXtend Python Lib...can this be done? Click the image to watch the video.
ESP32: Focussing on the microphone algorithm, I decide to write a similar one in ANSI C. After some issues, it works. So what does the comparation show? Then: the servomotor worked for a bit, but when? How? And what's with the buzzer? Does it do SOS? Click the image to watch the video.
Hand: Checking everything, I find that I have to fix several things, wires mostly. But where? Diagnose shows what, but then analysis is needed. In the end, I decide for a rewiring and have to adjust the algorithm for switch12. Click the image to watch the video.
RaspberryPi: Focussing on the output A from the MAX522: how do I know it's the correct output? Why does the LED burn w/out the program even running? Switching the 4th probe between A and Din, I get a first glimpse of what is up. Too bad I don't have more than 4.... Click the image to watch the video.
Mirft2: On with OpenCV and HSV: can I restore the colours I got a while back? What do value changes show? Intro to darktable for colour probing. HSV or something else? In the end: more modelling with Blender3D and finding some mistakes. Click the image to watch the video.
Mydfir: After adding the 4th lamp, I need to check and adjust the alogrithm. But what speed is best? Light seems to interfere as well, again. So what is best to do? A small mistake with power shows that the battery won't last as long. Oops. Click the image to watch the video.
RI-BASIC: Introduction into using the BASIC programming language for the RoboInterface using wine emulation on Linux. I skipped the installation of the library on Fedora, which differs slightly from installation on Ubuntu. Click the image to watch the video.
Discovery: With the new distance set, how does it behave? What's the difference between distance and counter value? The algorithm has to be changed again. Click the image to watch the video.
Arduino Mega2560 S2: After disconnecting the resistor from the 5V, I find another instruction: readVoltage(). What's the value for the Ax pins? I decide to add another Ax: A2 from the transistor. What's the result? Finally, I want to enlarge the vectors. But how? Click the image to watch the video.
BeagleBoard & rollertrack: After finishing the looping, it needs to get an ending. But how? Chain? Block? Then: the switches to change course and trajectory. It works manually, but what's wrong with automation? Looks like it's the gears, but how to solve it? Click the image to watch the video.
15 February (Playlist) Blog 310
RaspberryPi3 & PiXtend: Starting with a check on VNC with Android, I continue with soldering a resistor and a jumper. Ending with a nasty surprise: the jumper gets a bit ruined as well as a connector. But why? How? Finally some software: wine and CODESYS. Ending with another surprise. Click the image to watch the video.
ESP32: Continuing with the microphone: what's the signal? From where? Why doesn't the algorithm function? Then big oops and Murphy's Law. Click the image to watch the video.
Hand: The hand-pitch motor needs an immediate replacement (20:1 -> 50:1) as well as a very different setup. Will a worm-gear work? Then a switch yo I4 (I12 actually) but how to put it in place? How to wire it? Click the image to watch the video.
RaspberryPi: With the MAX522 DAC using SPI 3wire, can I get the signal? Using the good timebase, and new data, something seems to happen. Finally. Not really visible on the videostream, but it's there. Click the image to watch the video.
Mirft2: After the Veghel convention (video, pictures), I continue with OpenCV and a better elevation for the objects. But does it work? Also more modelling using Blender. Click the image to watch the video.
Mydfir: Focus on the linefollower with speed, but that doesn't go without problems (what's new..). New modification: adding a lamp on top, so I can (in theory) see the line-status. Right... Click the image to watch the video.
Arduino Yún: After a final intro, I need to re-capture data, display in Octave. Test Wifi and Linux. After which it's the end for this project. Click the image to watch the video.
Discovery: More tests with the trajectory: from the "distance_left", I find that the distance set in the algorithm better be changed. Then I find that distance_left isn't everywhere yet. So what's the result? And something with the camera...without a camera?! Click the image to watch the video.
Arduino Mega2560 S2: Using Octave I read the analogue values from the RL circuit. But do they make any sense? How is 585 the same as 5 V on the scope? How does pulling the resistor effectuate it? Click the image to watch the video.
RaspberryPi2 & ROS: Another attempt on wiringPi: can I get the GPIO to work? On the Mac via VNC with Bash, it seems fine after an oddity. So time to change the subscriber. What will happen? Run or fail? Click the image to watch the video.
BeagleBoard & rollertrack: Reconstruction of the looping takes more than initially anticipated. How should the trajectory go? How large should the looping be? Some solution is found. Click the image to watch the video.
8 February (Playlist) Blog 309
RaspberryPi3 & PiXtend: Parts assembly for the inductors and jumpers. More tests on vnc with Android and Mac. Click the image to watch the video.
ESP32: It's time to add the microphone. Looking at the available GPIOs, I decide to use DO: Digital Output, and wire to D0. Then, the LED from D1. But then, the algorithm. It's an event-registering device. So when it's the time? Click the image to watch the video.
Hand: First: ensuring that the pitch cord can't escape the hook. Then: reconstructing the hand-pitch winch and motor. But how? Finally: how to make sure I pick the correct interface in diagnose? Click the image to watch the video.
RaspberryPi: Focussing on the MAX522 DAC again, using the pigpio library, piscope and oscillscope, I hope to get a result at the output of the DAC. Altough I do see signals on both scopes, I realize very late that the timebase is way off. Ouch. Click the image to watch the video.
Mydfir: Following the Veghel convention, I decide to use artificial light only, and do linefollowing only. When things go wrong, the data isn't consistent with the observation or code. So what needs to be done? The end is...an oops. Click the image to watch the video.
Arduin Yún: Continuing with scp, I realise that I may have to check the settings via the GUI. And find something I wasn't looking for. Then, a quick search leads me to ssh-keygen. Will it work? After upload of the changed code, the console acts odd. Why? Taking a look in Octave to adjust last time's issue with some graphs, I have to change a name. Click the image to watch the video.
Discovery: At the Veghel convention (video, photos) the robot showed very normal behaviour. But: I did manual guide the AC-cable by lack of a charged battery. Time to recheck its behaviour: will it go crazy of stay normal? Click the image to watch the video.
1 February (Playlist) Blog 308
RaspberryPi3 & PiXtend: New discoveries for ppl, VNC for iPad and some parts assembly which doesn't go easy. Click the image to watch the video.
ESP32: Focus is on wiring: the 7segment dispplay and the buzzer. A closer look reveals a mistake for the display, which is quickly corrected. Then: the buzzer signal is weird, the wiring is fine. So what's up? Also the motor doesn't cooperate, again. What's next? A mic or other sensor? Click the image to watch the video.
Hand: Time to put the hand-pitch motor under an angle and hook up to the 2nd interface. As expected this takes a lot of wire. But the serial number could be an issue. The interface wasn't detected by ROBOPro, so I couldn't set it. Will the standard "1" work? Then also, the wrist pivot get a much needed re-reconstruction. Finally, gEDA has to be edited. Click the image to watch the video.
RaspberryPi: Continuing with pigpio/piscope, I play with the loop count and the sleeping time. Checking if the LED is fine (it is!), I put a resistor between output and LED. Then put probe 4 on the output and find it works (sort of.) So what's wrong then? Click the image to watch the video.
Mirft2: An attempt to repeat last time's result, I realize I've made a thinking mistake: the objects should be elevated as well. And the camera needs a modification. In the end, more modelling with Blender3d. Click the image to watch the video.
Mydfir: More testing with linefollowing and detecting objects: what goes wrong this time? I decide to modify the new object: increase the weight. When that seemingly doesn't help. I add something else. But why does colour get sensed again when there's just white!? Sigh. Click the image to watch the video.
Arduino Yún: After the introduction, I try to get scp working and after a code correction and again some data acquistion, I face a few oopses. Also, a possible mistake in the Octave graphs. An unexpected result is noticed in the data console, but how? From what? Click the image to watch the video.
Discovery: Continuing with the calculation of the distance by putting the code into more IFs. Meanwhile, ROBOPro and the datalog show something with the battery....which is supposed to be freshly charged. Oops. Click the image to watch the video.
Arduino Mega2560 S2: Running the algorithm, I find that the green LED burns, and keeps burning. This points to a bug. Then: what the difference between the RL circuit backlash the voltage measured? New reading could give answers, but do they? Click the image to watch the video.
BeagleBoard & rollertrack: First focus is on the monitor: how is the view now. Then: the motors & switches, probed on the oscilloscope. WIll it finally work? Last: the looping. It's not good, but how to take care of it? Reconstruction is needed. Click the image to watch the video.
25 January (Playlist) Blog 307
RaspberyyPi3 & PiXtend: Assembly of (a LOT of) resistors, some LEDs, a few relais and something else. Way too boring to watch, and soldering shows to be a little nightmare. Then on with the RPi itself: despite settings, vnc doesn't just start. And where' are the libraries and tools? Click the image to watch the video.
ESP32: Now the 7segment works via function, it's easy to add digits 4 - 6, but something goes odd at 6. And why does the buzzer sound at odd moments? Probably bad wiring, but the oscilloscope reveals another issue as well. Click the image to watch the video.
Hand: I need to correct the wrist-switch and base-pivot. But after the base-pivot, I turn to the hand-pitch: the motor needs to be in-balance: making a perpendicular angle with the axle. But how to do that? Also, can the motor speed be slower than 1? Click the image to watch the video.
RaspberryPi: A new attempt to get the MAX522 working, I try spidev with the expected outcome. Further searching brings me back to the pigpio library, running piscope. It also shows effect on the oscilloscope, but will it work on the LED? Click the image to watch the video.
Mirft2: Continuing from last time with the improved red detection, I find the new image not as good. Trying other distances to the objects gives some different results. But how to do it w/out ImageMagick? More modelling with Blender3D. Click the image to watch the video.
Mydfir: Focus again on detection by sonar. After more robot-object collisions, I find a mistake in the algorithm. How does it get there?! Then I decide to make another object to delete any possible reflections of the sonar. But will it help? Click the image to watch the video.
Arduino Yún: After a bit lengthy intro & recap, trying to increase the size of the graphs, I end up changing the graph setup. Then in C, can I determine filesize and copy to laptop, without too much hassle? Click the image to watch the video.
Discovery: Focus si again on the distance value: adapting if-condition for 30-35 cm. Bit the datalog shows it's not ok at all. So what's the problem? Click the image to watch the video.
Arduino Mega2560 S2: Reading the input goes wrong, but why? Adding a wire for voltage reading shows I have to rename variables. Some rewiring needed and what's the result? Click the image to watch the video.
RaspberryPi2 & ROS: First, does the GPIO still work after the rewiring of last time? Using the Android tablet for this. Then, checking on GPIOClass, I come across a familiar alternative solution, which after some errors compiles fine. But will it actually work? Click the image to watch the video.
BeagleBoard & rollertrack: Planning to check the wormgear and the looping, things go different. The "rescue" monitor looks like **** and the wormgear has its own issues. After recording, a reboot shows that the monitor can look ok. See instagram. Click the image to watch the video.
18 January (Playlist) Blog 306
RaspberryPi3 & PiXtend: Starting with the downloaded construction manual (apart from startup-manual and data-sheet) I can start with actual placement..which takes hours. Then, after the c(apacitors), d(iodes) and q (for transistors), I continue with ssh and vnc and find I should replace some software. Click the image to watch the video.
ESP32: First, I try to optimize the 7segment display function, after the errors of last time. After solving this, the LDR needs a solution. An observation leads to a quick solution. Also, a reseat of the ESP32 is needed to make the servomotor work. What's next? Click the image to watch the video.
Hand: Checking on the lift on the hand, it's actually a 2nd pitch. Which needs a modification, a checkout and wiring. But how? What should the algorithm be like with what controlling hardware? Does everything work now? (spoiler: several oopses during overall testing). Click the image to watch the video.
RaspberryPi: Investigating the mystery, I first check the spi on the ADC/MCP3008. Then I go on with the spi-3wire on DAC/MAX522. After also using the Mac, while checking on wiring, a big oops happens. Why? How? A final test shows what? Click the image to watch the video.
Mirft2: Starting with the HSV array, I try with several values for H,S and V to get rid of yellow. At the same time, watching the # of cycles..which make much sense. Finishing again with Blender3D to model the robot. Click the image to watch the video.
Discovery: First checking the trajectory (a mess again), I turn to the algorithm to find that I made a mistake in variable and in algorithm. And why doesn't a if-condition apply, according to the data? Click the image to watch the video.
Arduino Mega2560 S2: Once again: how can I read the pwm that is delivered by Octave? Changing the algorithm, pressing the ft switch and finally adding some more input. Something has to work, right? Click the image to watch the video.
RaspberryPi2 & ROS: Checking the GPIO using Bash, I find that a comparison with gEDA goes wrong. For some reason, details are missing and wrong. Wiring is wrong too. After fixing, compilation goes wrong. But it runs...how? why? Click the image to watch the video.
BeagleBoard & rollertrack: Starting with adding another angle to the trajectory, I find a problem with the wormgear. But how to solve that? Also, the chain motor should stop during the shift. Then problems set in. Oops. Click the image to watch the video.
11 January (Playlist) Blog 305
RaspberryPi3 & PiXtend: Introduction of the RaspberryPi3 in combination with the PiXtend: an open-source PLC that can operate together. The setup just needs some work. Also, what's with VNC? Click the image to watch the video.
ESP32: First focus is on the keypad: why doesn't it work? Can I work out the schematics? Then, the 7segment display can be optimized in the algorithm. But this gives an unexpected problem. What's with void and int? Click the image to watch the video.
Hand: Focus again on the winch: how to make this work? Will a modification to the hand work? Then the balance: how about a reinforcement of the arm-base? Then an oops with the wiring to the interface. How to solve that? Click the image to watch the video.
RaspberryPi: Trying again to get the MAX522 working using spidev, I decide to update and reboot..and try the MCP2008 DAC. What will happen? Do I need a rewire? I'm in for a surprise (again) and some food for thought. Click the image to watch the video.
Mirft2: Trying again on OpenCV with values things go bad. Finding other values, what happens? Why? Then: modelling using Blender and close observation reveals I need to change the model. Click the image to watch the video.
Mydfir: Starting with the usual linefollowing test towards objects, I notice something odd in response and direction. Testting with diagnose, something is wrong with the sonar. But how to solve this? Click the image to watch the video.
Arduino Yún: Starting with a short overview, I continue with Octave to get the graphs correct. Then: the lamp mechatronics need improvement to hold the lamp and I find out what's wrong with the flashlight. Oops. Finally, an idea to maybe copy the data to the computer. Click the image to watch the video.
Discovery: Focus is on distance again and trying to get the trajectory straight. But I find that my algorithm isn't effective and contains flaws. Also: what's with ROBOPro again? Click the image to watch the video.
Arduino Mega2560 S2: Focussing on input again, I change the algorithm bit by bit and find out that 0 isn't 0? Time for a switch replacement, but will it make a difference? Another analysis and an small mistake in the schematics. Click the image to watch the video.
RaspberryPi2 & ROS: Starting with another test on GPIO, this time on the Mac. Then, trying to find a solution for the GPIOClass. Finally, back to Mac and GPIO with a camera. Click the image to watch the video.
BeagleBoard & rollertrack: First, checking the switches using Python, since it can't be done properly with the diagnose tool. Then more reconstruction to give the balls more speed for the looping. But will it work out? Click the image to watch the video.
4 January (Playlist) Blog 304
ESP32: First focus: keypad. Does it help to change the algorithm? Then: why do the LCD, motor and LDR not work? Some rewiring leads to an unexpected solution for most. But the keypad still gives some questions. Click the image to watch the video.
Hand: After a short overview: how can the hand be lifted? This simple question starts a new analysis with parts missing and a looming reconstruction of the lower arm. But something has to be done. Click the image to watch the video.
RaspberryPi: For the MAX522 DAC, back to trying Python via the shell, using Mac as well. Is there any logic in what happens? Will some rewiring bring a solution? The live+4 seconds videostream is nice, but a bit .... Click the image to watch the video.
Mirft2: Focus starts on connecting: will it go fine this time? Then, OpenCV and HSV: what's up with the number of pixels. What about Gimp? Finally, further with modelling in Blender3D and finding some points to improve. Click the image to watch the video.
Arduino Yún: Focus is on the attempt to get data visible from the phototransistor. So new data acquisition, making sure all 100x''s are there. Next: Octave..careful observation reveals a viewing mistake which leads to change in the algorithm. Click the image to watch the video.
Arduino Mega2560 S2: Testing the input from the button, takes some code changes but will it solve the mystery? Then, to signal the next loop of the algorithm, I add another LED and another code bit. Click the image to watch the video.
RaspberryPi2 & ROS: For the GPIOClass.h, I realize this must be a linker issue, so this must be solved in the settings. But how and where? Then, with the Mac, another attempt with Bash for the GPIO with surprising results. Click the image to watch the video.
BeagleBoard & rollertrack: Instead of timing, 2 switches should be added to the wormgear and tthe algorithm changed. Does it work? Diagnose says yes. Then the track needs an adaption which requires a reconstruction. Click the image to watch the video.
