After fixing some broken plastic after having already ordered a replacement for our couple of years old Hom-Bot 3, I now have a spare Hom-Bot as toy. I noticed the USB interface a while ago, and wondered what access it would give.
- The German roboter forum describes how to install some additional software on the Hom-Bot LG Hombot 3.0 – WiFi & Camera Control with Webinterface
- Rob van Hamersveld created the manual LG HomBot 3 WiFi Mod and added some links to Wifi chipsets you can buy.
I updated to LG firmware 16552, all ok. Next step, install the INSTALL_LG_Hombot_3.0_FW_16552_WLAN-Steuerung_v2.34.zip, all ok.
Attempt 1: WiPi dongle.
It dumps this info in the syslog when connected to ubuntu:
ubuntu kernel: [251677.707825] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 5390, rev 0502 detected
ubuntu kernel: [251677.761133] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 5370 detected
5370 detected, so it should work, according to this list from the German forum:
“The following WLAN chipsets are supported by Hombot:
- rt8192 (WPA / WPA2 and hidden SSID)
- rt5370 (no encryption possible)
- rt3070 (no encryption possible)
- rt3370 (no encryption possible)
On the other hand, rt5370 is not RF 5370, and ubuntu later proceeds loading
ubuntu kernel: [251677.833743] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2870.bin'
Restarting the HomBot with the WiPi dongle, results in a HomBot startup that speaks the “Wireless Router connection is complete”. However, in the DHCP log no new lease is registered, and the last number of the IP number is not echoed as the description said it would. Perhaps I should setup an unencrypted Wifi network since support for the rt5370 is listed with ‘no encryption possible’ and try again. On the other hand, getting a rt8192 chipset based dongle seems a much easier route, so I ordered the TP-LINK TL-WN823N USB WiFI-adapter. Maybe more luck in the next couple of days..
Attempt 2: TP-Link TL-WN823N
Update: The TP Link adapter arrived. However, this seems to be the new ‘V2’ version of the adapter, syslog shows. idVendor=2357, idProduct=0109. When connected to the HomBot at startup, no mention of a wireless router connection is given at all. There is some talk about the new V2 on the Raspberry Mailing list. I guess this one will not work on the HomBot for the same reason as described there. Now I ordered the Edimax EW-7811UN 150Mbps Wireless Nano USB Adapter that is mentioned on the German robotic forum. ETA more than one week..
Attempt 3: Edimax EW-7811UN Nano USB Adapter. Bingo!
Today this adapter arrived. Attached to Hombot. Poweron, Start… “Starting Remote Connection” … “8”.
To quickly find which actual IP address the Hombot is connected to, use nmap to scan for hosts with port 6260 open:
nmap 192.168.1.0/24 -p6260 --open Starting Nmap 6.47 ( http://nmap.org ) at 2016-12-17 12:05 CET Nmap scan report for 192.168.1.83 Host is up (0.019s latency). PORT STATE SERVICE 6260/tcp open unknown Nmap done: 256 IP addresses (22 hosts up) scanned in 2.59 seconds
Webinterface http://:6260 and ssh with root/most9981 work 😉 Very cool to see the maps and the top camera.
As a sidenote I should mention that the wireless router connection is *only* established with one of my two Wifi access points. It works with the fairly recent Asus access point, not with the 5 or 6 year old TP-link.