If you don’t find the answer you’re looking for, please contact our Support Team
Vehicle sensors installation and related costs
Q: What are the standard installation costs of Tinynode sensors?
A: Costs vary according to sensor type and installation method. If deploying more than 100 sensors, the following parameters normally apply:
A4 or A4-H sensors, glued to the asphalt Cost of gluing material: 2 EUR/sensor
Installation time: 2 minutes/sensor
A4 or A4-H sensors, screwed to the asphalt Cost of screws: 2.50 EUR/sensor
Installation time: 5 minutes/sensor
B4 or B4-H sensors Cost of resin: 8 EUR/sensor
Cost of core drilling: 30 EUR/sensor
Installation time: 10 minutes/sensor
Q: Which materials do you recommend for installation?
A: Tinynode recommends the following products:
For A4 and A4-H gluing Asphalt: Preco Cryl Kaltplastik 2K glue
Concrete: Preco Cryl Kaltplastik 2K glue, Triflex Grund L1K primer
For B4 and B4-H core drilling Asphalt: Triflex Cryl R 238 resin
Concrete: Triflex Cryl R 238 resin, Triflex Grund L1K primer
Q: How many sensors can a G4 gateway handle?
A: Tinynode’s G4 gateway can handle up to 100 sensors (A4, B4 or a mix of them). If your parking facility has more than 100 parking lots, you simply need to add as many gateways as needed, one every 100 sensors.
Q: How many repeaters and gateways are normally needed to equip a medium-sized parking area?
A: It depends on the type of installation and the density of parking lots. The following criteria normally apply:
On-street parking (low density parking area) 1 G4 Gateway per 100 A4 or B4 sensors
1 R4 Repeater per 10 A4 or B4 sensors
Off-street parking (ie. corporate, airport or shopping malls) 1 G4 Gateway per 100 A4 or B4 sensors
1 R4 Repeater per 15 A4 or B4 sensors
HGV/Truck parking 1 G4 Gateway per 100 A4 or B4 sensors
1 R4 Repeater per 15 A4 or B4 sensors
Integration with customer or third-party systems
Q: Which interface does Tinynode system propose? Do you have an API?
A: Our standard for the transmission of parking sensors information is a TCP/IP based REST interface. API specifications are available upon request.
Q: Which third-party systems are you compatible with?
A: Tinynode Wireless Vehicle Detection System API has been integrated in several back-office systems, including:
Golden River (Clearview Traffic Group) – Insight
Schick – Signal Park
Labocom – Mivisu
FRITZ – Car Park Management System
INEO – EffiPark
Cofiroute – DPPL
ASF – Mistral
Optifib – Optipark
Q: Do you propose your own back-office system?
A: A lightweight, cloud-based back-office system is available for pilot projects.
Q: I wish to use a 3G modem/router to transmit data from the parking area to the back office. Which device do you recommend?
A: We can recommend SIERRA’s LS 300.
Q: Can you estimate the amount of data generated by the system? And related costs?
A: To calculate data storage costs, please consider the system is generating about 3 MByte of data per parking lot per month. To calculate data transfer costs (ie. over a GSM/3G network), please consider about 17 MB per parking lot per month.
Those values may vary according to the number of parking events (free/busy variations) and the maximal allowed latency (cycle time).
Q: Does Tinynode wireless technology require an Internet access?
A: Except for pilot projects using Tinynode cloud-based back-office, Internet access is not needed.
Q: I wish to count vehicles entering or exiting an area by placing a Tinynode A4 or B4 sensor on the lane, as an inductive loop replacement. Will it work?
A: No, Tinynode sensors are fit for detecting parked vehicles, not moving ones. If you want to detect or classify moving vehicles, we recommend Golden River’s M100 product.
Q: I would like to distribute Tinynode products in my country. How should I apply?
A: We will be happy to review terms and conditions with your company. Please contact us for further information.