Copy
View this email in your browser

In this Newsletter:

  • Now you can integrate AgoraBee RFID reader to Aplicom A9 telematics device – identify and track your assets precisely
  • Administrate your vehicles even more easily with new Aplicom RDL Service Management API
  • G-protocol is the latest addition to Aplicom protocols – new features are more flexibly available
Now you can integrate AgoraBee RFID reader to Aplicom A9 telematics device – identify and track your assets precisely
AgoraBee products offer an easy and cost-efficient way to identify and track trailers, containers, work machines, tools and other assets. AgoraBee IXCODE reader device and Aplicom A9 telematics device are the professional solution to market demands where robustness
and reliability are requested. The Mobile Asset Tracking solution consists of AgoraBee tags and reader, Aplicom telematics device and back-end SW-platform.
Ultra-long battery-life AgoraBee tags are mounted on assets and read by the IXCODE reader. The tag  uses various sensors to monitor temperature, motion and asset-identification information. The AgoraBee IXCODE reader is connected via a serial interface to Aplicom A9 telematics device that receives  information about events related to the assets. Aplicom A9 transmits the received data on the serial port via the 2G/3G cellular mobile network to the back-end server. The application-SW of the back-end server keeps track and monitors the assets according to the user requirements.

Typical application areas using Aplicom A9 telematics with active AgoraBee readers and tags:
Benefits:
  • Precise identification and real-time positioning of your assets
  • Improved operational efficiency of assets through tracking
  • Increased security
  • Scalable and adaptable tracking solution
  • Reliable and proven technology from named suppliers with over 20 years’ experience
  • Several references already in operational use on 5 continents
  • Fast and professional technical support and service
www.agorabee.com
www.aplicom.com
Administrate your vehicles even more easily with new Aplicom RDL Service Management API
The Aplicom digital tachograph remote download service has new API (Application Programmers Interface) RDL Service Management API to make RDL service easy to integrate with partners’ and system providers’ systems. Managing vehicles and other service administrative tasks can be made available through the partner‘s own telematics backend system to minimise RDL service related administrative tasks. The API allows integration with partners’ own services to manage RDL related tasks that were previously undertaken in Aplicom RDL service web admin portal. 

The main tasks are the adding of vehicles to the service and managing their settings, such as download interval and data to be downloaded etc, in the RDL service. The API offers also new settings and features that previously were not available in the admin portal. 

The main API functions available are:
  • Adding and managing vehicles in the RDL service
  • Setting of RDL download parametres and schedules
  • Commanding RDL service
  • Getting status of latest downloads 
  • Monitoring company card servers and the status of company cards
G-protocol is the latest addition to Aplicom protocols –new features are more flexibly available
Maintaining backwards compatibility and compatibility across different products has always been essential to Aplicom. We are now introducing the new G-protocol for data groups in order to accommodate new functionalities into the unit without compromising current D-protocol compatibility.

D-protocol roots are highly visible in G-protocol. The main structure remains similar, but as D-protocol was intended and optimised for selecting individual smaller Data (hence D) items to be transferred, G-protocol focuses on transferring slightly larger data block or data Groups (hence G). In short, the G-protocol is a binary protocol in a compact format without metadata in the packet itself. A single packet size depends on used field selector and content; typically a single packet is only 50-100 bytes that allows up to 20 000 packets per consumed megabyte.

With A11 SW version 1.2.0 and onwards it is possible to use G-protocol for transferring telematics data. The possibility to use G-protocol will be introduced later for further products. For parser implementations it is highly recommended to take the version number and field selector into account in order to stay compatible with possible future additions. Due to similarities, enhancing your current parser to support also G-protocol is a straightforward and easy process. Did you know that it is even possible to configure A11 to use G-protocol or different versions of D-protocol? Well, it is possible to send both simultaneously and to various servers.