The topics covered are listed down the left column. The topics will take you to the FAQ bookmarker for that item. Other Resources are the F1 Help which also contains the User Manual and the Document Library on this website.
Topic / Issue
PC Errors / Config Errors
Alarms / Inputs
Reader / Keypads
The DSX-LAN-D is the latest in LAN communications
interface and can replace all older DSX-LAN modules.
The DSX-IP-HUB is a communication distribution
module allowing the Master to Communicate with the
Sub Controllers via IP without the use of PC
Master Software. These units are programmed with a
web browser. They have a default IP address of
192.168.1.25. The Links below are to the
installation and configuration documents. These new
LAN-D and HUB modules require the TX and RX Ports to
be the same in both the software and module.
DSX LAN-D and IP-Hub Upgrade and Factory Default Instructions
DSX-USB Communication Module Instructions includes loading the driver
DSX-LAN. The Link below will allow you to download the following files for programming the DSX-LAN Module: IPSetup.exe, LanModuleSerialSetup.exe, LanMod2.pdf.
DSX-LAN-M configuration - Here are the instructions for the DSX-LAN-M
Below is a link to the DSX Cable Specifications. Using the specified cables will prevent many problems. These are the cable specifications for all generations of DSX Hardware. Please see the link below for specific cables required for communications, readers & keypads, locks, inputs, transformers, elevators and LAN. These specified or equivalent cables are the only ones DSX will support. These are the cables tested with the system and approved by UL. "CAT_5"CAT 5/6 cable should only be used for network connections to the DSX-LAN module. IT SHOULD NEVER be used for anything else. It will not function properly for panel communications. DSX Cable Specifications
No Communication to the
Master Controller can be due to several errors in
configuration among other things such as firewalls.
In WinDSX it is important to check these items:
a. There must be a Device 0 defined under Devices. In Location/Numeric Options Tab/ Connect Type must be Direct for all LAN, USB, and Serial Communications.
b. There must be a unique Comm Port defined. For LAN communications the Port Type must be LAN TCP/IP, The IP Address must match that of the LAN module.
c. The Transmit Port (TXIP Port) must match the Receive Port of the LAN Module. The Receive Port (RX IP Port) is typically 0 but if defined must match the Transmit Port of the LAN module (LAN-D’s require this). Please see configuration examples in LAN module instructions for more information on how to apply these settings correctly.
“Error 9” when trying to edit System Parameters or Location. This is caused by the increased number of regional time zones in Windows. Accommodations for Microsoft’s time zone structuring have been provided in our latest software releases. The problem is corrected with WinDSX 3.7.139 and higher.
“Operation Must Use an Updateable Query” is typically caused by inadequate Windows permissions to the files in the target Path to Database. Usually seen when adding Workstation PC’s to an existing system. Logon must have full permission over local (where the software is installed at the client) and shared WinDSX folders and subfolders.
“TCP/IP Lost” or “Comm Loss” in the Red Box in
the lower right corner of Workstation indicates one
of two things.
a. The IP Address found in DataBase/Setup/System Parameters/Comm Server Tab does not match the IPv4 address set in Windows. These must match. If changed, the Comm Server Program cs.exe or Service DSXComm must be restarted.
b. There is a Firewall or Port Blocked. WS.exe (workstation) uses TCP and Port 22223 to communicate with the Comm Server program CS.exe.
Time Zone Linking - Software Versions 3.7/4.7 and higher have a new feature that allows Time Zone Linking. This new linking logic will only work if all of the controllers in the location are of 1040 Series, 1022, or 1032 controllers with the 1030PR5 retrofit processor. All controllers in the location will require firmware V3129 or higher. This feature cannot be used if any of the controllers are of the old style 1030 Series or 1021. The 3.7/4.7 versions also require new updated versions of PC Master and Soft I/O.
History file getting too large? In WinDSX you
can configure how many days to keep in the history
logs of your system. In the Access Version it is Set
on the Comm Server in the WinDSX folder -
WinDSX\RunData\Db_Settings.txt and in WinDSX SQL it
is located in Setup/System Parameters/Comm Server
Tab. In both cases you are setting the number of
days of history to be stored.
With Firmware Versions 3098 and higher (for
1040/1022 Controllers) and 569 and higher (for
1030/1021 Controllers) multiple
device types can now
be used (stacked) simultaneously on the same reader.
In the past, some Device Types such as D5 had
multiple compatibilities. D5 would decode standard
26 bit, DSX-33 bit, and DSX-37 bit. With the newer
firmware Multiple Device Types can be implemented
(Stacked) by assigning separate Device Type
technologies to Device 0, Device 1, Device 2, and so
a. If you are using the multiple compatibility of an existing Device Type and you upgrade the firmware/flash in the controller(s), or once a new controller (containing the new firmware/flash) has been added to the system, it will be necessary to assign all of the Device Types required to the various Devices in the system.
b. If you require more Device Types than you have Devices, you can simply add an additional Device and give it the Device Type you require even though there will not actually be a controller with that address.
c. You cannot assign two different Device Types that are of the same bit length. This means that you cannot have more than 1 device type of the same bit length programmed in the system. There cannot be two different 26 bit formats or two different 37 bit formats in the Device List. It is ok to have the same Device Type more than once.
d. Once the different Device Types required have been addressed with the first few devices in the list, the rest of the devices can have the same Device Type.
e. This feature only applies to Wiegand Formats. It cannot be used for Clock and Data formats. Clock and Data formats are typically, but not always used for Magnetic Stripe and Barcode type readers.
f. The most common device types used for the Cards sold by DSX sells are: WE-26bit, D5-33bit, K0-35bit, L5-37bit.
DSX Flash.exe will shut down if an attempt to log on is made before the files have been properly copied to the WinDSX folder as directed in the “How to Flash.txt” file included in the Flash update zip file. Once in the folder check Setup/System Parameters and make sure the flash login and password are what you want them to be. Once in the Flash program you may need to go to Setup/Port Setup and under IP Port enter 127.0.0.1 for the IP Address if it is not there.
127.0.0.1 is a default TCP/IP address that can be programmed into WinDSX if not connected to a network, or if on a network but no other PC’s are to run the workstation portion of WinDSX. For proper operation including printing of any sort from WinDSX, each Workstation PC must have a unique Workstation Name and Workstation #. · Make sure a printer driver is loaded into the operating system. WinDSX software needs a printer driver installed before reports can be run. A printer is only needed if you want to print the reports to paper.
If the PC is not beeping on alarms, check Database/System Parameters/Yes/No Options/ “Enable Beep on Alarm”. This will control whether or not WAV sounds will play. Also, be sure Default Beep has been selected within the Operating System/Control Panel/Sounds. Also make sure in Workstation that the Alarm Window (bottom scrolling window) is open so you can see alarms.
The WinDSX Comm Server program, cs.exe, can be run as a service in Version 3.7.34 and 4.8.6 and higher. The procedure and files necessary to do so are on the Software Installation Drive in the Utilities folder. Make sure and copy just the files into \WinDSX and not the folder they are contained in.
Masking or not displaying the last User Name on the Login screen as per the software installation manual only applies to the database program. To prevent the Workstation program from displaying the last user name, it must be auto-started from DataBase. With the placement of the GOV.exe into the shared WinDSX folder the software will lockout an operator that makes three invalid attempts. Newer software requires the password to be at least 6 characters.
Multiple iterations of the same event showing in workstation has been determined to be caused by more than one Comm Server (cs.exe) running in a system. In Newer Software two Comm Servers result in Location Comm Loss Alarms that immediately restore. Go to DataBase/Software Registration/Workstations to find all of the PCs running the DSX Software.
Regional Time Zone and Daylight Savings Time settings. WinDSX has the ability to set each location’s Regional Time Zone and enable or disable daylight savings time (under Location in the database). The same is true for each workstation (under System/Setup/System Parameters). If used, these options must be set for each location and each workstation. Enable and set these everywhere. If not what you may see is that Workstation displays the correct time but events from the controllers may show up with the wrong time. Doors may not lock or unlock when they should. You may not be able to Edit or Add cards.
Password Profile restrictions for I/O and Device Overrides not only apply to operator manipulation of Inputs, Outputs, and Devices but to Scheduled Overrides and Linking Level Assignments. To Assign a Linking Level to a Card Holder the operator must have a profile that gives the operator all the points the Linking Level/Linking Groups includes.
On an Elevator Control System with code to output linking turned on at a particular device, the LED on the card reader does not change state on access granted unless the option "Link Granted Events to Output 1" is set to “Yes” under Device.
Card Holders that are marked as a Visitor cannot have an access level or linking level assigned unless those levels have been defined (checked) as “Can be assigned to Visitors” on the general tab.
Combinations of Code numbers that are HEX and DECIMAL values cannot be entered into WinDSX in a combination of formats. Once we turn on “Codes are HEX Values” then ALL code numbers MUST be entered into WinDSX as HEX values. Use Windows>Calculator in scientific mode and convert decimals to HEX. If codes are listed on cross reference sheets as decimal form and the “Codes are HEX Values” is checked, then the decimal code number MUST be converted to HEX and then entered into WinDSX using the HEX value.
The Time Zones that are being linked to cannot be assigned to what is initiating the link. In other words – What links to the Time Zone cannot be controlled by the Time Zone. Build as many Time Zones as necessary to make sure that when you link to a Time Zone it only affects those things you want affected. Re-using Time Zones could cause something to be controlled from a Link that was not desired. If you link to a Time Zone with a Latch response you must have another Linking Group that links to that same Time Zone with a response of Time Zone.
ASCII output from a Comm port on a Workstation is only used for Live Video Camera Control such as pan, tilt, zoom. ASCII output for alarm or status change on an input for camera call up will only work from the Communications Server. ASCII out can now be sent via UDP as well as Serial.
The Log.mdb file, which contains all the transaction history, should be kept between 50 and 100 megabytes in size. When this file becomes too large it can cause History reports to run slowly, or not run at all. In some cases, even the Delete Records option(s) in the Backup History section may not work correctly. One solution is to close the WinDSX program, copy the Log.mdb file to another folder, then delete the original Log.mdb. The copied file will still be available for History reports prior to this procedure. But if the size of the file is too large, reports may still be questionable. When WinDSX is started again, a new Log.mdb will be created. It will start recording history from Comm Server as of the date and time this procedure was done.
The abort delay option will only delay the reporting of an Alarm condition for an input. It will NOT delay the reporting of a Trouble condition for an input.
When "Use input 7 & 8", "Door Open detect relock", and "Exit request unlocks Output 1" under Devices are all set to no, Input 7 can still trigger the PreWarn. It doesn't really matter because once the input 7 has been disassociated with the door the prewarn should not be used.
When you are using two devices to control the same door Connect the output 1 of 1 device to the input 8 of the other device. Connect the Lock and DPS to the same device that has the REX connected to the other Device Output 1. Use the Hardware Installation Manual for a diagram and programming information.
Cat5/6 cable cannot be used for anything in the WinDSX system except for a network connection to a PC or LAN module.
The DSX-1030PR5 Intelligent Processor is used to upgrade existing DSX-1032, 1033, 1034 Intelligent Controllers. Mounts in metal enclosure that existing 1030P comes out of with 4 existing screws. The DSX-1030PR5 has 512K of Flash ROM and 512K of RAM. Must be revised I/O that has the row of diagnostic LEDS lower mid section.
No Lock power from a DSX-1042 could be caused by the fire override having an open condition on the Fire Override input of the 1040-PDM. Place a short across the input and lock power should restore for locks 1-8. A closed circuit from the Fire Alarm System can also be connected to the Fire Override input. This circuit should go “open” on a fire alarm condition.
There is no +5 VDC on a DSX-1042 Intelligent Controller reader port. Use caution when wiring readers to the 1042 panel. Readers will not work if they are wired improperly. However, there is 5VDC @ .5amps available on the 1040-CDM for 5 volt devices.
On the 1040-CDM, jumpers 1 & 2 should be set properly to indicate if there is a Master Controller, (dip switch 8 on) within that enclosure. Jumpers connected to the 2 left pins = all controllers in this enclosure are Subs. Jumpers connected to the right 2 pins = a Master controller exists within this enclosure.
If there appears to be no control of relays on a DSX-1043 Intelligent Controller, make sure it is defined with a Device Type of “OR”. Also, make sure there is a short between the Relay Override input terminals near the center of the Controller. These were pins 24-25 on older 1043’s, pins 50-51 on newer 1043’s.
The 150/15 power supply, intended to provide power for all 1040 Series Intelligent Controllers, must not be used to provide lock power as well. A separate power supply must be used for lock power.
When troubleshooting a reader on a 1042 panel, take the reader to the DSX panel and terminate it directly to the reader port. If the reader works fine at the panel, check the field wire for ground faults and shorts. If there are no faults or shorts on the wire, contact DSX Technical Support.
All unused inputs on all DSX Intelligent Controllers must be terminated with 1K resistors except for the DSX-1033 and 1043 Output Controllers.
Communications loss when relay outputs are cycled (energized or de-energized) is commonly due to a counter EMF spike. Counter EMF spike is best described as the collapsing of the magnetic field when a coil is de-energized. When a door strike or maglock is powered down. The magnetic field collapses and the energy must go somewhere. It is important to switch positive power to the coil driven device and keep the ground to that device constant and place an MOV across the connections from your wire to the device. This allows the MOV to activate when the field spikes to high and shunt the energy to the ground wire right at the device. Troubleshooting this is simple. Cycle one or more relays up to 50 times or until the comm. loss occurs. Then remove the wiring from the relays you are testing and cycle them again and this time there should be no comm. losses. Try the same test again once you have wired the device with a constant ground and an MOV. Use different MOVs for 12 and 24V locks.
Report Error in SQL - Server Not Yet Been Opened. When loading 6.0.24 and up the Report templates are TLS1.2 only unless you are using Windows Auth. If SQL Auth is being used on a non TLS1.2 SQL Server, the alternate TLS report templates must be unzipped and placed in the root of all \WinDSX folder installations including the Shared folder. Both sets of Reports are on the Install Media.
Missing Badge Editing Slide Controls, Positioning Arrows and Image Editing Slide Controls. Windows update KB5001337 has caused these type of windows control mechanisms to not appear where they should be and to not function. Removing this update will correct the issue or continue to update until the fix is distributed. This issue is resolved in KB5003169.