This page contains answers to questions that have been asked by customers several times (more than once).
The page is constantly updated.
Where can I find the latest documentation?
The newest documentation is always here.
This documentation website is the only place where you can find up-to-date technical information about our products.
We will update this content regularly to improve information and to make things simpler. So we ask you to read this information first.
Where can I get technical support?
- If you purchased the product from a Reseller or as Part of a Project please contact your Reseller or Project Partner first.
- If you purchased the product directly from Parametric use our Support Inquiry Form to contact us.
- Book a Premium Remote Support Session
Why I do not get an answer within hours?
At Parametric, customers are supported directly by a small team of engineers.
Support is provided alongside the actual engineering activities. This can take a little longer. The answers are usually target-oriented. For this reason, we cannot offer telephone support without prior appointment.
How to get technical support faster?
There is a Premium Remote Support offer.
You can book a support session directly in the calendar of the support team. An engineer will contact you at the requested time to solve your issues remotely. This service can be paid conveniently with Paypal or Credit Cards.
This service is limited to products and services provided by Parametric. If there are problems with third-party products, services or software (including problems with Windows), we can help isolate them. There is no guarantee that every problem will be solved. In some cases an analysis or repair in our service center may be necessary.
What is LoRaWAN®?
The LoRaWAN® specification is a Low Power, Wide Area (LPWAN) networking protocol designed to wirelessly connect low energy devices to the internet in regional, national or global networks, and targets key Internet of Things (IoT) requirements such as bi-directional communication, end-to-end security, mobility and localization services. Read more...
Do I need a LoRaWAN® ?
TCR and PCR2 are connected devices used for live data applications. The LoRaWAN® connection is used to transmit data to a server at regular intervals having a real time coverage of the traffic situation.
Do I need to run my own LoRaWAN® ?
There are professional LoRaWAN® Networks Providers with fully managed offerings including support. Ask Google to find such a provider in your area.
Should I operate my own private LoRaWAN®?
It is possible to run private LoRaWAN® networks including own LNS and Gateways. Although we really do not recommend it and won't be able to support it. If there is no professional provider in your area this might be the only option to operate TCR traffic counters.
Take following advice based on our experiences:
- Use only quality LoRaWAN Gateways from famous manufacturers such as Tektelic or Kerlink.
- Use Loriot Free Community Public Server to get started. Later you can switch to Professional Offering. Loriot.io is good software. We did not see major issues so far.
Can I use collaborative LoRaWAN® networks?
We do not recommend using community operated LoRaWAN® networks for professional applications. (Would you like to fly to mars with a RaspberryPI controlled rocket!?)
Why we do not recommed it?
- There is nobody you can contact except "the community".
- Coverage of community networks is not guaranteed. Gateways can be switched on or off at any time changing the whole coverage map.
- Usually these networks are based on very limited hardware.
- Limited knowledge on building wireless networks including the selection of suitable locations and antenna optimization.
Can I use The Things Network (TTN)?
Technically yes, but we do not recommended it.
The Things Network (TTN) is the free community network, that’s mainly operated by TTI on best effort.
There is a Fair Use Policy which limits the uplink airtime to 30 seconds per day (24 hours) per node and the downlink messages to 10 messages per day (24 hours) per node.
You may get support from volunteers, at the TTN forum but they cannot access the network servers to analyze or fix anything.
Due to TTN is very limited we do not recommend using it together with our products because it restricts the functional potential.
Do you provide payload decoder example code?
We have a public repository where you can download a payload decoder code examples as a starting point to write your own decoder.
What is the shortest uplink interval?
TCR devices transfer counter data in regular intervals.
Depending on the LoRaWAN region, it may not be possible to transmit as often as desired. A reasonable value is 10min. This means that 6 messages are sent per hour. You can use this Airtime Calculator to find the limitations in your region. Use payload size=10.
TTN is very limited due to the fair use policy. Max. 20msg/24hour (Payload size = 10) in the EUR868 region.
How do I change the device settings?
For the initial configuration we recommend using the PPX Setup Tool.
Alternatively, the command line interface CLI can also be used. For large deployments, it would even be worthwhile to write a few Python scripts using the CLI to configure the devices automatically.
When the devices are rolled out, the settings can be changed remotely via LoRaWAN® Downlinks.
Where can I find the LoRaWAN® keys?
You find the LoRaWAN® Keys Slip on the inside of the box. This slip is printed out during the production of the device and contains device-specific data.
Can I protect the settings from unauthorized access??
Starting with TCR Firmware V2.2 you can lock the settings with a PIN code. See the CLI Documentation for details.
What does RTL and LTR mean?
TCRs are bidirectional traffic counters that must be placed to the side of the object movement.
- RTL means from right-to-left
- LTR means from left-to-right
The directional indications are meant from the viewer's perspective towards the LEDs located under the service lid. Never the "view of the device" towards the road.
Device does not join. What can I do?
Step 1: Check the device type first
If the device type is just TCR-xx without a LoRaWAN® region, you should set the LoRaWAN® region using the command line interface (CLI)
|LoRaWAN® Region||CLI command|
Always use the
savecommand to store changes permanently into device's ROM.
Check device type with
get typestrat the end.
Step 2: Check Keys
Check if you entered the right keys.
You can always read out LoRaWAN® keys from the device by using PPX or the CLI. Or you overwrite the AppEUI and AppKey with your own.
Step 3: Check Connectivity Settings
TCR uses following network parameters per default:
- LoRaWAN® 1.0.3
- ADR On
See Device Datasheet for more detailed information.
ALL PRODUCT, PRODUCT SPECIFICATIONS AND DATA ARE SUBJECT TO CHANGE WITHOUT NOTICE TO IMPROVE RELIABILITY, FUNCTION OR DESIGN OR OTHERWISE.
Parametric GmbH, its affiliates, agents, and employees, and all persons acting on its or their behalf (collectively, “Parametric”), disclaim any and all liability for any errors, inaccuracies or incompleteness contained in any datasheet or in any other disclosure relating to any product.
Parametric 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, Parametric 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 Parametric'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 Parametric of any of the products, services or opinions of the corporation, organization or individual associated with the third-party website. Parametric 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, Parametric 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 Parametric product could result in personal injury or death. Customers using or selling Parametric products not expressly indicated for use in such applications do so at their own risk. Please contact authorized Parametric 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 Parametric. Product names and markings noted herein may be trademarks of their respective owners