How can I interface Pysae with the Hanover SIV via a WIFI router?

Pysae is able to control the Passenger Information System (PIS) on board vehicles via a wireless connection based on the use of a WIFI/4G router.

This allows the driver's entry into service on the AVM to be shared with the SIV. This limits the number of manipulations the driver has to make on the on-board systems, and saves drivers precious time

💡Principle

Pooling the driver's service entry means that the service entry can be transmitted directly via Pysae to the Hanover FSS.

The information needed to operate the Hanover SIV is thus transmitted by the AVM: Pysae sends the SIV an "SIV code", a unique identifier attached to a journey which enables it to be recognised.

Automating the sending of SIV codes by Pysae makes the operation of the various systems more reliable and reduces the risk of errors.

🔍Technical requirements

You must have the following equipment:

Hanover Eric+, EG3 or DG3 Girouette console
Smartphone or tablet
Mounting bracket
Data connection
4G Wifi router (to act as a gateway between the various on-board equipment)

📝Transport plan and required fields

Ensure that your transport plans (in GTFS format) are identical in your Pysae and Hanover solutions. It is possible to retrieve the GTFS published in Pysae via the Transport Plan API.

The connector transmits all the following information each time a field is updated:

agency_id: The race agency.
block_id: The service of the journey
current_status: The status of the journey. Can be one of the following values:
"STOPPED_AT": at a standstill.
"IN_TRANSIT_TO": to stop.
"INCOMING_AT": approaching the stop.
current_stop_id: The stop identifier indicated by the status. This is the stop_id of the stop in GTFS.
current_stop_sequence: Number. The stop_sequence of the stop indicated by the status; this is the stop's rank in the race.
direction_id: The direction of the race
fleet_number: The fleet number of the vehicle, in the form of a character string.
route_id: The identifier of the line in the race
route_short_name: The short name of the line referenced by route_id
shape_id: The identifier of the race route
staff_number: The staff number of the driver, in the form of a character string
trip_id: The race identifier
trip_short_name: The short name of the race
ts : Number. UNIX timestamp (in seconds) indicating the time at which this message was created.

💻Configuration in Pysae

1/ Activate Hannover

Go to the "Integrations" section at the bottom left.

Click on the "Activate" button in the corresponding box.

Select "TCP/IP" in the "Serial" box

2/ Adding the connection IP for the TCP/IP port

The connection IP is the IP address used to configure the 4G routers that will power the connection between Pysae and Hanover. You should ask your 4G provider for this address.

The TCP/IP port to be specified depends on your Internet Service Provider (ISP). You should contact your ISP to obtain this information. The default setting is 33335.

Don't forget to click on the "Save" button.

3/ Toe-up code for the SIV console

To change the code for the toe-in phases as set, go to the "Settings" tab and click on "Driver application".