TCR Command Line Interface

V2.2 | V2.1 | V2.0 | V1.3 | V1.1 | V1.0

Introduction

This manual describes the command line interface (CLI) of Parametric TCR traffic counters with LoRaWAN. CLI is used for initial setup of the device. Alternatively you can use the PPX Product Explorer for setting up your device.

CR LF Line Endings

All commands are terminated by a CR (\r) and LF (\n) ASCII symbol.

For the sake of clarity, we refrain from adding '\r\n' to each command.

Set & Get Commands

Device settings can be changed by a set and get commands, as well as a few control commands such as restart.

Range Checks

All supplied arguments are range checked and truncated if necessary.

Example:

set interval 2000    // 2000 is not OK
1440                 // value will be truncated 

set interval 10      // 10 is OK 
10

save

Save & Apply Changes

All changes to device settings need to be stored in internal ROM. This is done by using the save command.

Some changes will be active only after a device restart by a power cycle or by sending the restart command.

Example:

lora set interval 5
5

save
ok

restart

Command List

The complete list of supported CLI commands. help prints the same list to the console.

Status Commands

Application Settings

Commands to change common application settings.

Traffic Category Settings

Settings to configure traffic categorization. This includes object size and speed of an object. If both values are in the defined range, the object will marked to be cat P, A, B or C.

P (People)

Commands used to configure people detection.

A (Two-Wheelers)

Commands used to configure two-wheeler detection (bikes, motocycles, scooters)

B (Cars)

Commands used to configure detection of cars.

C (HGV)

Commands used to configure detection of heavy goods vehicules (trucks, lorries)

Radar Settings

Use these settings to fine tune radar module.

LoRaWAN® Settings

LoRaWAN® Status

These commands are useful to debug the LoRaWAN® connection

Device Control

Using a Terminal Emulator

You could use a terminal emulator such as RealTerm to open the serial connection and send/receive commands.

Serial Port Settings

• Baudrate: 19200
• Data Bits: 8usb_t
• Parity: None
• Stop Bits: 1

Terminal Emulator Settings: - Append CRLF

Examples

Typical device setup

This example shows a typical setup of a TCR counting traffic on a two direction street.

• We want to have data every 10min
• LoRaWAN® application key is changed
• Traffic from right (RTL) is in 3.4m distance (nearer lane)
• Traffic from left (LTR) is in 6.5m distance (farer lane)
• Sensitivity we set to 100% as a starting point
• At the end we save the changes to ROM and restart the device

> lora set interval 10
10

> lora set appkey AE64E7C8AB5745AAA7E328CA781B54E6
AE64E7C8AB5745AAA7E328CA781B54E6

> radar set rtldist 340
340

> radar set ltrdist 650
650

> radar set sens 100
100

> save
ok

> restart

Disclaimer

ALL PRODUCT, PRODUCT SPECIFICATIONS AND DATA ARE SUBJECT TO CHANGE WITHOUT NOTICE TO IMPROVE RELIABILITY, FUNCTION OR DESIGN OR OTHERWISE.

PMY Systems AG, its affiliates, agents, and employees, and all persons acting on its or their behalf (collectively, "PMX"), disclaim any and all liability for any errors, inaccuracies or incompleteness contained in any datasheet or in any other disclosure relating to any product.

PMX makes no warranty, representation or guarantee regarding the suitability of the products for any particular purpose or the continuing production of any product. To the maximum extent permitted by applicable law, PMX disclaims (i) any and all liability arising out of the application or use of any product, (ii) any and all liability, including without limitation special, consequential or incidental damages, and (iii) any and all implied warranties, including warranties of fitness for particular purpose, non-infringement and merchantability.

Statements regarding the suitability of products for certain types of applications are based on PMX's knowledge of typical requirements that are often placed on Paramtric products in generic applications. Such statements are not binding statements about the suitability of products for a particular application. It is the customer's responsibility to validate that a particular product with the properties described in the product specification is suitable for use in a particular application. Parameters provided in datasheets and / or specifications may vary in different applications and performance may vary over time. All operating parameters, including typical parameters, must be validated for each customer application by the customer's technical experts. Product specifications do not expand or otherwise modify Paramtric's terms and conditions of purchase, including but not limited to the warranty expressed therein.

Hyperlinks may direct users to third-party websites. These links are provided as a convenience and for informational purposes only. Inclusion of these hyperlinks does not constitute an endorsement or an approval by PMX of any of the products, services or opinions of the corporation, organization or individual associated with the third-party website. PMX disclaims any and all liability and bears no responsibility for the accuracy, legality or content of the third-party website or for that of subsequent links.

Except as expressly indicated in writing, PMX products are not designed for use in medical, life-saving, or life-sustaining applications or for any other application in which the failure of the PMX product could result in personal injury or death. Customers using or selling PMX products not expressly indicated for use in such applications do so at their own risk. Please contact authorized PMX personnel to obtain written terms and conditions regarding products designed for such applications.

No license, express or implied, by estoppel or otherwise, to any intellectual property rights is granted by this document or by any conduct of PMX. Product names and markings noted herein may be trademarks of their respective owners