Skip to main content
All Collections🔗Connectors and interfacesOn-board equipment
How can I interface Pysae with the Hanover SIV via a wired connector?
How can I interface Pysae with the Hanover SIV via a wired connector?
A
Written by Antoine Marin
Updated over 4 months ago

Contents

💡Principle

Mutualisation of the driver's service entry allows the service entry to be transmitted directly via Pysae to the Hanover SIV.

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

The Hanover Eric+, EG3 or DG3 windvane consoles and the Hanover HTC SIV computer can be wired to Pysae.

You need the following equipment:

Hanover Eric+, EG3 or DG3 windvane consoles

  • Hanover HTC SIV calculator (optional: only if you need to connect your audible and visual announcement systems to the Pysae SAE)

  • Smartphone or tablet

  • Mounting bracket

  • Data connection

  • 3-port cable with RS232 serial output, micro-USB port and USB port

  • DB9 (F) <> DB25 (M) cable

🔌Installation

There are two on-board architecture schemes depending on the wiring chosen:

  • Eric+, EG3 or DG3 destination sign console

  • SIV HTC computer

The destination sign code or run code must be entered in the transport plan for each run in the ext_pis_code field.

The port used on the console is 2. Port 2 must be configured as GTMH-1. The RM configuration option must be activated (1) and the auto destination code must be entered (0000) or forced (see AM).

Connection with the Hanover Eric++ destination sign console

The connection between the Hanover Eric++ console and the PYSAE smartphone or tablet is made via a FT312D-based serial cable (e.g. StarTech ICUSBANDR232).

The RS232 serial port of the serial cable is connected to the DB25 "Multicomms" port of the console with a DB9 (F) <> DB25 (M) cable. This cable has the following connections:

| Nom | pin DB9 (F) | pin DB25 (M) |
| --- | ----------- | ------------ |
| GND | 5 | 23 |
| RXD | 2 | 12 |
| TXD | 3 | 10 |

Connection with the Hanover EG3 destination sign control panel

The Pysae solution can also be interfaced with the Hanover EG3 console.

For this model, the wiring diagram is as follows:

| Nom | pin DB9 (F) | pin mini fit 8 |
| --- | ----------- | -------------- |
| GND | 5 | 2 |
| RXD | 2 | 5 |
| TXD | 3 | 1 |

Wire colour correspondence:

  • GND: blue and white wire

  • RXD: green wire

  • TXD: blue wire

📝Transport plan and required fields

Make sure that your transport plans (in GTFS format) are identical in your Pysae and Hanover solutions. You can retrieve the GTFS published in Pysae via the Transport Plan API.

The destination sign code or run code must be entered in the transport plan for each run in the ext_pis_code field.

💻Configuration in Pysae

Go to the "Integrations" menu and click on "Activate" in the Hanover box.

In the "Type" section, activate the "Serial" box.

In the parameters at the top right, click on the "Driver application" section, then enter the code "Haut-le-Pied pour le pupitre SIV".

Don't forget to press the "Save" button.

Did this answer your question?