Just a note to myself as I wasted more time than I should have fixing this.
I recently changed the WiFi access credentials and my HP F4580, obviously, stopped working. Neither the Mac nor the Windows drivers I had let me edit the WiFi settings but I finally found a way to reset the WiFi configuration:
Turn on the printer
Click and hold down the Cancel button
Click and release the WiFi button
Release the Cancel button
This creates a ad hoc network called hpsetup that you can connect to via WiFi to configure the router.
I started off using 3 MaxBotix MB1000 sensors (downwards left, forward, downwards right). The forward sensor always worked pretty well but I had problems getting fast and accurate readings from the sensors pointing downwards. Without calibrating the sensors (making sure they were pointed away from any object) I got results that where to inaccurate to use for table top navigation.
Tonight I tried the Sharp GP2Y0D810 sensor from hobbytronics which makes a huge difference. It's lightning fast and it has a small red LED which is lit when there is an object within a 2-10 cm range which is a great help for debugging. The sensor may be less versatile then the MaxBotix sensor as it only gives a true/false result for a limited range but, in my experience, it's fast, accurate and developer friendly which I exactly what I need. It also cost a lot less :-)
The rover in the video is using two Sharp GP2Y0D810 sensors pointing downwards and a MaxBotix MB1000 for obstacle detection.
I'm in the process of migrating from SiADSL to Tiscali for my home ADSL connection. I have been very happy with SiADSL but I need more bandwidth in upload for video conferences, i.e. Google+ Hangouts with extras. The increase from 7Mb/512kb to 20Mb/1Mb should make a significant difference.
I heard from Michele that Tiscali blocks some ports so I wanted to have a record of the differences between the two provider in case I had problems. Netalyzr to the rescue! It can run as a Java Applet or as a command line client for the more security conscious. It takes several minutes to run and tests everything I ever knew about and then some...
So, what changes between Tiscali and SiADSL?
Tiscali blocks some TCP and UDP ports which I consider a feature, not a problem, if you have Windows machines on the network:
Direct TCP access to remote RPC servers (port 135) is blocked. This is probably for security reasons, as this protocol is generally not designed for use outside the local network.
Direct UDP access to remote NetBIOS NS servers (port 137) is blocked.
Direct UDP access to remote IKE key exchange servers (port 500) is blocked.
I was surprised to notice this potential problem though after I moved to Tiscali:
I passed from PPPoE which uses a max MTU of 1492 to PPPoA which supports 1500 and I had forgotten to update the max MTU on my border router. I tried to leave the max MTU at 1492 but quickly had problems so I increased it to 1500 and it has been working like a charm since. I would have blamed my connectivity problems at Tiscali unless Netalyzr found the problem for me.
I'm also pleased to see that this warning I had on the SiADSL connection is gone with Tiscali:
Exactly the behavior I have seen over the last year(s). Uploads with Picasa killed internet access and video conferencing with many participants is "impossible" even with no other traffic.
I use my motorcycle every single day of the year as long as the roads are not icy which is 360+ days a year in Milan :-)
The only problem I have is that my helmet and glasses fog up when it get's very foggy or cold. I have tried everything, but so far the only thing that has worked is keeping the visor up. Not fun when it's below zero...
EICMA changed that when I found the Zeibe.es stand. I got a sample of their helmet anti fog product which worked very well on my glasses so I ordered a set of their long lasting anti-fog treatment. It worked perfectly today on my helmet visor and glasses. I don't know if it will last the advertised two weeks, but I'm very happy so far.
It really does work as well as the demo video shows:
My Roomba 520 has been out of service for more than six months. The wheels worked fine but the internal brushes didn't turn around anymore. I picked it apart and cleaned the internal gears and engine several times which made it work for a while but I finally gave in and bought a new engine.
Surprise, surprise, it refused to start even after charging it for more than one day. I always got this never ending loop:
It successfully undocked from its docking station but it just reset whenever it tried to start the brushes which led me to believe it was a low battery problem.
Mixing various instructions I found on the internet, I ended up with this procedure which seems to fix the problem:
Connect the Roomba and charge it completely (until the light turns green)
Disconnect the Roomba from the charger (the light turns off)
Turn on the Roomba by pressing the Start button once (the light turns green)
Press and hold down the Dock and Spot buttons for 15 seconds to reset the Roomba (the Roomba turns off)
Release the Dock and Spot buttons (the Romba plays the 5 tone startup sound)
Go back to step 1
I have repeated the procedure 5 times so far and the run time keeps increasing.
My Nabaztag has been collecting dust on my desk since the online service powering it died this summer.
The first meeting of GTUG Milano was the perfect excuse to have some fun and use the Nabaztag for something useful. Using this Nabaztag disassembly video it didn't take long to pick it apart and figure out which wires controlled what.
Thomas took care of all the electronics work and I added some lines of code to the Android ADK demo code to create a proof of concept Android ADK powered rabbit.
Take it for what it is; a proof of concept that just controls the two ears, 3 multi color LEDs and does some text to speech. It does not do any of the useful things that the Nabaztag did like reading mails, rss feeds, showing weather information etc.
It could though, as all of it is easy to implement on Android. Which is why it's time to make it do something useful :-)
I've decided to replace the Android ADK Demo Shield with a Arduino Mega ADK which is smaller an "only" costs 59 euro. It will be the interface with the Nabaztag hardware and control the ears and LEDs initially. The rest of the work will be done by an Android device.
To be perfectly honest, I probably got a bit carried way when ordering the Arduino Mega ADK. I got some LEDs with the idea of organizing them in a grid to show basic symbols, but then I found the 32x16 LED matrix and couldn't resist it. The idea of replacing the 3 multi colored LEDs found in the Nabaztag with something that can display information was just too much to resist. I think it should fit in the almost empty Nabaztag shell but I may have to do some rabbit surgery if it doesn't.
Add the power of cellbots and we have a pretty powerful rabbit on our hands. Let's just hope it does not turn Evil...
The freeWhyMCA Mobile Developer Conference looks very interesting with tracks for Android, iPhone, Windows Phone 7, cross platform development etc. There will be a parallel Mobile Hackathon if you want to show of your coding skillz.
