| Info |
|---|
Tenkt å være en trinnvis guide til hvordan koble opp ... Er den nødvendig? |
In order to connect to Ruter Vehicle API, there are some preparations that need to be done:
...
You need to be a PTO or other operator/integrator already under a contractual agreement with Ruter to register for access to the Vehicle API. If that is taken care of, contact us at dummyadresse@ruterrdp-support@ruter.no for connection details.
Ensure vehicle compliance
Your vehicles need to comply with the following minimum requirements to be allowed acces to the Vehicle API. More detailed requirements are coming soon.
- Technical installations in the vehicle must comply with ITxPT specification S01
- Services in the vehicle must comply with ITxPT specification S02.
- The vehicle must bridge all necessary MQTT topics over the air to and from Ruter's MQTT endpoint withiut without delay.
- The vehicle must identify at all times with the Vehicle Identification Number (VIN).
- To utilise the DPI service, all isplays displays in the vehicle need to comply to the approved display sizes, resolutions and form factors.
Site to site compliance
All consumers Users of the Vehicle API need to can give Ruter access to their Vehicle and Equipment Registry (VER) through a REST API. This API should be structured according to Ruter's latest schema.
...
All transmitted data must validate against Ruter's Over-The-Air schemas.
Which data to transmit to Ruter?
The basic requirement is to continually (every 1-2 seconds) transmit vehiclke positions as Code Block avl/json . At the start of a service, the block to be serviced needs to be trsansmitted along with the Vehicle ID in aa signon/json telegram. .
Related articles
| Filter by label (Content by label) | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
If the signon is accepted, you will start to receive DPI message as the vehicle moves along the upcoming journeys.