Roomba 5xx - repairing a power supply

Time ago I had a Roomba 560 with an Error 5.
The problem was the power supply used to charge the battery.

Time to try to fix it.

Roomba 5xx and Err 5 charging

Yeah OK, is just "another post about the Error 5 when charging a Roomba of 5th generation", but is just a note/reminder.
The official suggestion from iRobot is to check the battery contacts, the base contacts and relative Roomba contacts.
If all is OK, then try to change battery and if still not OK, send the unit to repair.

The first thing to do however is to measure the voltage of the power supply.
After repairing a Roomba (a 560 unit) and changing battery, after few days the Err 5 started to appear.
Measured the power supply : 19V

It MUST be at least 22 V !!
Changed the power supply with a new one, and Err 5 disappeared.

Of course is possible to have many other causes for the error, but I would say that in order to diagnose it, the sequence that did the trick for me is :

• check the power supply. The Voltage measure must be at least of 22 V
  if OK
• try to use a power stabilizer or at least a surge control
  if OK
• check the battery contacts and clean up from oxide and dirt
  if OK
• change the battery

If OK but still Err 5, well, it "could be" also a motherboard problem.

So it seems now I have a nice iRobot power supply to repair :)

Office gadget - the Fhelper

Ok, this is just for fun.

Energia and MSP430G2553

Recently I had a little bit more deep experience with Energia and the MSP430G2553.
Here some notes about this experience.

SmartPhone audio accessory

Some notes about some audio accessories for smartphone.

Hype Retro Walkie Talkie handset

This funny toy is shaped like a traditional-style ham radio microphone.

The idea is to "transform" the smartphone into an Ham radio. For example, used with Zello can facilitate to use it in a mobile environment or for who is nostalgic about it.

I tested it on the Samsung tablet but is not working with Zello.
However is working with other applications. This suggests that there are other differences other the 3.5 mm jack pinout.

Let's open it up

The quality of the gadget is of course very low. Beside, for 5$ really is not expected to be better.

The gadget

To open it there are just four Philips screws

The little board has a small amplifier based probably on  a LM386.

There are two push button and a trimmer for the ON/OFF and volume setting.

The small push button on the top is the one that is used to start the conversation.

The big push button on the side simply mute the speaker (IMHO wrong  choice since normally the PTT button is on the side on a normal/standard mike).

Operations

The idea is to plug the mike in the smartphone audio jack and turn it on.
After that the audio output is redirected to the small speaker and when pressing the PTT button, the mike is activated.

5V Solar Power Supply for Raspberry Pi - first results

The introductory article was about describing the feasibility of the project.
Let's see some preliminary results.

The measurements

Until now I did run the system with an external voltmeter to see if the solar panel was able to keep up with the system.
It seems that so far the answer is no.

The graph shows the battery level measured in few days.
Note that basically there was no real load to the battery, only the Dc/Dc converter, so very few mA were drawn from the battery.
The days were pretty cloudy all the time, so no full sun for long time. In the best scenario (see the latest days) the battery level barely reached the 2.9V, well well below the minimum of 3.5V, and again I stress the fact there was no real load on the system.

The solar panel used so far is a 6V 2W, capable to provide in full sun a current of 330mA.
Definitively not enough to keep the battery charged AND powering something else (the Raspberry Pi has an estimated drawing current around 300-350mA).

Until there was sun the system did run happily, but as soon as the solar panel was not in full sun, the system had to use more and more the battery to power up the project and of course there was no battery charging there.

The battery is a nominal 3.7V 6600mAh and can last just few hours when not charged, so the system starting with a loaded battery in a sunny day can run almost all the day, but that only the first day.

What to do ?

There are few things to try.

1. Use a bigger and powerful solar panel.
   A bigger solar panel, still 6V but maybe 6 or 9 W, probably can give more energy even with less light.
   In full sun the power should be enough to charge the battery AND power the system.
   Adafruit has a 6V 5.6 W solar panel, capable to give up to 930 mA in full sun and presumably more juice even in less than ideal conditions.
    
2. Implement an intelligent power management
   We can assume to don't have the system running 24 hours a day.
   An external circuit (like the RPOf) can monitor the charge of the battery and shutdown the Raspberry when the battery level is below a specific threshold.
   When the battery threshold level is above a specific value the circuit can power on back the Raspberry.
3. Reduce as much as possible the Raspberry Pi current needs.
   It can be done disabling every thing not needed, like the HDMI port or the LEDs.
   Even better adopting a Raspberry Pi 3, eliminating also the need to power the USB ports (currently the USB ports are in use for the WiFi dongle).

Very probably all the solutions will be needed.

Sensor modification

To better handle the solar management, a modification is needed on the light sensor.
Currently the light sensor is based on a photoresistor.
It can indicate if there is light or dark but is not enough to determine the "quality" of the light.
In other words the value returned is not enough to determine if the light is enough to generate ppower via the solar panel or not.
To do so a better light sensor is needed.  So in the near future I'll use a solar light sensor rather than the generic light sensor.

Entertainment system evolution

After long time I decided to do something to improve little bit my entertainment system.

In the past I played with some streamers and lately I ended up to use the glorious Wii to watch Netflix or Chromecast with the same purpose.
For a while I tried to use some Android sticks without much success.
They did work but all suffered by a bad video quality and connection problems.

In fact the connection to the network is the real problem.
The TV is located far away from the WiFi router and even using a repeater it didn't improve much the connection reliability.

So after a long time experimenting with cheap and wireless streamers, I decided to set up something better.
Here my basic requirements :

• Wired connection
• Faster streamer
• Decent user interface
• HD quality
• Possibility to be connected to the main network
• Possibility to stream from my server
• Possibility to stream from local memory (flash pen)
• Support for all video formats
• More streaming choices than Netflix
• Possibility to receive local HD program via antenna

Looking for something capable to cover these requirements, I ended up with two choices :

• Wetek Play 2
• Amazon Fire TV

Wetek Play 2 is a nice and faster streamer with also the possibility to install a digital HDTV receiver (ATSC).
It is Android based and uses Kodi as main streaming management.

Amazon Fire TV is an Android based streamer with Alexa (the Amazon voice interface) integrated in it and very nice intuitive way, plus it supports Plex for streaming.

I tried to install Kodi on the server but I had some problems, then it was not clear when the Wetek Play 2 would be available.
I then installed as media server Plex on the server, after reading some interesting reports, and it went perfectly, plus Amazon Fire TV was readily available.

Because of that I decided to go with Amazon also if is missing the possibility to connect an ATSC receiver in order to see local HDTV channels.

As bonus it has Amazon Alexa that helps to integrate vocal commands to search for programs or activate applications. 

So after a while, here some pros and cons of using Fire TV.

Pro

• Easy to configure and handle
• Fast streamer. No I mean ... FAST.
• Nice to search/select some programs using Alexa
• Fast streaming from my server using Plex
• Quite reliable
• Very small, very easy to hide

Cons

• Vudu is blocked because competitor of Amazon
• No possibility to connect an ATSC receiver
• Not integrated with Amazon Echo even if both are using Alexa
• Too many apps require subscription (I guess is the same for all streamer though)
• Quite close system. Is Android but is not open to install whatever you want

Playing with Alexa and Echo

After my first tests with the Raspberry Pi and Alexa it was time to try an Echo.
Since now is available a more cheap version, the Echo Dot, I bought one of these and started to play.
Here some notes about.

Is it good ?

Yeah :) It is good.
Of course is not perfect, there is a huge space for improvements, but it is already something, especially when I was able to link it with my HA system.
But let see some details.

What it can do

Well, like the things I tried with the Raspberry Pi  you have the usual activities, asking the time, setting timers, creating lists, emulating Eliza :)
Other than that, the big advantage of Echo Dot is the possibility to ask and listen music, podcast, etc.
Of course to have decent results is better to pair it with an external bluetooth speaker.

Then, with some plugins and extra work, is possible to interface Alexa with different things, like my HA system (based on X10) and other appliances.
Now is really nice to turn on/off/dim the lights of my house simply asking Alexa to do it.

Yeah, nothing really new, already 20 years ago it was possible something like that, but the cost to set up a system capable to respond to vocal commands was huge and the system was surely less responsive and less easy to use.
Alexa really is impressive and all considered is easy to set up.

Well, OK, easy relatively speaking.
For example, in order to connect Alexa to my HA system I had to do some vodoo :)

Interface Alexa with X10

As I said, my HA system is still based on the old, glorious X10 protocol.
Why ? Well, I had around tons fo X10 modules and the newer systems, like Zigbee or Zwave, are still quite expensive.
I would love to migrate on Zigbee for example, but I still have a lot of still good X10 working modules.
I hate to trash away something that still work.

I have a server running Heyu that controls the lights and it handle some macros and timer.
So the natural question was, is it possible to interface Alexa with my server ?
A quick search with google said yes !

I found a very nice and detailed article from Corey Murnaghan : Amazon Echo X10 Home Control.
From there actually there was a link to an update : UPDATED Amazon Echo X10 Home Control

The two articles (I strongly suggest to use the updated version) discuss about how to interface Alexa with a Raspberry Pi running Heyu.
I already had a server running Heyu, with the glorious Ubuntu 16.04, so I used that article as main guideline, changing things here and there and in the end, voila', everything worked just nice.

The main differences from the Corey's article were about of course the Heyu installation and setting, since I already had that done years and years ago :)
In the end I just installed the Ha-bridge and configured little bit differently, also because my server hosts some websites, so it was impossible to follow some suggestions like erase the /var/www/html directory.

I had to change also some ports, since I was already using the port 80.
At least my version of Echo/Alexa requires to use the port 80 to recognize the Ha-bridge>
In order to have Alexa recognizing the server, I had to change the UPNP IP Address, forcing to use the one of the server.
Of course I had also to modify some firewall configuration for security reasons, to make the HA system local to my network and not be accessible from outside.

But in the end, I have now a very nice and useful way to control my lights :)

5V Solar Power supply for Raspberry Pi - feasibility phase

Ok, here the deal.
The goal is to have a 5V solar power supply for Raspberry Pi in order to power up a project (fHelper).

Playing with Vagrant

Vagrant is a way to handle virtual machines for development or other uses.

Here some practical notes about this tool and how to use it.