Paul Austen - 2012-09-04

Looks like the data from the CM160 device is not what is expected.

If you can reproduce this problem could you post the cm160server.log when running the following (enables debug)

cm160server -d > /tmp/cm160server.log

Regards

Paul