Wednesday 22 June 2016

A look at the TOP-308 IP camera

The TOP-308 is a wired-ethernet IP network 720p camera. It found it for under 15 Euros (now:20) at Banggood and thought it might replace my somewhat aged Linksys WGS54 .

Power on

The camera does not come with a power adapter. The connector is a center-positive barrel connector and requires a 12V 1A power supply. (ToDo: measure actual current)
I found an orphaned power supply in a junk box.

First contact

If your local network segment is, you're nearly there: The camera's address comes pre-set to Changing it requires some effort. (More about that further down.)
The easiest way to get a video stream is to  use VLC, click "Open network stream" and enter:


as the network address. This should immediately show a live stream.
First stream

Browsing is not a breeze

In Chrome & Safari, the web interface of the camera is a total pain. I struggled with it for quite a while. The web page always came up in Chinese, although the source code shows that there was an "English.js" that could be retrieved from the camera.
So I used the requestly-plugin for chrome to replace the requested file:
The resulting web page turned out to be entirely useless.
No way I could set up any of the camera's parameters in here.

Internet Explorer to the rescue

So I resorted to using the Internet Explorer 11. That brought up a different page that allowed not only to change the language, but also offered to download an active-X control from the manufacturer's web server.
That made things a lot easier to set things up. Date, DHCP.... anything you'd expect.
Many users will probably be happy with that. I'm not.

A closer look

I don't particularly like the Internet Explorer (iexplore) and it is only a matter of time when old 3rd party plugins are no longer supported.
That setup panel needs to communicate with the camera in some way and I need to find out about that. So I ran nmap against the camera:
Scanning [65535 ports]
Discovered open port 554/tcp on
Discovered open port 80/tcp on
Discovered open port 9527/tcp on
Discovered open port 9530/tcp on
Discovered open port 34567/tcp on
Discovered open port 8899/tcp on
Completed Connect Scan at 23:12, 35.47s elapsed (65535 total ports)

So there are a number of open ports to be examined:
Port 80 goes without saying: The web interface.
Port 554 is the RSTP port we already used to stream to VLC in the example above.

That leaves 9527, 9530, 34567 and 8899 for further investigations.

A quick look at a wireshark trace suggests that TCP-port 34567 is the most promising candidate for reading / writing camera parameters. That connection also reveals an otherwise hidden user/password combination:
"PassWord" : "tlJwpbo6", "UserName" : "admin"

On port 9527 there is something that looks like a telnet interface. Logon is "admin" and no password:

Save SysTime to Flash:2016-06-23 10:28:04, Time:2378 Min, Trail:2378 Min
Save SysTime to Flash:2016-06-23 10:30:04, Time:2380 Min, Trail:2380 Min

admin$ help
----------------------Console Commands----------------------------
                 232 Comm dump
              485Pro 485 Protocol!
             ability Net Ability Utility!
                  ad AD debug interface!
               alarm Alarm status!
             bitrate Dump BitRate infomation!
                 cfg Config Help Utility!
        cloudupgrade CloudUpgrade console utility!
                comm Comm Input String
              encode Encode commands!
               front front board utility!

                  fs Fs debug interface!
                heap Dump heap status!
                help Try help!
                 log Log utility!
               magic magic tools!
              netitf NetInterFace Dump!
                netm NetManager Dump!
               onvif Onvif debug msg!
              packet Packet usage!
                 ptz ptz dump!
                quit Quit!
              reboot Reboot the system!
              record Record console utility!
                 rtp RTP Dump!
               shell Linux shell prompt!
            shutdown Shutdown the system!
                snap Snap Console Utility!
              thread Dump application threads!
                time Set SystemTime!
               timer Dump application timers!
             upgrade Upgrade utility!
                user Account Information!
                 ver version info!
             xmcloud XmCloud Dump!
To see details, please use 'cmd -h'

admin$ ver
Save SysTime to Flash:2016-06-23 10:32:04, Time:2382 Min, Trail:2382 Min
ver ---- V4.02.R12.00006210, [000 06 210]
Version: V4.02.R12.00006210.10010.140700.00000, BuildTime: 2016-02-24 13:22:12

That looks like a fairly recent build.

Through the shell command, I seem to be able to access a busybox binary, but could not get it to behave like on a standard linux system.

ls -l
ls: invalid option --

BusyBox v1.16.1 (2015-12-18 09:48:05 CST) multi-call binary.

Usage: ls [-1AacCdeFilnpLRrSsTtuvwxXk] [FILE]...

ls (-l)sh: syntax error: unexpected word (expecting ")")

Something seems to cripple the input. But there are lots of other options to look at:

admin$ netm
netm -c          show Connect Information!
netm -s          show Transport Information!
netm -a          triger Adapter Debug Output!
netm -t <valve>  Adapter statistic output!
netm -p          print debug info or not!
admin$ netm -c

And why does this thing have a reference to an Amazon AWS server? Sooo many questions...

To be continued...

PS: Yes, I am aware of the "CMS" software for the TOP cameras. I try to get away without proprietary software.

Tuesday 21 June 2016

Convoy S2+ mod for Keeppower 18350 cell

From an earlier electronics project, I had a nice Keeppower 18350 protected cell left over. These are great little cells, although the capacity is not outstanding at 900mAh. It would have been a shame not to put that cell to a good use, so I looked for a suitable single cell lamp.
I found a good quality Convoy S2+ that looked nice and should be compatible with 18350 cells. It also was within my budget.
I intentionally choose the warm white XML2 T6-4C LED because I when hiking and camping, I find the cold/neutral white a bit too "harsh" and unpleasant for reading.
I already have an "eagle eyes" branded light for 18650 cells that I quite like. Some of my cells would not fit into that light.
Bits'n pieces
So I ran into the same problem. My cell doesn't fit:
The strip for the protection circuit adds a few 10ths
The bulge is not that wide, so a groove in the anodized aluminium tube should do the trick.
The bulge is just 4mm wide
So it's off to the workshop...
Not too much pressure and a pair of protective pads!
... to file it down a bit. To get smooth ends, I needed a bit of fine grained sand paper.

And sure enough:
The battery now fits nicely
This works, of course:
Ain't she a beauty?
I was pleasantly surprised by the moderate power requirements of the Convoy (XML2 T6-4C):
(And: No, the battery is not the limiting factor here.)

Low: 57 mA
Mid: 430mA
High: 1049mA

As opposed to my similar looking (different driver, though) Eagle Eye X2 (with a XM-L T6 U2-1A) emitter. (That I use with a 3100mAh 18650 cell.)

Low: 254mA
Mid: 1224mA
High: 1980mA (no wonder this thing gets hot!)

Bottom line: The combination of this LED and driver seems great for the small cell. I especially like the low light mode, which should last for about 15 hours with the 900mAh cell The XML2's improved efficiency over the older XML is very well used in this scenario.

PS: The Convoy  S2+ also works great with a CR123 cell.
PPS: To change between 3 and 5 modes (incl. strobe / SOS), switch the light off briefly after it has flickered in low-power mode.