Skip to main content

Wolf8Access

HSYCO integrates the 8Access system by Wolf Safety through USB or Ethernet connection.

Communication

W-LAN (or WP-LAN) module

Protocol version 3.xx or lower

If using the W-LAN Ethernet module, it must be configured using the Tibbo DS Manager tool.
You need to set its static IP address, port (default 1001) and serial communication parameters.
For the serial parameter, go to Settings > Channel1 tab and set the parameters as shown in the table below.

Protocol version 4.xx or higher

If using the WP-LAN Ethernet module the system works in DHCP mode, so you cannot set a static IP address. If you want a static IP address on your module please contact Wolf assistance before buying it.

You have to set the serial number of the Wolf8Access MIND module in the I/O Server options.

W-USB module

If using the W-USB module, just configure HSYCO to use the following serial parameters:

Baud rate115200
Data bits8
Stop bit1
Paritynone
Flow controlnone

HSYCO Configuration

Add a WOLF8ACCESS I/O Server in the I/O Servers section of the Settings and set its parameters:

Communication

  • Comm ID: select the comm port connected to the panel.

If using USB connection (W-USB module) crate a serial Comm port, otherwise, if using the Ethernet adapter (W-LAN module or WP-LAN), crate a server Comm port. For version 4.xx or higher, communication with the WP-LAN module implies TCP/IP protocol on port 8000.

Authentication

  • Password: wolf system password

High Availability

  • Shutdown when inactive: defaults to true.

Options

IDDefaultValuesDescription
serialnum<val>serial number of the Wolf8Access MIND board. Leave it empty for protocol 3.xx or lower

Wolf8Access Utility

Use the Wolf8Access Utility to automatically discover new keys or configure existing ones.

Datapoints

Peripherals' numbers (p<n>) range from 0 to 7.

IDValueR/WDescription
connectiononlineRconnection established
offlineRHSYCO can't connect to the device
p<n>.key<pos>Rperipheral <n> read the key saved in memory position <pos>
p<n>.open1Rperipheral <n>'s door is open
1Wopen peripheral <n>'s relay
0Rperipheral <n>'s door is closed
p<n>.blocked1Rperipheral <n> is blocked (all non-manager keys disabled)
1Wblock peripheral <n> (disable all non-manager keys)
0Rperipheral <n> is un-blocked (all non-manager keys restored)
0Wun-block peripheral <n> (restore all non-manager keys)
p<n>.k<m>eraseWerase the key specified at position <m> from peripheral <n>'s memory
p<n>.k<m>.blocked1Rkey in memory position <m> of peripheral <n> is disabled
1Wdisable key in memory position <m> of peripheral <n>
0Rkey in memory position <m> of peripheral <n> is enabled
0Wenable key in memory position <m> of peripheral <n>
p<n>.k<m>.sn<val>Rthe serial number of the key in memory position <m> of peripheral <n> is <val>. Updated only at startup and after a call to p<n>.mem = read
p<n>.k<m>.manager1Rthe key in memory position <m> of peripheral <n> is a manager key. Updated only at startup and after a call to p<n>.mem = read
0Rthe key in memory position <m> of peripheral <n> is a regular key. Updated only at startup and after a call to p<n>.mem = read
p<n>.memaddWinstruct peripheral <n> to add to memory the next read key
readWrequest to peripheral <n> the list of saved keys (see p<n>.k<m>.sn and p<n>.k<m>.manager datapoints)
clearWclear peripheral <n>'s memory
refreshWrefresh peripheral <n>'s memory erasing all disabled keys
p<n>.mem.ok<pos>Rthe read key has been correctly saved in memory position <pos>
p<n>.mem.err<pos>Rthe read key was already saved in memory position <pos>
p<n>.mem.full<val>Rthe memory of peripheral <n> is full and it contains <val> keys
p<n>.mem.free<val>Rperipheral <n> has <val> key slots available in its memory. Updated only after a "read" request
readWrequest the reading of available memory on peripheral <n>
p<n>.mem.clear1Rthe memory of peripheral <n> has been cleared
0Rerror while clearing the memory of peripheral <n>
p<n>.mem.refresh1Rthe memory of peripheral <n> has been refreshed
0Rerror while refreshing the memory of peripheral <n>
p<n>.alarm.forced1Rdoor forced alarm
p<n>.alarm.comm1Rcommunication error with peripheral <n>
0Rcommunication with peripheral <n> restored
p<n>.copy<n1>:<from>:<to>Wcopy to peripheral <n>'s memory all the keys in the specified range (<from> - <to>) of peripheral <n1>'s memory. (e.g. p1.copy = 0:10:20)
p<n>.reltime<val>Rthe relay time of peripheral <n> is set to <val>, in sec/10
<val>Wset the relay time of peripheral <n> to <val>, in sec/10 (max 65535 = 109 min)
MRperipheral <n>'s relay is set as monostable
time<val>Rtime and date set on the module, value format: "yyyy-mm-dd hh:mm:ss". Updated only after a "read" request
<val>Wset the module's time and date, value format: "yyyy-mm-dd hh:mm:ss"
readWrequest the module's time and date

UISET Actions

IDAttribute
log<text>
log0<text>

Release Notes

3.8.0

  • support for protocol versions 4.xx and 5.xx
  • more verbose logs
  • support for multiple EVO modules

3.7.0

  • initial release

''WOLF SAFETY is a registered trade mark of ELP s.n.c.