Professional Documents
Culture Documents
VoyagerMulti 5.6.1.26 - Release Bulletin
VoyagerMulti 5.6.1.26 - Release Bulletin
Issue 1
It applies to:
General Release
Contents
Firmware Release Bulletin 1
Tema-Voyager Multi rel 5.6.1.26 1
Contents 1
Features available starting Tema-Voyager Multi 5.6.1.26 2
Features and Issues available starting Tema-Voyager Multi 5.6.1.18 2
Features and Issues available starting Tema-Voyager Multi 5.6.1.01 4
Features and Issues available starting Tema-Voyager Multi 5.6.0.17 5
Features and Issues available starting Tema-Voyager Multi 5.6.0.16 5
Features and Issues available starting Tema-Voyager Multi 5.6.0.13 5
RFC/Enhancement included 8
ISRs / Trouble Reports Resolved 9
Tema-Voyager Multi Limits 13
Compatibility 15
Localization 15
On-line help 15
Notes on downloading firmware 15
Supporting Web Sites and Details 16
HONEYWELL CONFIDENTIAL & PROPRIETARY. This work contains valuable, confidential, and proprietary information. Disclosure, use,
or reproduction outside of Honeywell International is prohibited except as authorized in writing. This unpublished work is protected by
the laws of the United States and other countries.
HONEYWELL DISCLAIMS THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PURPOSE AND MAKES NO
EXPRESS WARRANTIES EXCEPT AS MAY BE STATED IN ITS WRITTEN AGREEMENT WITH AND FOR ITS CUSTOMER.
In no event is Honeywell liable to anyone for any direct, special, or consequential damages. The information and specification in this
document are subject to change without notice.
Patents Pending.
This bulletin introduces the new Tema-Voyager Multi release 5.6.1.26
*NOTE – To use WEB pages need to have at least TLS1.2 enable in Internet Explorer options
Internet ExplorerInternet OptionsAdvancedSecurity, set the flag “Use TLS 1.2”
*Note: To use this firmware, it’s required to update EBI to release EBI 500.1 + Temaline 5.7 Update 3 or higher
*Warning: When downloading this firmware in a Multi Controller with release 5.6.0.x, the reset database is
automatically executed.
Default Certificate
Device is provided with default self-signed certificate, with the adequate security parameters for the site
operation. However, the customer is requested to procure the signed certificate from their certification
Authority (CA).
CA Certificate
This combination of key and algorithm, is to be considered while procuring the certificate.
RSA 2048 bit with SHA256
New statistics on the RS485-OSDP communication to help people to correctly install the OSDP reader.
Wit Multi WEB pages, in the section Device Connection, you can have the statistics of the OSDP lines
2 www.honeywell.com
www.honeywell.com 3
Table 1 Connection status/quality:
Reader Reader number (from 0 to 3)
Addr RS485 phisical address
Speed Speed of the RS485 connection
State Online/Offline
CON Connection status ( X-Active O-Inactive)
SEC Scure channel status ( X-Active O-Inactive)
TPR Reader Tamper Status ( X-Active O-Inactive)
PWF Power Fail Status ( X-Active O-Inactive)
CON AC Connection attempt count
SC FC Secure channel fail count
New flag on WEB pages to disable the text management. Some Biometric OSDP readers with display, will show junk
characters
4 www.honeywell.com
Features and Issues available starting Tema-Voyager Multi 5.6.0.17
The communication between EBI-Tema supervision center and Tema-Voyager Multi devices is encrypted, by default,
using AES algorithm (keys are 256-bit length) with dynamic exchange of the session key.
It is not possible to disable the encryption, this means that the system always works with the Host communication
encrypted
It’s possible to change the number of readers, changing the license file in the Voyager Multi memory, using Voyager
Multi web pages, unless for Tema-Voyager Multi-0 that use a different HW and cannot be updated.
For more details see the bulletin “PB-686 Tema-Voyager Multi license upgrade”, available on the EBI Global Support
Site
The Tema-Voyager Multi is a new controller within Temaline family that offers the management of a limited number of
doors together with high security.
The Tema-Voyager Multi can be connected with Peer-to-Peer communication with other Tema-Voyager Compact
and Temaline devices to ensure complete autonomy even in case of failure at the supervisory level.
www.honeywell.com 5
The Tema-Voyager Multi offers in a single device both a controller as well as the readers connection and the I/O
management.
The Tema-Voyager Multi can connect up to 4 readers (Wiegand or RS485 via OSDP protocol) to manage 4 Single
Side Doors or 2 Double Side Doors.
The Tema-Voyager Multi can handle 4 fixed input, 4 fixed output and 8 configurable Input/output
In addition is also available the model to only manage I/O
The Tema-Voyager Multi is available with different number of readers that can be connected
Single- Double-
side door side door
1 reader + Inputs Outputs Flexible I/O
1 REX 2 readers
Tema-Voyager Multi-0 0 0 4 4 8
Tema-Voyager Multi-1 1 0 4 4 8
2 0 4 4 8
Tema-Voyager Multi-2 0 1 4 4 8
3 0 4 4 8
Tema-Voyager Multi-3 1 1 4 4 8
4 0 4 4 8
3 0 4 4 8
Tema-Voyager Multi-4 2 1 4 4 8
0 2 4 4 8
6 www.honeywell.com
Simplified connection via POE & POE+ with possibility to manage the unlock up to 2 doors (POE+ only) with
optional Internal relay Board
Wall or DIN rail mounting
Tamper resistant (anti opening)
Dimensions (W x H x D) 240*140*60mm
Supply voltage : 10-30VDC or POE/POE+
Protection IP32 level
WEB Interface for configuration with HTTPS protocol (Telnet no more available)
The Tema-Voyager Multi checks the power supply of the Wiegand connection to identify if there is a short or
a cut. If a short or a cut is identified the Tema-Voyager Multi sends an alarm to the supervisory center. In
addition also the tamper of the reader connected on the Wiegand is checked and an alarm sent to
supervisory level
The Tema-Voyager Multi connected to a POE+ LAN, allows to fully managing the un-lock of the doors
without any additional Power Supply but simply using the optional relay output board. The number of locks
managed depends of course from the power required.
The optional Emergency Relay Output Board allows the Tema-Voyager Multi to interrupt the power supply to
doors when connected via POE+, in case an emergency alarm is raised (typically fire alarm).
www.honeywell.com 7
OSDP Reader supported
For the list of OSDP readers can be connected to Voyager Multi, please check the bulletin “PB-747 OSDP Readers
for Voyager Multi”, available on the EBI Global Support site.
RFC/Enhancement included
8 www.honeywell.com
ISRs / Trouble Reports Resolved
Resolved in:
ISR# Description
5.6.1.26
219439 Vulnerability Analysis points
When you disconnect OSDP reader #1, sometimes you have 5.6.1.25
215765
alarm also in reader #2
5.6.1.24
219390 After input re-arm, the input stay normal
5.6.1.24
219484 OSDP reader goes of line after some time
5.6.1.24
219548 After input re-enable, the input stay normal
5.6.1.24
214728 Login in with WEB Pages clear the input anomaly alarm
Flood up the EBI event summary with the message "Reset 5.6.1.22
213174
maximum number of"
5.6.1.21
218547 When supervised input detects CUT alarm, buzzer is not enabled
5.6.1.21
215820 After reset db the technical alarm is cleared
Need to remove the timeout on same card reading from web 5.6.1.21
216000
pages
5.6.1.21
217449 Double reading feedback doesn't work if the door is open
5.6.1.20
215667 Once chexhit alarm DI activated, it reseted immediately
When we are using valid pin no. to open the door, power coming 5.6.1.20
215679
back immediately to the lock if pulse duration is 0.
[Chexit Gate] - Pulse output is not deactivating even when user 5.6.1.20
215445
closes the door after the door left open alarm
Gateway forced open beep sound is not stopping when we trigger 5.6.1.20
216040
the Unlock door command from page in Door Open state
Chexit gate, the status need to return to gateway opened after 5.6.1.20
216148
door closing
[Chexit Door] - Pulse output is not turning off even after 5.6.1.20
216150
deactivated the emergency input from field
213881 Need to have the statistics on the RS485-OSDP communication to 5.6.1.18
help people to correctly install the OSDP reader
Boarding gate kept open if reader swapped for one transit while 5.6.1.17
215309
door is kept open
Door Point Detail Display do not have Unlock button for Boarding 5.6.1.17
214915
gate type 2
The reader is not responding to pin entry after unlock the door for 5.6.1.17
214957
one transit from Point Detail Display pages
Chexit gate, the status need to return to gateway opened after 5.6.1.17
214939
door closing
5.6.1.17
214940 Chexit gate: pin only should work also with emergecy input on
Door with Maglock, the unlock gate command should keep the 5.6.1.17
214914
output always on
If the boarding is been started from the EBI Point Detail Display, 5.6.1.17
214791
the gate busy state is not set
5.6.1.13
213674 Unwanted logging info for flexible inputs
5.6.1.12
210372 Door do not relock properly for Flap Door type 2
www.honeywell.com 9
5.6.1.11
214478 Temaline Voyager Multi - Maglock Relock Issue
5.6.1.11
213225 Remove the zeroes in the card number when sent as a parameter
Chexit gate: need to reset emergency on valid card reading. 5.6.1.10
214481 To have this feature you need to set the flag “Chexit Card read in
Emergency” with Multi Web pages, section Application Status
Output I/O not properly working for Unlock gate for entry / exit 5.6.1.10
214491
command executed from double side airport Boarding gate
Lock for entry / Lock for exit needs to be ignored while Boarding in 5.6.1.10
214494
Double Side Airport Boarding gate
Voyager Multi and Compact do not manage the status "Gate Left 5.6.1.09
212736
Open"
DSD with boarding door type 2, lock power does not return back 5.6.1.09
214250
until door closed (for exit reader)
5.6.1.08
213215 Delay configured in gate not working as expected
5.6.1.08
213706 Double read with Authorized function not working as intended
5.6.1.08
213590 Missing information about input anomaly
Wrong behavior of the output/led for Flap door type 2 (OSDP or 5.6.1.07
213507
Wiegand)
HID OSDP reader not detected if Multi starts with the reader 5.6.1.07
205765
disconnected, and alarm not send if cable removed
5.6.1.06
213507 Wrong behavior of the output/led for Flap door type2
Lock command and Open command must be rejected during 5.6.1.06
213538
boarding
REX button presses 2 times very close to each other(<1 sec) 5.6.1.06
213536
causes the hanging issue
After Valid normal Transit with Gate Not shut alarm, Boarding 5.6.1.06
213224 cannot be started from field (But it is working when we start
boarding from door PDD)
Door do not relock preperly for Flap Door type 2 5.6.1.06
210372
10 www.honeywell.com
Need to have a configuration flag to avoid to send text to OSDP 5.6.1.01
211504 reader with text support (to avoid junk characters on Biometric
reader with display)
Even though we show valid card, sometimes the LED stays in 5.6.0.28
211157
RED (For both DSD/SSD - "Card + Pin" Mode)
Reader LED blinking wrongly while waiting for pin in chexit door 5.6.0.28
211116
with card + pin transit procedure
Multi do not manage the keepalive message of the Wiegand 5.6.0.25
209777
reader
Voyager Multi goes hanging when we use the door type as "Chexit 5.6.0.25
210287
door" for some of the scenarios
210794 Sometime Multi lose the communication with OSDP reader 2,3,4 5.6.0.24
www.honeywell.com 11
Tema Multi readers getting disconnected from the EBI with 5.6.0.24
210341
Encryption Key Mismatch
210823 Some OSDP Readers glow in Blue color after Power on 5.6.0.24
In case of a door set with "Pin Only" Transit Procedure, when the 5.6.0.24
196801 PIN is entered, the Green LED glows in the Exit reader, which is
meant for the Entry Reader LED
In Voyager Multi, Card only mode (DSD), If the card shown in 5.6.0.24
210824
Entry side, Exit Reader LED is glowing Green.
209211 Double transit not working when card number >32 bit 5.6.0.23
HID reader with encryption doesn't work in position 1 when all 4 5.6.0.22
208210
readers are configured for OSDP
After Card reading, before to complete the pin, the green led is not 5.6.0.21
209714
blinking (Wiegand interface)
The feedback associated to the transit executed in exit for double 5.6.0.20
209086
door do not work
When HID OSDP reader with encryption is connected, the 5.6.0.19
207879
comunication do not start
Transit type wrongly updated as "AC" instead of "AC,SAP" for 5.6.0.18
200354
SAP Cards
Status of Encrypted peer controller is shown as Not encrypted(NE) 5.6.0.18
202648
in other peer controller when some controller goes offline
Voyager Multi controllers reboots continously when Peer to Peer 5.6.0.18
202526
encryption is enabled
Optimized the flash erase procedure after resetdb to reduce the 5.6.0.16
--
reset database total time.
If the trace tool needs to be used to debug an issue present on the 5.6.0.15
195989 device and no one configured previously the Log Server address
to be used, there is the risk to lose the issue because to set the
Log server address it is required to reboot the device.
Disabling & enabling the reader buzzer triggers continues 5.6.0.15
197462
sounding in RPK40 OSDP readers
Feedbacks on “Double card reading” are not executed when the 5.6.0.15
186999
door is in Emergency status
5.6.0.15
183301 Time synchronisation based on Custom Rule is not working
186708 5.6.0.15
In Voyager Multi, some gate types are not developed
199357 5.6.0.15
more than one transits happens within transit timeout when door is
put under emergency without enabling transit on another transit
12 www.honeywell.com
Card+Pin in DSD not denying transit for first cardholder when 5.6.0.15
198173 second cardholder enter valid transit before first card holder enter
the pin
Event for the first getting missed in Card + Pin mode with during 5.6.0.15
198536 transit with 3 different users
In Card+Pin mode, No event for first card holder when second 5.6.0.15
card is immediately shown after valid pin completion for the first
198462 card
5.6.0.15
[DIT] Sometime Transit is getting terminated in Card+Pin scenario
191038
191054 Sometimes Transits are not reported in EBI in Card+pin scenario 5.6.0.15
If temakey is enabled for card+pin and selected for "Allow transit 5.6.0.15
190846 on transit function". The user gets pin entry timeout as per the
timeout configured for for the temakey.
Max 512 Voyager Multi devices per EBI (this number is reduced if you also have some TemaServers and/or Tema
Voyager Compact installed).
The number of max cardholders and max number of behaviors associated to any cardholder can be assigned changing
the memory formatting:
www.honeywell.com 13
14 www.honeywell.com
Compatibility
Localization
No localization required.
Manuals
On-line help
You can access Voyager Multi Web Interface Guide by clicking the ? on the web page. The Help file will be
displayed, if the EBI server is on line and connected to the TS2. The help file is included in the directory
..\honeywell\EBI_Tema\Webstation\help\TSHelp.
www.honeywell.com 15
Supporting Web Sites and Details
http://www.temaline.honeywell.com
https://honeywellprod.sharepoint.com/teams/hbs-EBIHome
This web site requires a user ID for logon. To get a User ID click the Register link. Usually you will receive a
response within 24 hours. This site provides invaluable information and training primarily for Technicians, but it is
also useful to Sales personnel.
16 www.honeywell.com