Bosch D6600
Native Integration Available
This integration requires a Class 3 License and a Device Server. Please contact your account manager for more details.
Native Integrations Supported Features
- Alarms
Network Requirements
From |
To |
Port |
Use |
Bosch D6600 Receiver |
Device Server |
7700 UDP |
For receiving heartbeats and alarms |
Device Server
|
Bosch D6600 Receiver |
7700 UDP |
For responding to heartbeats and alarms |
Configuring Your Device
Native Integration - Device Setup
In Bosch D6600
- The Bosch D6600 Receiver must be set to "SIA" mode ("D6500" mode is NOT supported).
- A Serial-to-Ethernet converter must be attached to each receiver and configured as per the 'Network Communications' section of the D6600 manual - baud rate 38400 using UDP mode.
- Panels must be set to send either "Contact ID" or "SIA" format signals (other formats are NOT supported).
Having connected and configured the Receiver with a Serial-to-Ethernet converter as described in the 'Network Communications' section of the D6600 manual, next configure the Receiver to send its data to the IP of the On-Premise Device Server as the "Automation Network Connection" (menu option "6.3.1" - refer to the D6600 manual).
In SureView
Using the SureView Advanced Device Setup add "Bosch D6600" to the to your relevant Area using the following fields
Host | IP Address of the Bosch D6600 Receiver |
Port | 7700 |
Username | leave blank |
Password | leave blank |
Extra value |
{ServerId:xxx,AlarmCodesWithUser:"401, 402, 451, 452, 456, 457, 458, 459, 462, 463, 464, 421, 422, 429, 430, 574, 604, 605, 607, 625, 642, NriAB, NidDA, NDA, NDB, NidDB, Nri/idDY, Nri/idDC, Nri/idDO, NriFI, Nri/idCM, Nri/idNM, NidRO, NidRC",AlarmCodesSystem:"602"} |
Go to the Alarms Tab in your Device Setup screen and add your alarm points.
Inut1 |
Enter a unique number for each individual alarm point. Starting at '1' and increasing for each alarm. |
Input2 | -1 |
Extra value |
accountnumber_linenumber_boschinput1_boschinput2 example |
Troubleshooting
Not receiving alarms in Sureview
If you are not receiving alarms, check the following points:
- Have you done the steps in above?
- Is the receiver configured to send its alarms to the IP address of your Device Server?
- Can the Device Server ping the Receiver? If it can't then the two cannot communicate with each other on the network.
- If you run the Simulation software on your Device Server (you will need to stop the Sureview Bosch Receiver service) do you receive alarms? If this does not work then your receiver is not configured properly.
- If you are seeing System.Net.Sockets.SocketException errors in the trace output which state
The requested address is not valid in its context
then it is likely you may have set the wrong value in the NetworkInterface section of the exe.config file
Outgoing network interface
The Bosch receiver expects replies and acknowledgements to come from the same IP address that it is sending its alarms to. If you have a server with more than one connected network card you will need to ensure that the Bosch Service is replying on the same interface as it is receiving on. As such, this means that the Bosch receivers cannot be load balanced.
To do this, edit SVBoschReceiver.exe.config and enter the IP address of your network interface in the NetworkInterface setting. Note: A blank value means it will choose your default network card. This is fine on a server with only one connected network interface.
Comments
0 commentsPlease sign in to leave a comment.