Release Notes for mtcdp-client:
------------------------------

Version : 0.0.5
Date : 3/30/11

1. Integrated the annex.proto version 0.1.3

2. Added support for SoftwareUpgradeStatus messages

3. Added support for aborting the software upgrade.

4. Added support for ClientConfig messages. This would allow change of hostname/port, send
   some stats periodically without RequestPackageDelivery.

Release Notes for mtcdp-client:
------------------------------

Version : 0.0.4
Date : 3/22/11

1. Fixed the software upgrade issue.

2. Changed the buffer allocations to dynamic and increased the size to 32768 from 4096.

3. Added support for AnnexVersion message.

4. Added support for dumping the protobuf messages on client when log-upto is set to 7.

5. Check for media card availability for software upgrades.

6. Added support for resuming software upgrade if connection lost in between.

Release Notes for mtcdp-client:
------------------------------

Version : 0.0.1
Date : 3/2/11

This notes details the usage of the mtcdp-client for remote management
which confirms to the annex protocol version 0.1.2.

The mtcdp-client uses the CoreCDP release 1.1.1 as the base for development.
The bitbake recipe used for building the mtcdp-client is 'rm-image'. If you
want to build the cdp release with the remote management client, after installing
the corecdp, build the rm-image using the command, 'bitbake rm-image'.


Usage: " PROGRAM_NAME " [ OPTIONS ... ]
where  OPTIONS := { 
         --host <host>
         --port <port>
         --vendor-id <vendor-id>
         --product-id <product-id>
         --device-id <device-id>
         --rpd-interval <(msecs - default 1000)>
         --log-upto <log-level (0-7)>
         --daemonize
         --sasl-username <username>
         --sasl-passwd <passwd>
         --sasl-realm <realm>
         --sasl-force-mech <mech>
         --ssl-method {none | ssl | tls}
         --verbose
         --help

host -> specify the remote management host server address

port -> specify the remote management host server port

vendor-id -> specify the vendor-id to be used in the messages
             this overwrites the vendor-id read either from EEPROM
             or the config file in /etc/mtcdp.

product-id -> specify the product-id to be used in the messages
             this overwrites the vendor-id read either from EEPROM
             or the config file in /etc/mtcdp.

device-id -> specify the device-id to be used in the messages
             this overwrites the vendor-id read either from EEPROM
             or the config file in /etc/mtcdp.

rpd-interval -> specify the interval in msecs for the sending the
                request package delivery messages from the client

log-upto -> specify the log level for messages (similar to syslog levels)

daemonize -> runs the client application as a daemon

sasl-username -> username to be used for secure connection

sasl-passwd -> password to be used for the secure connection

sasl-realm -> realm to be used for hashing the secure key

sasl-force-mech ->

ssl-method -> specify the secure mechanism - none, ssl or tsl.
              by default, the 'none' mechanism is used.

version -> specifies the version of the client application

help -> displays the usage menu

Typical invocation of the mtcdp-client would be:

annexcd --host 172.16.0.251 --sasl-username uip --sasl-passwd passwd --rpd-interval 2000

------------------------------------------------------------------------

GPS Details:
-----------

The mtcdp-client utilizes the venus-gps application for reporting the GPS
details to the server. To enable the mtcdp-client to send GPS information,
one needs to invoke the venus-gps application prior to invoking the client.

The typical usage of venus-gps application would be:

venus-gps --daemonize --udp-client 127.0.0.1:5446

To list more options of the venus-gps, enter "venus-gps --help".

------------------------------------------------------------------------

Software Upgrade Procedure:
--------------------------

To perform the software upgrade, create a folder 'files' and copy the
files uImage and roofs.jffs2 in it. Now generate a tar ball of this folder
and name it as 'cdp-firmware.tar.gz'. Use the annex protocol to transfer this
file to the MTCDP platfom and copy the extracted files to either the
'/var/volatile/flash-upgrade' or the 'media/card/flash-upgrade' folder
and reboot the system. On reboot, the system will erase the flash memory
and copy these files into the kernel and root filesystem partitions.

------------------------------------------------------------------------
