0% found this document useful (0 votes)
6 views

Guard_Software_User_Guide4

The Perimeter Guard AN307 Software user guide provides detailed instructions for connecting AN307COM devices to an integrated system via RS485 communication, using either K307 or UDS1100 devices. It covers installation, configuration, and user settings, along with descriptions of various components such as the LR307USB relays unit and SDK. The guide also includes troubleshooting tips and a warranty disclaimer.
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
6 views

Guard_Software_User_Guide4

The Perimeter Guard AN307 Software user guide provides detailed instructions for connecting AN307COM devices to an integrated system via RS485 communication, using either K307 or UDS1100 devices. It covers installation, configuration, and user settings, along with descriptions of various components such as the LR307USB relays unit and SDK. The guide also includes troubleshooting tips and a warranty disclaimer.
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 24

U SER G UIDE

PERIMETER GUARD AN307 SOFTWARE

Author: User Guide Version:


Andrej Osterman V1.22

October 2022
CONTENTS CONTENTS

Contents
1 Introduction 2
1.1 K307 (Anikom) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2 UDS1100 (Lantronix) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.3 LR307USB relays unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.4 LR307USB status check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

2 Installation 5
2.1 Running for the first time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.2 Login as Superuser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

3 Main Window 6
3.1 Main Window Look . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

4 Users 7
4.1 Users Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

5 Configure 8
5.1 Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
5.2 Configure Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
5.3 Edit Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
5.4 E-mail Configure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
5.5 E-mail Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
5.6 Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

6 Settings 12
6.1 Remotely Settings the Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
6.2 Read signal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

7 History 14
7.1 View History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

8 The K307 15
8.1 Wiring with K307 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
8.2 Start up the K307 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

9 UDS1100 17
9.1 UDS1100 settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
9.2 UDS1100 block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
9.3 UDS1100 wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

10 SDK (Software Development Kit) 21


10.1 Configure the SDK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
10.2 SDK alarm handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

11 Warranty and Disclaimer 23

12 Contact 23

1
1 INTRODUCTION

1 Introduction
The Perimeter Guard AN307 Software is used for connecting several AN307COM devices with the in-
tegrated system. AN307COM devices are connected to the system using the two wire standard RS485.
Currently there are two ways to terminate RS485 communication: with the K307 device (manufactured
by Anikom) or with the UDS1100 device(s) (manufactured by Lantronix). If the RS485 communica-
tion can be brought close to the PC computer, where the Guard Software is running, then K307 can be
used. In case the RS485 can not be directly brought to the PC computer, one or several UDS1100 can
be used.
This manual describes the installation and configuration of the software in detail. The recommen-
dations for the power supply and the RS485 communication wiring are also described. Finally, the
usage of the SDK is described.

1.1 K307 (Anikom)


K307 is used for connecting several AN307COM
devices with the integrated system. K307 is a
converter from the RS485 to the RS232 hardware
protocol. If the personal computer does not have
an RS232 terminal, the conventional USB/RS232
converter can be used to connect K307 to USB.
RS485 is galvanically isolated from the rest of
the terminals (RS232, power supply and relays
output).
The K307 also has a control function. There
are two relays outputs: the operation and the
alarm relay. If everything is operating normally,
both relays are in the NC (normal close) position
and the corresponding LEDs turn green. Figure 1: K307
If alarm, cable fault, tamper or fault occurs
in any of the AN307COM, connected to the system, the alarm relay goes to open position and the
corresponding LED turn red. If the software is somehow in wrong status (some error) or if does not
work, then operating relay goes to open position and the corresponding LED turn red. This way, we
have visual and electrical control of the proper working of the system. Only one K307 can be used in
a single perimeter system.
See Figure 19 for K307 wiring.

2
1.2 UDS1100 (Lantronix) 1 INTRODUCTION

1.2 UDS1100 (Lantronix)


An UDS1100 is an alternative to the K307. The
UDS1100 is a single-port device server that provide a quick
and simple way to bring the advantages of data accessibility
and remote management of devices connected to an Ether-
net network.
The UDS1100 is used for remote connection the
AN307COM system with the Perimeter Guard AN307
Software through the Internet or the internal Ethernet net-
Figure 2: UDS1100 work. One or several AN307COM can be connected to a
single UDS1100. One or several UDS1100 can be used
with one Perimeter Guard AN307 Software.
The UDS1100 has the Ethernet connection port (to the Internet side) and the RS485 connection
port (to the AN307COM side). Data from the RS485 is encapsulated in the UDP packet, which are
transmitted through the Internet. The Perimeter Guard AN307 Software is capable of receiving and
transmitting the UDP packets according to the settings. Each UDS1100 has a static IP address. A
personal computer running Perimeter Guard AN307 Software must also have a static IP address.
One or more UDS1100s can be used in the system.
Each UDS1100 can drive one or more AN307COM. In this way, the configuration of the system is
very flexible and depends on the topology of the guarded object. See Figure 23 for UDS1100 wiring.

3
1.3 LR307USB relays unit 1 INTRODUCTION

1.3 LR307USB relays unit


The LR307USB is an output event device
with 24 relays with an easy plug-and-play USB
connection to a personal computer. Each relay
can take one or more alarm states. For each relay
you can set events: the ALARM 1, the SABO-
TAGE 1, the ALARM 2, the SABOTAGE 2, the
BOX and the FAULT for each AN307COM de-
vice. Each relay can be configured to manifest
one or more events. All intermediate variants
are also possible. Settings for LR307USB are
in Configure/Configure Devices menu (see Fig- Figure 3: LR307USB
ure 11). Usually, one LR307USB can be used per
eight AN307COM, ie for each AN307COM three relays can be used.

1.4 LR307USB status check


LR307USB status can be checked on the Configure/Relays Status (LR307USB) pull down menu.
The dialog is shown in Figure 4. At the bottom of the dialog are buttons Next Device and Previous
Device for navigating through all eight devices. If the observed device is working properly, the LEDs
for each relay show status of the relay (green color means closed status). If the observed device is not
working properly or is not connected, the red LED OFF turns on.

Figure 4: LR307USB status

The text at each relay terminal describes which events are outlined by the relay.
The maximum current through the relays can be 120 mA. Therefore, LR307USB is suitable for
connecting the alarm panels or some other devices, whose signals have low current.

4
2 INSTALLATION

2 Installation
First, the FTDI D2XX driver must be installed.
The driver should be downloaded from https://ftdichip.com/drivers/d2xx-drivers. For Windows,
the driver should be in zip form (for example CDM212364 Setup.zip). Unzip it and run the installation.
The perimeter Guard AN307 Software can be installed by a run of the Setup Guard AN307.exe
program. The setup procedure is standardized, like most setup programs (see Figure 5).
The default installation directory is c:\Perimeter Guard AN307. You can choose the installation
directory, but it is recommended to leave directory as it is. The main files which are installed are
guard.exe (execution program) and guard.ini (configuration settings).
The program can be started from Start/Perimeter Guard AN307/Perimeter Guard AN307.

Figure 5: Installation of the Perimeter Guard AN307 Software

2.1 Running for the first time


If the Perimeter Guard AN307
Software is not running yet, the con-
figuration file guard.ini is not yet cre-
ated. It is created when the program is
running for the first time. A dialog ap-
pears (see Figure 6). Choose Default
button, if you want predefined param-
eters, or choose Empty, if you want to Figure 6: First time running
start with no predefined parameters.

5
2.2 Login as Superuser 3 MAIN WINDOW

2.2 Login as Superuser


After the program is starts, the parameters should be set and the
users should be defined. To achieve this, we need to log in as a supe-
ruser. Int the pull down menu we choose Users/Log In. The dialog
(see Figure 7) for entering the username and password appears.
For the username writes: superuser.
For the password writes: abc.
The superuser has access to all configuration and settings.

Figure 7: Log In

3 Main Window
3.1 Main Window Look
The main window of the software can be seen in Figure 8. The left upper field of the main window
shows the ground plan of the object with lines (which represents fences).
The lines are color-coded and represent the status of the fence. Colors are described in the legend.
The status shows the current status of the fences. If the fence is in normal mode (no alarm, everything
is OK), the status window is empty. In History, there are the last few events. The number of events
shown can be adjusted in Preferences (see Figure 10).
The status window shows the current highest status (priority is defined in the Legend window - the
one on top has the highest priority). The Clock window shows current date and time. It is updated each
second.

Figure 8: Main Window

6
4 USERS

4 Users
4.1 Users Settings
Only the superuser can use settings of users. The Users Settings dialog is reached from Users/Users
Settings.
In this table the users and their permissions are set (see Figure 9).

Figure 9: Users Settings

The permissions for nouser can also be defined. This can be done if nouser is written in the User
and Password field (see Figure 9). In this row, the permissions for the nouser can be set.

7
5 CONFIGURE

5 Configure
5.1 Preferences
The preferences dialog can be
reached by the superuser and those
users who have the permission for this
task.
The preferences dialog is reached
from Configure/Preferences. In the
Preferences dialog some parameters
can be set (see Figure 10). At
the top, one can choose the Con-
necting Device. Currently, there are
two options: through the serial port
connection (K307 or 2xUDS1100)
and through the Ethernet connection
(Multi UDS1100). If the first (K307)
or second (2xUDS1100) option is cho-
sen, the serial port should be selected.
If the third option (2xUDS1100) is
chosen, the UDP port should be writ-
ten.
The History Event Size on Main
Window is a number of recent events,
that are shown in the History window.
The sounds for main alarm and for
other alarms can be chosen. Currently,
wav files are supported. Background
picture can be select from the Ground
Plan Picture. JPG and GIF formats
are supported. Opacity of the picture
can be set by the opacity slider.
Figure 10: Preferences Thickness of lines on the map can
be set, the values are from 1 to 9.
The password for the superuser can be changed. Only the superuser can change this password. To
change it, type the same password twice.
If Allow nouser is checked, the so-called nouser is allowed.
If Exit program with a username and password is checked, the program can be exited only if
the username and password are typed again.
If Always on top is checked, the main program window always stays on top, regardless of mouse
focus. To achieve this, the program should be restarted after changing this option.
The Wind Save Period is a period in minutes of saving wind speed events to the history table.
The Relays Inactivity Duration is a period in which the onboard AN307COM relays remains
inactive, when the button Relays Off is pressed, regardless of alarms, which may occur in that period
of time.
The Sound Inactivity Duration is a period in which the PC alarm sound remains inactive, when
the button Sound Off is pressed, regardless of alarms, which may occur in that period of time.
The purpose of the SDK (Software Development Kit ) is to connect data from the Perimeter Guard
AN307 Software to other software packages. In this way other packages can safely use data without
fear of program collapse. The SDK is working through the network console and its functions can be
reached with a web browser (eg. http://localhost:8080/index.html).

8
5.2 Configure Devices 5 CONFIGURE

5.2 Configure Devices


The device configuration menu can be reached from Configure/Configure Devices. Each AN307COM
is defined in only one row. Each AN307COM must have a unique address. Each AN307COM has two
fences (wings) with a unique name. Each device must have a unique address and each fence must have
a unique name (see Figure 11).

Figure 11: Configure Devices

If the connection device is K307, the column UDS1100 IP has no relevance and can be left empty
(see Preferences and Figure 10).
If the Multi UDS1100 connection mode is used, the UDS1100 IP address should be written. The
IP address must be entered from UDS1100, which is connected to the desired AN307COM.
If only one UDS1100 is used for several AN307COM, the same UDS1100 IP should be written for
all devices.
In the LR307USB column, the address of the LR307USB should be set (possible values are from 1
to 8). The address of LR307USB device can be read on the label at the bottom of LR307USB device.
For each event (Alarm1, Sab1, Alarm2, Sab2, Box and Fault) a corresponding number of relay can be
set (possible values are from 1 to 24). Several events can be set to a single relay. The relay will open the
contact if some of those events occur (OR logic). If alarms or events don’t occur, relays are in normal
close (NC) state.

9
5.3 Edit Line 5 CONFIGURE

5.3 Edit Line


Lines can only be edited if the user has per-
mission to do that (the superuser can always edit
lines). After all the devices have been defined
(see Configure Devices), each line must be in
junction with one fence. A new line can be added
to the site map by the command Configure/Add
Line. A new line, when added, is drawn on the
left side of the site map. The line can be moved
by pressing and holding the left mouse button Figure 12: Edit Line
over the end of the line and leading it to the de-
sired position. In the desired position the left mouse button should be released. By pressing the right
mouse button over the desired line, the Edit line dialog box appears (see Figure 12). According to the
real situation on the field, each line should be connected to a particular fence. A line can be deleted by
clicking Delete Line button.

5.4 E-mail Configure


Sending E-mails can be configured in
Config/E-mail Configure (see Figure 13). E-
mails can be configured only if the user has per-
mission to do that (the superuser can always con-
figure E-mails).
On the field To, the e-mail of the main recip-
ient should be written. Additional recipients of
the e-mails can be written in the field Bcc, each
in a separate row ending with the semicolon (;).
The field From can contain your or any e-mail
address (at the receiving side this is the Sender
field).
The Subject is usually the name of the object,
which is protected by the AN307COM system.
The most important configuration in this dia-
log is the SMTP Server. Usually, it is the same
server as in your E-mail software (see the ac-
count settings or the Outgoing Server SMTP in
your E-mail software). If the SMTP server needs
your password and username, you should proved
them.
At this point sending an e-mail can be tested.
This is done by clicking the Send Test E-mail
button.

Figure 13: E-mail Configure

10
5.5 E-mail Text 5 CONFIGURE

5.5 E-mail Text


Sending the E-mail text can be configured in
Config/E-mail Text (see Figure 14). The e-mail
text can be configured only if the user has per-
mission to do that (the superuser can always con-
figure the E-mail text).
For each particular event the text can be writ-
ten. If the event occurs and the check-box for a
particular event is checked, text is sent by e-mail.
Please note, that this function should be used
with caution. Since servers are not 100% ma-
chines, could happen that SMTP server goes
down, and there will be no e-mail and no warning
about the event through the e-mail!

Figure 14: E-mail Text

5.6 Language
The language can be selected from this menu. After changing
this option and clicking the OK button, the program should immedi-
ately change to the desired language. Currently following languages
are available: English, Italian, Slovene, Chinese, French, Czech and
Spanish.

Figure 15: Language

11
6 SETTINGS

6 Settings
6.1 Remotely Settings the Device
In the Devices Settings the parameters of the
AN307COM devices can be remotely changed.
The Devices Settings can be configured only if
the user has permission to do that (the superuser
can always do this).
The dialog for changing parameters can be
entered from Settings/Devices Settings. The dia-
log can be seen in Figure 16.
First, the desired device should be chosen.
The parameters are automatically read from the
device, when it is chosen. The parameters can
also be re-read by clicking the push-button Read
Device.
The new value can be now set by the rotat-
ing knob. When the value of the knob is different
than the value of the device, the knob is colored
red. When the values are set, click on the Write
Device button and the parameters will be sent to
the device. The default values are: 25 for Sen-
sitivity, 3 for Beat and 7 for Time Window, Use
Relays is off, Temp. Meas is on, Wind Adjust-
Figure 16: Devices Settings
ment is 1 and Algorithm is 3.
If Relays NC is checked, the two relays on
the AN307COM are in the NC (normal close) function. If Relays NC is unchecked, the relays are
in NO (normal open) function. Relays will be in function, when the alarm is triggered, the cable is
faulted, or the box is opened.
If Temp. Meas. is checked, the temperature is measured on the AN307COM board. At low tem-
peratures, sensitivity is automatically increased because the sensor cable is less sensitive to vibration.
If the Wind Adjust. is set from 1 to 15 and the windmill is connected, the sensitivity is automat-
ically reduced the wind blows. The higher is the wind sensitivity adjustment set, more is sensitivity
reduced. Set this parameter high enough so that false alarms do not occur when the wind blows. If no
windmill is connected or if the wind is not blows, this parameter has no effect.
Algorithm 0 is the least sensitive among the three algorithms and sensitivity should be set a bit
higher (start with sensitivity 60 or more). This is the basic algorithm (the same algorithm as in the
firmware version V2.16 or earlier).
Algorithm 1 is the same as Algorithm 0. The only difference is that it is more sensitive. Sensitivity
should be set lower a with Algorithm 0 (start with sensitivity 40).
Algorithm 2 is even more sensitive than Algorithm 1. It is also adaptable to periodic disturbances.
Start with sensitivity 25.
Algorithm 3 is similar as Algorithm 2 with the addition of the wind filter. The wind filter minimizes
false alarms because of the wind.

12
6.2 Read signal 6 SETTINGS

6.2 Read signal


This function is intended for monitoring unwanted disturbances in the sensor cable. The Devices
Settings can be configured only if the user has permission to do that (the superuser can always do this).
The signal on the fence can be observed from Settings/Read Signal. An example is shown in
Figure 17, where signal from one shake of the fence can be observed.
First, the desired device should be chosen. Then Read Fence 1 or Read Fence 2 button can be
clicked. Reading takes about 4 seconds, and after that, the signal curve is shown. The scale of the
y-axis can be changed in the Y Axis Zoom combo box.
If there are no disturbances on the sensor cable, the curve should be everywhere close to 0.

Figure 17: Read Signal

Curves are stored in the files in the buffer directory. The file name composes of the device address
(2 -255), fence input (1 or 2), and the time the file was created (yymmdd hhmmss, where yy is year,
mm is month, dd is day, hh is hour, mm is minute and ss is seconds of time of creation of the file). The
file has the suffix *.txt.
Previous curves can be observed with the Graph combo box, where all graph files are listed.

13
7 HISTORY

7 History
7.1 View History
All past events can be listed in the table (see Figure 18). History/View History lists all events in the
present month. The time period can be chosen with the combo box From: and To:. After selecting the
time period, Refresh button should be clicked to see the table.
View History can only be reached if the user has permission to do that (the superuser can always
see History).

Figure 18: View History

14
8 THE K307

8 The K307
If the K307 is used, Connecting Device should be set to K307 (see Preferences). The K307 is
normally used when is possible to bring the RS485 wires next to the personal computer. The K307 is
used for connection of several AN307COM devices to the integrated system. The K307 is a converter
from the RS485 to the RS232 hardware protocol. RS485 is galvanically isolated from the rest of the
terminals ( RS232, the power supply and the relays output).
In additional, the K307 has the control function. There are two types of relay outputs in K307
board, the operating relay and the alarm relay. If everything is operating normally, the relays are in
the NC (normal close) position and the belonging LEDs turn green.
If the alarm is triggered, the sensor cable has fault, a tamper emerge, or any other error occurs
in any of the AN307COMs connected to the system, the alarm relay goes to open position and the
belonging LED turn red.
If there is an error in software, the operating relay goes to open position and the belonging LED
turns red.
This way, we have a visual and electrical control of the proper working of the system.

8.1 Wiring with K307


The connection diagram for AN307COMs and K307 is shown in Figure 19. The RS485 should be
done with shielded twisted pair cable. The shield should be connected only at the K307 side. At the
AN307COM side, it should be left unconnected. The RS485 wiring is parallel. Be careful to connect
all the A terminals together and all the B terminals together.
It is strongly recommended to use a different power supply for the K307 and the AN307COMs!
Power supply for the K307 could be a wall power supply (for example 12VDC, > 150mA). The main
power supply must be grounded appropriately.
The power supply wires for the AN307COMs must have a large enough intersection to avoid a
too high voltage drop. It doesn’t matter if the power supply cable is twisted or not. For the power
supply cable the ohm impedance and the voltage drop should be calculated. The power supply voltage
at the AN307COM should be higher than 8VDC. Note that the maximum power supply current for the
AN307COM is up to 100 mA.
You should consider your country’s regulation about the grounding protection of the electrical
equipment and the buildings. The fence itself must be grounded appropriately. Consult the manufac-
turer of the fence on how to ground the fence.

8.2 Start up the K307


Start the software Perimeter Guard AN307 on your PC. Set the right Comm port (serial port) in
Preferences.
Connect the power supply to K307. Both lights at the front of the K307 should be red. Then
connect the K307 to the serial port. The operating light at the front of the K307 should be green, while
the alarm light stays red (that means that the software is running, but the alarms stay on because the
software is not yet configured and the AN307COMs are not connected through the RS485).
After everything is well configured and there is no alarm, the alarm light at the front of the K307
should turn green.

15
8.2 Start up the K307 8 THE K307

Figure 19: K307 wiring

16
9 UDS1100

9 UDS1100
In this section the Multi UDS1100 mode is described. In Preferences, Connecting Device should
be set to Multi UDS1100. In this mode, one or several UDS1100(s) can be connected to the Perimeter
Guard AN307 Software through the Ethernet. Please don’t be confused by the word Multi - there can
be one or several UDS1100(s) used!
The 2-x UDS1100 mode is obsolete and is only left in the software for test purposes.
Please note that each UDS1100 has a static IP address. The personal computer, running the Perime-
ter Guard AN307 Software, must also has the static IP. This is done for security reasons. The data
packets sent through the Internet are UDP/IP and are routed regarding the IP addresses.
The Perimeter Guard AN307 Software sends the UDP/IP data packets, which have a destination IP
address of the UDS1100. The UDS1100 answers with the UDP/IP data packets, which have a destina-
tion IP address of the personal computer.

9.1 UDS1100 settings


The first decision about network settings is choosing the appropriate port for the UDP packets.
The port 8007 is chosen by default. It is recommended to use the same port number for incoming and
outgoing UDP/IP data packets. Please consult your network administrator on which port to choose.
This port number should be configured to the UDS1100 and also to the Perimeter Guard AN307
Software. In the Perimeter Guard AN307 Software, the port number should be written in Config-
ure/Preferences/UDS1100 Port (see Figure 10).

Figure 20: UDS1100 Settings

17
9.1 UDS1100 settings 9 UDS1100

The following settings should be used for the UDS1100 device (see Figure 20):

1. Network Settings

(a) IP Configuration
i. IP Address: unique IP address, this is IP from the UDS1100
ii. Sub-net Mask: 255.255.255.0 (or appropriate to your network)
iii. Default Gateway: 0.0.0.0
iv. DNS Server: 0.0.0.0
(b) Ethernet Configuration
i. Auto Negotiate: yes

2. Serial Settings

(a) Channel 1
i. Protocol: RS485-2 wire
ii. Flow control: None
iii. Baud Rate: 4800
iv. Data Bits: 8
v. Parity: None
vi. Stop Bits: 2
(b) Pack Control
i. Enable Packing: yes
ii. Idle Gap Time: 12 msec
iii. Send Frame Immediate: yes
iv. Match 2 Byte Sequence: no
v. Send Trilling Bytes:no
(c) Flush Mode
i. All set to: no

3. Connection Settings

(a) Connected Protocol


i. Protocol: UDP
(b) Datagram Mode:
i. Datagram Type: 01
(c) Endpoint Configuration:
i. Local Port: 8007 (or appropriate, see text)
ii. Remote Port: 8007 (or appropriate, see text)
iii. Remote Host: static IP from the host computer (where the Guard software is running)
iv. Use Broadcast: No

18
9.2 UDS1100 block diagram 9 UDS1100

9.2 UDS1100 block diagram


More UDS1100s can be connected to one Perimeter Guard AN307 Software. Each UDS1100
should have a unique IP address.
Several AN307COMs can be connected to each UDS1100 (see Figure 21).
Each AN307COM should have a unique RS485 address. This rule is also valid if two AN307COM
are not connected to the same UDS1100 (identical RS485 addresses are not allowed).
The Perimeter Guard AN307 Software should know to which UDS1100 should send data for the
particular AN307COM. This is done by writing the IP address of the UDS1100 for each AN307COM
in Configure/Configure Devices/UDS1100 IP column (see Figure 11).
Each UDS1100 should also know where to send the packets. The destination is the IP address of
the personal computer where the Perimeter Guard AN307 Software is running. On each UDS1100 this
IP should be written in Connection Settings/Endpoint Configuration/Remote Host (see Figure 20).

Figure 21: UDS1100 block diagram

9.3 UDS1100 wiring


The connection diagram for AN307COMs and UDS1100s
is shown in Figure 23. It is recommended that for the
RS485 communication, a twisted pair (preferably shielded)
cable is used. If the cable is shielded, the shield should be
connected only at UDS1100 side. At the AN307COM side,
shield should be left unconnected. Be careful to connect all
the A RS485 terminals together and all the B RS485 termi-
nals together.
It is strongly recommended to use a different power
supply device for the UDS1100 and for the AN307COMs! Figure 22: UDS1100 DB25 Connector
The power supply for the UDS1100 could be wall imple-
mentation (for example 12VDC, > 150mA). The main power supply must be grounded appropriately.
The power supply wires for the AN307COMs must have an intersection large enough to avoid a
too high voltage drop. It doesn’t matter if the power supply cable is twisted or not. For the power
supply cable, the ohm impedance and the voltage drop should be calculated. The power supply voltage
at the AN307COM should be higher than 8VDC. Note that the maximum power supply current for the
AN307COM is up to 100 mA.
You should also consider the regulations in your country about grounding protection of electrical
equipment and buildings. The fence itself must be grounded appropriately. Consult the manufacturer
of the fence on how to ground the fence.

19
9.3 UDS1100 wiring 9 UDS1100

Figure 23: UDS1100 Wiring

20
10 SDK (SOFTWARE DEVELOPMENT KIT)

10 SDK (Software Development Kit)


The purpose of the SDK (Software Development Kit ) is to transfer data from the Perimeter Guard
AN307 Software to a User Software Package. In this way, the User Software Package can safely use
data without fear of collapse program. The SDK works through the network console and its functions
can be reached on the web browser (eg. http://localhost:8080/index.html).

10.1 Configure the SDK


To successfully run the SDK, set the Configure/Preferences/SDK http server connection to Local-
host and the SDK port to 8080. On the same personal computer run the web browser and type follow-
ing URL: http://localhost:8080/index.html. If everything works, the browser should show something
similar as Figure 24.

Figure 24: SDK Reading Data

The first line always says: AN307 perimeter wire fence system. The second line is the current
date and time. The following line shows the main status. If everything is OK, the main status is OK.
The status field is listed between first and second dashed line.
The last few history events are listed between the second and third dashed line. The number of
these events can be set in Configure/Preferences/History Event Size on Main Window (see Figure
10).
The data does not update automatically. To read through the data, click the Reload Current Page
on the browser. The User Software Package should work on the same principle. After each time the
data is refreshed, second line (with the current date and time) should be inspected.

21
10.2 SDK alarm handling 10 SDK (SOFTWARE DEVELOPMENT KIT)

10.2 SDK alarm handling


Figure 25 shows a case in which two alarms occur. The alarm stays on until the operator press the
button Alarm Off on the main window. If thew program works like the SDK, there will be no operator,
who will directly press the button Alarm Off. Instead, the outside program must do this task. This can
be done with the two sequential readings with the additional arguments.
The first reading after the alarm occurs should be http://localhost:8080/index.html?alarm=1 and
the second should be http://localhost:8080/index.html?alarm=2. After this procedure, the alarm
event will be erased from the status field.

Figure 25: SDK alarm

22
12 CONTACT

11 Warranty and Disclaimer


The product is constructed by all the enforced technical norms and corresponds to the regulations
of the electromagnetic compatibility (UL RS Slovenia, 64/2001). The product is a low voltage device
(up to 18 VDC). Therefore, it does not pose a danger of electrical shock. The product is not intended
for installation in areas where the presence of explosive gases is possible. The producer ensures the
operation of the product and is engaged to eliminate all the defects on the product in the period of
normal usage. If the product is not repaired in 45 days, it will be replaced. The product has a one
year guarantee from the purchase date. The guarantee is not valid in case of damages caused by
incompetent electrical workers or atmospheric causes (the blow of direct or indirect lightning, caused
static electricity from the thunderstorm).
The fence should be grounded. Resistance to the ground should be less than 20 Ohm. The man-
ufacturer of the fence should be consulted on how to ground the fence. One must also consider the
regulations regarding grounding protection of electrical equipment and buildings in one’s country.
The guarantee is valid only for the product itself. The producer does not assume responsibility for
other damages caused by malfunctioning or wrong operation of the product. The producer, moreover,
does not assume responsibility for whichever type of damages caused by a third party protected with
this product. In cases of this kind the plant must adequately be assured from the insurance agency.
The installation must be evaluated for proper operation at least in half year period and maintenance
records must be kept. The guarantee is valid if the date of purchase on the guarantee certificate is
proven from the stamp and from the company of the authorized dealer. The period of guarantee is
extended for the repair time. Assistance and pieces of reciprocation for the product are assured for the
period of 7 years.

12 Contact
MARS COMMERCE d.o.o.
Poslovna cona A 10
SI-4208 Šenčur
Tel.: +386 04 280 74 00
[email protected]

LATEX Saturday 8th October, 2022 at 10:30

23

You might also like