User Manual

ManualsBrandsu-blox ManualsElectronicsWAGO Bluetooth Terminal 750-644

Table Of Contents

Bluetooth® RF Transceiver 750-644

Fieldbus Independent

I/O Modules

Bluetooth

RF Transceiver

750-644

Manual

Version 1.0.1

Summary of content (228 pages)

PAGE 1
Fieldbus Independent I/O Modules Bluetooth® RF Transceiver 750-644 Manual Version 1.0.
PAGE 2
• General Copyright © 2008 by WAGO Kontakttechnik GmbH & Co. KG All rights reserved. WAGO Kontakttechnik GmbH & Co. KG Hansastraße 27 D-32423 Minden Phone: +49 (0) 571/8 87 – 0 Fax: +49 (0) 571/8 87 – 1 69 E-Mail: info@wago.com Web: http://www.wago.com Technical Support Phone: +49 (0) 571/8 87 – 5 55 Fax: +49 (0) 571/8 87 – 85 55 E-Mail: support@wago.com Every conceivable measure has been taken to ensure the correctness and completeness of this documentation.
PAGE 3
Important Comments Legal Principles • 3 Content 1 Important Comments ................................................................................. 7 1.1 Legal Principles........................................................................................ 7 1.1.1 Copyright ............................................................................................. 7 1.1.2 Personnel Qualification ....................................................................... 7 1.1.3 Intended Use ...........
PAGE 4
• Important Comments Legal Principles 5 Fieldbus-specific Additions ...................................................................... 82 5.1 CANopen................................................................................................ 82 5.1.1 Process Image Access........................................................................ 82 5.1.1.1 Example ........................................................................................ 83 5.2 DeviceNet ...............................
PAGE 5
Important Comments Legal Principles 6.3.5.5 6.3.5.6 6.3.5.7 6.3.5.8 6.3.5.9 6.3.5.10 6.3.5.11 6.3.5.12 6.3.5.13 6.3.5.14 6.3.5.15 6.3.5.16 6.3.5.17 6.3.5.18 6.3.5.19 6.3.5.20 6.3.5.21 6.3.5.22 6.3.5.23 6.3.5.24 6.3.5.25 6.3.5.26 6.3.5.27 6.3.5.28 6.3.5.29 6.3.5.30 6.3.5.31 6.3.5.32 6.3.5.33 6.3.5.34 6.3.5.35 WAGO-I/O-SYSTEM 750 I/O Modules • 5 Set Local IP Address (SetLocalIPAddress, 0x44) ...................... 125 Read Local Subnet Mask (GetLocalSubnetMask, 0x45)............
PAGE 6
• Important Comments Legal Principles 6.3.5.36 Write the User-Friendly Name of an Authorized Device (SetUserfriendlyName, 0x8D) .................................................... 168 6.3.6 Diagnostics ...................................................................................... 170 6.3.6.1 Read Status of the Local Bus Module (GetLocalDeviceStatus, 0xD0) .......................................................................................... 170 6.3.6.
PAGE 7
Important Comments Legal Principles • 7 1 Important Comments To ensure fast installation and start-up of the units described in this manual, we strongly recommend that the following information and explanations are read carefully and followed. 1.1 Legal Principles 1.1.1 Copyright This manual is copyrighted, together with all figures and illustrations contained therein. Any use of this manual which infringes the copyright provisions stipulated herein, is not permitted.
PAGE 8
• Important Comments Symbols 1.2 Symbols Danger Always abide by this information to protect persons from injury. Warning Always abide by this information to prevent damage to the device. Attention Marginal conditions must always be observed to ensure smooth operation. ESD (Electrostatic Discharge) Warning of damage to the components by electrostatic discharge. Observe precautionary measures for handling components at risk.
PAGE 9
Important Comments Safety Notes • 9 1.4 Safety Notes Warning Switch-off the system prior to working on bus modules! In the event of deformed contacts, the module in question is to be replaced, as its functionality can no longer be ensured on a long-term basis. The components are not resistant against materials having seeping and insulating properties. Members of this group include: aerosols, silicones, triglycerides (found in some hand creams).
PAGE 10
• I/O Modules Special Modules 2 I/O Modules 2.1 Special Modules 2.1.1 750-644 [Bluetooth® RF Transceiver] 2.1.1.1 View 13 14 Operational and connection status Antenna socket SMA Data contacts Power jumper contacts 750-644 Figure 1: View g064400e 2.1.1.2 Description The Bluetooth® RF Transceiver 750-644 (referred to in the following as "Bluetooth® module") integrates a Bluetooth® network (piconet) into the WAGOI/O-SYSTEM 750.
PAGE 11
I/O Modules Special Modules • 11 The Bluetooth® module is operated in the public domain ISM 2.4 GHz band and enables wireless data transfer over large distances. If using the WAGO Antenna 758-912, ranges of up to 1000 meters can be achieved.
PAGE 12
• I/O Modules Special Modules The version information is contained in the serial number or in the update matrix; both are printed on the right side of the coupler/controller.
PAGE 13
I/O Modules Special Modules • 13 2.1.1.3 Indicators The LED display must be interpreted differently depending on whether the Bluetooth® module functions as a master or as a slave (see Sections 2.1.1.3.1 and 2.1.1.3.2). 13 14 1 3 5 7 2 4 6 8 Figure 3: Display Elements g064402 x 2.1.1.3.
PAGE 14
• I/O Modules Special Modules 2.1.1.3.2 Slave Table 2: LED Slave Signals LED 1 Designation Operation status indicator Status: Function green Operating status OK (independent of radio communication) red Disruption of the local internal data bus connection, the field voltage or the internal communication (circuit board) green Connection to master established green flashing Data transfer 2 off No master is configured for this slot.
PAGE 15
I/O Modules Special Modules • 15 2.1.1.4 Schematic Diagram Antenna socket SMA 1 5 1 5 Antenna 24 V 2 6 2 6 +24 V 0V BTModule OS 3 7 3 7 SPI SPI Logic 0V 8-segment LED display 4 8 4 8 750-644 Figure 4: Schematic Diagram g064401e 2.1.1.5 Technical Data Table 3: Technical Data for Bluetooth® Module 750-644 Module-Specific Data Radio technology Bluetooth® 2.
PAGE 16
• I/O Modules Special Modules Module-Specific Data Diagnosis (through optical display) Device status, connection status [1] Diagnosis (through process image) Device status, connection status [1], time monitoring Configuration WAGO-I/O-CHECK and WAGO-I/O-PRO CAA Dimensions (mm) W x H x L 24 x 64 [2] x 100 Weight approx. 85 g Accessories Miniature WSB Quick marking system External WAGO antenna, SMA, with magnet base (item no. 758-912) Standards and directives (see Section 2.
PAGE 17
I/O Modules Special Modules • 17 2.1.1.6 Function Description Bluetooth® technology defines piconet as a topology consisting of a master and up to seven slaves. Data can be exchanged between each slave and the master wirelessly and bidirectionally. Data transfer from slave to slave is possible indirectly through the master. The Bluetooth® module implements Bluetooth® Protocol 2.0+EDR and can be configured as either master or slave.
PAGE 18
• I/O Modules Special Modules the real-time profile) are offered for this purpose. The most important diagnostic information is also displayed on the device via LEDs, so that the status can also be directly monitored without additional components at the installation site. Additional Information The Bluetooth® module starts either with the startup tool WAGO-I/OCHECK or function blocks of the WAGO-I/O-PRO CAA. The function blocks for configuration are contained in the library WAGO_Bluetooth_xx.
PAGE 19
I/O Modules Special Modules • 19 2.1.1.6.1 Bluetooth® Class of Device (CoD) The Class-of-Device (CoD) is a 24-bit field specifying the capabilities of a Bluetooth® device that is sent with the packet "Frequency Hop Synchronization" (FHS) during the device search. According to the Bluetooth® Standard, the CoD describes the capabilities of the device, thus supporting the search for devices with certain functionalities.
PAGE 20
• I/O Modules Special Modules Note The device subclass can be set by mailbox commands (see Appendix 6.3.5.9). The CoD can only be influenced by the device (sub)class. Changes in the Major Service Class or Major Device Class are not possible. When loading the factory settings, the device class is set to value 7 and the device subclass to value 6. This results in a CoD of 0x0020F8 for the Bluetooth® inquiry. Many stacks handle devices according to their CoD.
PAGE 21
I/O Modules Special Modules • 21 2.1.1.7 Operating Modes The Bluetooth® module has two different modes available. Each mode fulfills a certain function: • Configuration mode • Communication mode • in real-time profile • in ad hoc profile Note The Bluetooth® module is in configuration mode when the customer receives it. Note If a Bluetooth® master is operated in the real-time profile, up to 7 Bluetooth® slaves can be connected to the master.
PAGE 22
• I/O Modules Special Modules 2.1.1.7.1 Time Required for Initialization Waiting times occur during the initialization of the module (see Table 5): Table 5: Waiting times during normal operation of the module Waiting times for Seconds Connecting to the first slave ~5 Establishment of connection to a ready-to-receive slave 2-3 Successful establishment of connection by the master to another slave 2-3 Unsuccessful attempt to connect to another slave 3-5 Inquiry up to 10.
PAGE 23
I/O Modules Special Modules • 23 However, no data exchange takes place. As there is no cyclic process data, the general error bit continues to be set. With suitable settings, or immediately after initialization (if already set beforehand), the module can change to communication mode. If the module is started in communication mode, profiles are first loaded and quality-of-service procedures are prepared. Finally, the connection to preconfigured devices is configured. Display LED 1 lights up green.
PAGE 24
• I/O Modules Special Modules 2.1.1.7.2.1 Configuration Mode Mailbox commands are used in configuration mode to configure the Bluetooth® module for use. The commands are passed to the Bluetooth® module and carried out, for example, with WAGO-I/O-CHECK or by using function blocks of the WAGO-I/O-PRO CAA. Additional Information The mailbox commands for configuring the Bluetooth® module can be found in Appendix 6.1. In Section 3 and Appendix 6.5, the configuration is described using WAGO-I/O-CHECK.
PAGE 25
I/O Modules Special Modules • 25 2.1.1.7.2.2 Block Transfer The module parameters can be individually read and written using mailbox commands (see Appendix 6.1). It is also possible, as an alternative, to upload or download the complete configuration in 512-byte blocks. For example, a created or read out configuration block can be used to set up and configure all additional slaves. 512-byte blocks are sent. The transfer is opened each time by the group DLD_START described in Appendix 6.3.2.
PAGE 26
• I/O Modules Special Modules If there is an existing connection between WAGO devices, the time between the received packets is measured. If there is a significant timeout, warnings or error messages are sent (see Table 8). The typical time response is significantly more high performance than the upper limits given here for warnings and errors.
PAGE 27
I/O Modules Special Modules • 27 2.1.1.7.2.4 Communication Mode – Ad Hoc Profile "Ad hoc communication" is the "spontaneous" connection of devices. The main feature is the problem-free connection of very different types of devices. Therefore, the requirements for partner devices are less strict, making realtime communication impossible when using this profile. Note In the ad hoc profile, you can connect up to 6 slaves with one master (up to 7 slaves in the real-time profile).
PAGE 28
• I/O Modules Special Modules Table 9: Configuration of the Bluetooth® Packet Channel name Length Value in bytes Description CHANNEL_SELECT 1 0000 0001 Virtual channel selection, always 0x01 (0x01) STATUS_FLAGS 1 0000 0000 Status bits, always 0x00 for external devices (0x00) STATUS_DATA_SIZE 1 xxxx xxxx Data length in bytes, according to "cutoff" (see Section 2.1.1.8.1.2) DATA[1] 1 xxxx xxxx 1st byte of process data ... ... xxxx xxxx ...
PAGE 29
I/O Modules Special Modules • 29 2.1.1.7.2.5 Configuration of the Wireless Connection End devices are passive during configuration of the connection. Masters are also passive if the connection is configured through SPP or PAN by external devices. During the configuration of a connection, the status of a remote node (if it is authorized and entered on the external devices list) is tested.
PAGE 30
• I/O Modules Special Modules Note Wireless packets are only accepted and forwarded to the slave if a bilaterally authorized wireless connection exists; i.e., the Bluetooth® MAC address of the communication partner is entered in the table of permitted devices and the table entry has been activated for the creation of a connection (linked) in the master and slave.
PAGE 31
I/O Modules Special Modules • 31 2.1.1.8 Process Image Process data communication using the Bluetooth® protocol is cyclic. Data is requested, processed in a fixed sequence and exchanged between master and slaves. For configuration, diagnosis and register communication, data is transmitted acyclically between modules and locally connected applications - but not wirelessly (see Figure 8). Both the cyclic and acyclic communication share a transmission channel - the process image.
PAGE 32
I/O Modules Special Modules Table 10: Process data and register communication Process data communication Register Communication Mailbox switched on Mailbox switched off Control /status (1 byte long, from byte 0) Control /status (1 byte long, from byte 0) Control /status (1 byte long, from byte 0) Used internally (1 byte long, from byte 1) Used internally (1 byte long, from byte 1) Used internally (1 byte long, from byte 1) Register data (2 bytes long, from byte 2 to 3) Mailbox (Acyclical data, 6…1
PAGE 33
I/O Modules Special Modules • 33 If the mailbox bit (bit 25 in the control byte) is set to masked mailbox (see Table 10), the mailbox is masked by the cyclical data field. The masked field is then no longer valid; however, the non-masked field continues to be updated and may be used. If the mailbox flag is not set, the mailbox is masked and the cyclical data field is valid. The desired setting is confirmed by mirroring in bit 25 of the status byte.
PAGE 34
• I/O Modules Special Modules 2.1.1.8.1 Process Data Communication During active process data communication, cyclic process data is exchanged between master and slaves. 2.1.1.8.1.
PAGE 35
I/O Modules Special Modules Bit Value Description 22 23 24 25 26 27 2.1.1.8.1.1.1 • 35 0 Mailbox of the connected device covered 1 Mailbox of the connected device uncovered (warning of obsolete data) 0 No warning 1 Warning; e.g.
PAGE 36
• I/O Modules Special Modules If WAGO and external devices in different modes are connected with a WAGO master, the following guidelines apply for communication with each other (see Table 15): Table 15: Possible connection of a master with WAGO or external slaves Slave Master Real-time profile Ad hoc profile WAGO BT module Real-time profile WAGO BT module Ad hoc profile External device up to 7 devices - - up to 6 devices up to 6 devices In the ad hoc profile, a maximum of 7 devices can be acti
PAGE 37
I/O Modules Special Modules • 37 2.1.1.8.1.2 Process Image Mapping of the Master Up to seven slaves can be connected to one master. The process images of these slaves are mapped in the process image of the master. The process image consists of a fixed number of virtual plug-ins for the Bluetooth® master and slaves, designated as slots. Each slot is assigned a defined share of the process image by means of the process image mapping.
PAGE 38
I/O Modules Special Modules In doing so, the slaves only send "excerpts" of their process data to the master. The size of these "excerpts" is determined by "cutoff" in the configuration mode. The command "cutoff" is symmetrical for the data stream entering and exiting the master. The current data to be read and written, which are assigned slots in the master's process image, remain (see Figure 11). Master Slave Data Direction Slave Slave A Data Direction Master 38 • Slave B Slave C Slave X ...
PAGE 39
I/O Modules Special Modules • 39 In an additional example, we describe how the slot configurations behave in conjunction with a configuration of the master (process image size = 48 bytes): WAGO Table External Table W1 permitted cutoff = 6 E1 linked cutoff = 6 W2 linked cutoff = 6 E2 linked cutoff = 6 W3 free cutoff = 0 E3 linked cutoff = 6 W4 linked cutoff = 4 E4 free cutoff = 0 W5 linked cutoff = 6 E5 free cutoff = 0 W6 free cutoff = 0 E6 free cutoff = 0 W7 linked
PAGE 40
• I/O Modules Special Modules W6 has been processed in the configuration mode (ad hoc profile) • "AllowRemoteDevice" with MAC address of W6 • "Cutoff" for slot 6 raised from 0 to 6 W1 W2 W4 W5 W6 W7 E2 E3 0 48 Connection to E2 is disconnected (ad hoc profile) • UnbindRemoteDevice or end device discontinues the connection • Slot assignments are not changed • The last data is retained until the next reboot W1 W2 W4 W5 W7 E1 E2 (Data obsolete) E3 0 48 Control/status byte and internall
PAGE 41
I/O Modules Special Modules • 41 Slave's process image 12, 24, 48 Byte Usable process data (local) 10, 22, 46 Byte Control/status byte Byte used internally Slave Importing of individual information (cutoff) Cutoff Cutoff size entry into header Bluetooth® protocol header Bluetooth® protocoll Radio transmission Bluetooth® protocol header Master Assignment of slave process image to a slot within the master process image Control/status byte Byte used internally Slot1 Slot 2 Slot 3 Slot 4 will be
PAGE 42
• I/O Modules Special Modules Note The offset begins with the 3rd byte of the process image (after the control/status and internal bytes). 2.1.1.8.1.3 Process Data Mapping of the Slaves The process image of the master occupies only one slot (the first) in the process image of the slave. This first slot uses the entire process image size. In this case, it does not matter which cutoff size was set for slot 1 in the slave.
PAGE 43
I/O Modules Special Modules • 43 2.1.1.8.1.4 Up-to-Dateness of the Process Image WAGO master and WAGO slave regularly send their current process image independently of changes. If one party, (master or slave) no longer receives a new process image, the most recently received data remains current. If the master receives no new process image from a WAGO slave over a longer period of time, it signals this in its status byte (in the real-time profile, see Section 2.1.1.8.1.1).
PAGE 44
• I/O Modules Special Modules 2.1.1.8.2 Mailbox Communication Modules with mailbox functionality have an acyclic communication channel (mailbox) in the process image. The data exchange between module and application can be significantly expanded over this channel without enlarging the process image. The mailbox masks cyclic data in the process image if active. Depending on the module function, the remaining cyclic data is valid and available during mailbox communication (see page 32, Figure 9).
PAGE 45
I/O Modules Special Modules • 45 Superposed by mailbox With Mailbox Received process image Slot is not updated since superposed by mailbox Control/status byte Byte internally used Mailbox Slot 2 Slot 3 Slot 4 Process images of the remote devices Input process image Figure 14: Unmasking of the mailbox response in the input process image g064414e+89e Process data in the output process image is also masked when the mailbox is activated.
PAGE 46
• I/O Modules Special Modules 2.1.1.8.2.2 Setup If bit 5 in the control byte is set, the mailbox is unmasked. It begins with byte 3 of the process image after the control/status byte and the internal byte. It covers, depending on the set size, 6, 12 or 18 bytes of the process data (see page 32, Figure 9). In this area, the data is interpreted as mailbox data, so that commands (opcodes) can be sent here.
PAGE 47
I/O Modules Special Modules • 47 Table 17: Mailbox query Mailbox query Byte 27 26 25 24 23 22 21 20 0 0 0 1 0 0 0 0 0 1 - 2 Opcode 3 T - 4 Query parameter byte 0 … … max. 19 Query parameter byte 15 Opcode T - command code of the mailbox request - toggle bit - A mailbox request is started with a change. In the mailbox response, bits 25 and 26 of the status byte are set. Bit 25 confirms the activated mailbox. Bit 26 can be set.
PAGE 48
• I/O Modules Special Modules 2.1.1.8.2.3 Access Procedure Unmasking the mailbox by setting bit 5 in the control byte is required for executing mailbox commands. The module confirms this by setting bit 5 in the status byte. In order to execute a mailbox command, query parameters and the opcode of the command must be written in the output process image.
PAGE 49
I/O Modules Special Modules PIO Processing Times • 49 PII Cyclically updated process data Cyclically updated process data [XX.XX.XX.XX.XX.XX.XX.XX.XX.XX].00.00 [XX.XX.XX.XX.XX.XX.XX.XX.XX.XX].00.00 Switching on the mailbox, mailbox command IDLE (0x00) [XX.XX.XX.XX].[00.00.00.00].[00.00].00.20 Response to mailbox command IDLE (0x00) [XX.XX.XX.XX].[00.00.00.00].[00.00].00.60 Request for mailbox command GetLinkSignalStrength (0xD7) [XX.XX.XX.XX].[00.00.00].[20].[00.D7].00.
PAGE 50
• I/O Modules Special Modules 2.1.1.8.2.4 Mailbox Commands and Return Values In Appendix 6.1, you will find an overview of all mailbox commands sorted according to groups and opcodes (see Appendix 6.1.1) or alphabetically according to the names of the commands (see Appendix 6.1.2). A detailed description of each command can be found in the reference to Appendix 6.3. If a mailbox command is executed, the command is confirmed. The return value is transmitted in byte 3 of the process data. Section 2.1.1.
PAGE 51
I/O Modules Special Modules • 51 2.1.1.8.3 Register Communication Register communication allows direct access to 64 module registers. These serve exclusively for module configuration on the lowest level. Register communication is active if bit 27 is set.
PAGE 52
• I/O Modules Special Modules Active register communication is confirmed by the module in the status byte: Table 21: Configuration of the status byte Status byte Bit 27 26 Value/ Description 1 0 Bit Value 0 2 -2 5 25 24 23 22 21 20 Register number Description Reg. no. Register number 6 0 always 0 27 1 Always 1 during register communication (confirmation by the bus module) (Switch between process data communication and register communication) 2 2.1.1.8.3.
PAGE 53
I/O Modules Special Modules • 53 2.1.1.8.3.3 Register Structure 2.1.1.8.3.3.1 Parameter Data (register 56) Register 56 contains the parameter data to be read or written. Depending on the access type, either the I/O module (read parameters) or the fieldbus coupler (write parameters) will write data to the register.
PAGE 54
• I/O Modules Special Modules Parameter Value range Description A0 … A7 0 ...255 Word address of the parameter to be read/written. TGL_MS FALSE, TRUE Toggle bit to release new instructions from the application to the module. If TGL_SM and TGL_MS have the same status, no new instruction has been released yet. If the flags have different statuses, a new instruction has been released and is currently being processed.
PAGE 55
I/O Modules Special Modules • 55 2.1.1.8.3.4 Parameter Sets For use of the parameter channel; parameter sets are defined and indexed using parameter addresses (A7...A0). Module-specific parameters (parameters 0 through 249) and general system parameters (parameters 250 through 255) are differentiated. 2.1.1.8.3.5 Process of Parameter Transmission The parameter data exchange between the application and bus module is made via request/response process.
PAGE 56
• I/O Modules Special Modules 2.1.1.8.3.5.2 Set Factory Settings (System Parameters) Query (application) Parameter Value Description TGL_MS != TGL_SM Enter instruction PRM_RW = TRUE Write access A0...A7 255 Address of factory settings Response (bus module) Parameter Value Description TGL_SM == TGL_MS Instruction completed A0...
PAGE 57
I/O Modules Special Modules • 57 Response (bus module) Parameter Value Description TGL_SM == TGL_MS Instruction completed A0...A7 0...(n-1) Address parameter data mirrored TIMEOUT FALSE, TRUE Monitoring time expired BUF_OFL FALSE, TRUE Access outside the module parameter range PRM_ERR FALSE, TRUE Parameter/parameter set error PRM0... PRM15 0 ...
PAGE 58
• Configuration of a Bluetooth® Piconet Special Modules 3 Configuration of a Bluetooth® Piconet To configure a piconet, connect 2 to 8 Bluetooth® devices with each other.
PAGE 59
Configuration of a Bluetooth® Piconet Special Modules • 59 box"). In this case, you can also configure in such a way that the first slot has no device allocated to it and the size of the first slot corresponds to the mailbox size. This does mean, however, that one less device can be linked, but the up-to-dateness of the process data is not dependent on the masking or unmasking of the mailbox.
PAGE 60
• Tools for Configuring and Operating Special Modules 4 Tools for Configuring and Operating The Bluetooth® module is configured using the WAGO-I/O-CHECK software (Version 3 or later). The software's basic functionality is described separately in the WAGO-I/O-CHECK documentation. Additional Information You can obtain the WAGO-I/O-CHECK software (Version 3 or later) on CD ROM using order number 750-302. The CD ROM contains all programming files for the application.
PAGE 61
Tools for Configuring and Operating Configuring and Operating with WAGO-I/O-CHECK • 61 4.1 Configuring and Operating with WAGO-I/O-CHECK 4.1.1 User Interface The user interface of the Bluetooth® parameterization dialog is divided into the following areas (see Figure 20): Figure 20: User interface of the Bluetooth® parameterization dialog 1. Title bar (see Section 4.1.1.1) 2. Symbol bar (see Section 4.1.1.2) 3. Navigation (see Section 4.1.1.3) 4. Mode assignment (see Section 4.1.1.4) 5.
PAGE 62
• Tools for Configuring and Operating Configuring and Operating with WAGO-I/O-CHECK 4.1.1.1 Title Bar The position of the module within the node (as well as its name and item and version number) are displayed in the title bar of the parameterization dialog. 4.1.1.
PAGE 63
Tools for Configuring and Operating Configuring and Operating with WAGO-I/O-CHECK • 63 4.1.1.3 Navigation You can toggel between the different configuration areas of the module by using the navigation on the left side of the screen (see Figure 22).
PAGE 64
• Tools for Configuring and Operating Configuring and Operating with WAGO-I/O-CHECK 4.1.1.4 Mode Assignment Device Role is displayed in the top area, indicating whether the currently configured module is a master or a slave. The lower area, Operation Mode is used to assign the mode to the locally connected module. Using the buttons, choose whether the module is to be operated in either the configuration or communication mode (real-time or ad hoc profile) (see Figure 23).
PAGE 65
Tools for Configuring and Operating Configuring and Operating with WAGO-I/O-CHECK • 65 4.1.1.5 Parameterization Area In the parameterization area, the Bluetooth® module is configured and prepared for communication. This is described in further detail in the following sections. Changing and saving data To change settings in the Bluetooth® module, adjust the values displayed in the parameterization area. Altered settings are labeled with a change symbol .
PAGE 66
• Tools for Configuring and Operating Configuring and Operating with WAGO-I/O-CHECK 4.1.1.5.1 Settings Settings displays general module parameters (see Figure 25). Figure 25: Settings g064418e The following parameters can be changed and loaded to the module.
PAGE 67
Tools for Configuring and Operating Configuring and Operating with WAGO-I/O-CHECK • 67 Name Entry/Selection Description Authorization OFF No authorization required. Password For external devices, password entry is required. The "Link key" for the authorization must be recalculated for each established connection. Link key The "Link key" for the authorization does not have to be recalculated. After a first-time connection, entering the password is no longer necessary for an external device either.
PAGE 68
• Tools for Configuring and Operating Configuring and Operating with WAGO-I/O-CHECK 4.1.1.5.2 Net Forming "Net Forming" refers to the configuration of the Bluetooth® network. On the "net forming" side, devices are manually entered or automatically sought and bound for later communication. Figure 26: Net forming g064443e On the left side, all devices within range are displayed. You update the list by clicking on the [Search] button.
PAGE 69
Tools for Configuring and Operating Configuring and Operating with WAGO-I/O-CHECK • 69 Select Other to manually enter which CoD should be used to filter the search results (see Figure 27). Figure 27: Filter according to device classes g064489e To the right on the "net forming" page, the configured devices are displayed in two lists. The upper list contains WAGO devices using the real-time profile. The lower list contains both WAGO and/or external devices using the ad hoc profile.
PAGE 70
• Tools for Configuring and Operating Configuring and Operating with WAGO-I/O-CHECK 4.1.1.5.3 PI Mapping To undertake settings on the "PI mapping" (process image mapping) page, the process image size of the master must first be set. Use the [Data Frame] button in the symbol bar to open the dialog for entering the process image and mailbox sizes (see Figure 28).
PAGE 71
Tools for Configuring and Operating Configuring and Operating with WAGO-I/O-CHECK Figure 29: PI mapping • 71 g064445e On the left side, slots 1 through 7 for the real-time profile are displayed (for WAGO devices only). The right side displays slots 8 through 13 for the ad hoc profile (for WAGO and external devices).
PAGE 72
• Tools for Configuring and Operating Configuring and Operating with WAGO-I/O-CHECK Table 30: Display of a slot Setting g064447x-51x Description Identification of slots (1…7 real-time, 8…13 ad hoc) Display of the "UserFriendlyName", if provided Selection of slot color for the graphic display in the lower area (see Figure 29) Sliding controller for the size of the process data in bytes (cutoff size) assigned to a slot Entry field for the size of the process data in bytes (cutoff size) assigned to a slo
PAGE 73
Tools for Configuring and Operating Configuring and Operating with WAGO-I/O-CHECK • 73 4.1.1.5.4 Block Transfer This page displays the configuration block during uploading and downloading of the process data (see Figure 32). The menu item Block Transfer is only visible in the configuration mode.
PAGE 74
• Tools for Configuring and Operating Configuring and Operating with WAGO-I/O-CHECK Download [Configuration] Writes the configuration to the module. [Local Name] Writes the local name to the module. The name can be entered in the entry field. [Password] Writes the password in the locally connected module. The password can be entered in the entry field. 4.1.1.5.5 Diagnostics This page displays diagnostic information on the module status, the network and the quality of the connection (see Figure 33).
PAGE 75
Tools for Configuring and Operating Configuring and Operating with WAGO-I/O-CHECK • 75 The following displays are summarized under the header "Status" (see Table 32): Table 32: General status display Status Value Description Device Role Slave Device takes over the role of "slave" Master Device takes over the role of "master" (see also Appendix 6.3.5.20, "GetLocalDeviceRole") Operating Mode Communication Device is in communication mode (see also Appendix 6.3.3.
PAGE 76
• Tools for Configuring and Operating Configuring and Operating with WAGO-I/O-CHECK Status Signal Strength Available Channels Value Description -127...0 RSSI value/signal strength too weak 0 Signal strength very good 0...+127 Signal strength too strong (see Appendix 6.3.6.5, "GetLinkSignalStrength") < 39 Too many busy/defective channels 39…53 Some busy/defective channels > 53 Free/undisturbed channels (low interference) (see Appendix 6.3.6.
PAGE 77
Tools for Configuring and Operating Configuring and Operating with WAGO-I/O-CHECK Object Groups Status * Time monitoring Ok • 77 Watchdog Process image Ok Process image is defective A remote mailbox is active Intersystem communication Ok Interruption in SPI communication SPI is overloaded Error in the mailbox communication Configuration Ok Configuration altered Error in the network configuration * The meaning of the individual status reports can be found in Appendix 6.3.6.3.
PAGE 78
• Tools for Configuring and Operating Configuring the Bluetooth® Module 750-644 4.2 Configuring the Bluetooth® Module 750-644 In order to work with the Bluetooth® module 750-644, you must first set up the communication connection to your node. Then read the node configuration and select the desired module in the navigation or node view. Next, set the necessary process data and mailbox size in the parameterization dialog.
PAGE 79
Tools for Configuring and Operating Configuring the Bluetooth® Module 750-644 • 79 4.2.3 Role Assignment (Master/Slave) The Bluetooth® module can be configured as either master or slave. Choose Settings in the context menu of the selected module (node view or navigation) to open the parameterization dialog. In the navigation to the left, choose Settings. Click in the field to the right beside Device Role.
PAGE 80
• Tools for Configuring and Operating Configuring the Bluetooth® Module 750-644 4.2.5.2 Bind Bluetooth® Devices from Network Search Devices found by using the [Search] button are displayed in the list of devices within range. These devices can be chosen and transferred to one of the two lists using the [>>] button on the right side. In doing so, only WAGO devices are added to the upper list (real-time), while the lower list can take both WAGO devices and external devices (ad hoc).
PAGE 81
Tools for Configuring and Operating Configuring the Bluetooth® Module 750-644 • 81 4.2.6 Assigning Slave Process Data to Slots in the Master Choose Settings in the context menu of the selected module (node view or navigation) to open the parameterization dialog. Click on PI Mapping in the navigation area. The master only considers parts of the individual slave process images. Select the size of these parts (cutoff) using the slide control.
PAGE 82
• Fieldbus-specific Additions CANopen 5 Fieldbus-specific Additions 5.1 CANopen 5.1.1 Process Image Access The CANopen master accesses the Bluetooth® mailbox and process data in the coupler/controller using process data objects (PDOs). In the standard configuration, the Bluetooth® module data is mapped in serial PDOs. Each PDO can take up eight bytes of data. The maximum Bluetooth® module process image of 48 bytes therefore includes six PDOs.
PAGE 83
Fieldbus-specific Additions CANopen • 83 With a masked or unmasked mailbox, the following allocation of the process image size to the number of busy PDOs applies. Table 35: Allocation of the process image size to the number of busy PDOs Process image size 12 bytes 24 bytes 48 bytes no.
PAGE 84
• Fieldbus-specific Additions CANopen PDOs 1 through 4 are, according to the standard for digital and analog modules, reserved and occupied. Additional PDOs are not necessary for digital and analog modules. With the exception of a Bluetooth® module, no additional special modules are plugged in. The Bluetooth® module uses a process image of 12 bytes with a mailbox size of 6 bytes. The mailbox is unmasked. Therefore, the 5th and 6th PDOs are allocated to this module.
PAGE 85
Fieldbus-specific Additions CANopen 2 3 4 DI DI DI DI AI AI 402 402 402 452 5 6 7 BT 8 9 AO AO AI AI 550 452 10 11 12 AO AO AI AI 13 DO DO 750-337 1 DI DI • 85 602 644 602 550 452 602 504 600 Input image AI1 C1 AI1 C2 Status byte Mailbox Mailbox Mailbox Data Data AI2 C1 AI2 C2 AI3 C1 AI3 C2 DI1 C1-DI3 C4 Output image Control byte Mailbox Mailbox Mailbox Data Data AO1 C1 AO1 C2 AO2 C1 AO2 C2 DO1 C1-C4 TxPDO 1, DI1 C1 - DI3 C4 TxPDO 2, AI1 C1 - AI2 C2 TxPDO 3, AI3 C1 - C2
PAGE 86
• Fieldbus-specific Additions DeviceNet 5.2 DeviceNet 5.2.1 Process Image Access The DeviceNet master can access the Bluetooth® data in two ways. With predefined instances of the assembly object, digital and analog input and output data of a node are transmitted with a command to, or from, the master. The application in the master can then address the data in the memory. The data is stored in the master as it is for mapping in the coupler/controller.
PAGE 87
Fieldbus-specific Additions DeviceNet 2 3 4 DI DI DI DI AI AI 402 402 402 452 5 6 7 BT 8 9 AO AO AI AI 550 452 10 11 12 AO AO AI AI 13 DO DO 750-306 1 DI DI • 87 602 644 602 550 452 602 504 600 Input image (in words) Assembly Object Instance 9 Analog input data Assembly Object Instance 8 Digital input data Channel 1 Channel 2 Status Mailbox Mailbox Mailbox Data Data Channel 1 Channel 2 Channel 1 Channel 2 DI 1-12 Output image (in words) Assembly Object Instance 3 Ana
PAGE 88
• Fieldbus-specific Additions ETHERNET 5.3 ETHERNET 5.3.1 Process Image Access 5.3.1.1 MODBUS Protocol Bluetooth® module data is accessed with functions for reading and writing registers. Registers can be read and written in block or individually. A register includes two bytes. The allocation of the register to the input and output data of the module is dependent on the order and type of modules.
PAGE 89
Fieldbus-specific Additions ETHERNET 2 3 4 DI DI DI DI AI AI 402 402 402 452 5 6 7 BT 8 9 AO AO AI AI 550 452 10 11 12 AO AO AI AI 13 DO DO 750-342 1 DI DI • 89 602 644 602 550 452 602 504 600 Input register 0 1 2 3 4 5 6 7 8 9 10 11 12 Status Mailbox Mailbox Mailbox Data Data Access to data with FC 3, Start address 2, Length 6 Output register 0 1 2 3 4 5 6 7 8 9 10 Figure 39: Register allocation of a Bluetooth® module Control Mailbox Mailbox Mailbox Data Data Acces
PAGE 90
• Fieldbus-specific Additions ETHERNET 5.3.1.2 EtherNet/IP Protocol With the EtherNet/IP protocol, Bluetooth® data can be accessed in two ways. In predefined instances of the assembly object, digital and analog input and output data of a node are transmitted with a command to, or from, the Bluetooth® module. The application in the Bluetooth® module can then address the data in the memory. The data is stored in the module in the same manner as when mapping in the coupler/controller.
PAGE 91
Fieldbus-specific Additions ETHERNET 2 3 4 DI DI DI DI AI AI 402 402 402 452 5 6 7 BT 8 9 AO AO AI AI 550 452 10 11 12 AO AO AI AI 13 DO DO 750-341 1 DI DI • 91 602 644 602 550 452 602 504 600 Input image Assembly Object Instance 109 Analog input data Assembly Object Instance 108 Digital input data Channel 1 Channel 2 Status Mailbox Mailbox Mailbox Data Data Channel 1 Channel 2 Channel 1 Channel 2 DI 1-12 Output image Assembly Object Instance 103 Analog output data
PAGE 92
• Fieldbus-specific Additions PROFIBUS-DP 5.4 PROFIBUS-DP 5.4.1 Process Image Access The Bluetooth® module data is accessed through the process image of the PROFIBUS master. To ensure data consistency at a data width of 12 to 48 bytes, the data must be mapped with system functions for the consistent reading and writing to an appropriately large, reserved flag area. The data in this flag area can then be processed by the control program. 5.4.1.
PAGE 93
Fieldbus-specific Additions PROFIBUS-DP no. 4 5 6 Function Module Process image of the master * Identifier inputs outputs Analog input 750-452 2 AI/0…20 mA/diff.
PAGE 94
Fieldbus-specific Additions PROFIBUS-DP CALL SFC 15 LADDR := W#16#0A (write from output address AW10) RECORD := P#M114.
PAGE 95
Fieldbus-specific Additions LON • 95 5.5 LON The Bluetooth® module 750-644 is supported by the LON Fieldbus Coupler 750-319 and by the programmable LON Fieldbus Controller 750-819.
PAGE 96
• Appendix Mailbox Commands 6 Appendix 6.1 Mailbox Commands This appendix provides an overview of all available mailbox commands, sorted according to groups and opcodes (see Appendix 6.1.1) and according to mailbox commands (see Appendix 6.1.2). Which commands can be executed with which mailbox size is indicated by symbols as follows: ● Available The command can be executed.
PAGE 97
Appendix Mailbox Commands Mailbox commands GetRemotePiMapping Length query Opcode Description Length response • 97 May be executed with mailbox Page 6 12 18 ● ● ● 118 0x33 Query the remote process image parameters within the master process image 3 6 GetLocalDeviceName 0x40 Read device names 2 3…18 (●) (●) ● 120 SetLocalDeviceName 0x41 Set device names 3…18 2 (●) (●) ● 121 GetLocalMacID 0x42 Read MAC-ID 2 8 - ● ● 123 GetLocalIPAddress 0x43 Read IP address 2 6 ●
PAGE 98
• Appendix Mailbox Commands Mailbox commands Opcode Description Length query Length response May be executed with mailbox Page 6 12 18 GetAllowedRemoteDevices 0x84 Read back remote device from the authorization table 2 8 - ● ● 154 BindRemoteDevice 0x85 Activate authorized device 3 2 ● ● ● 156 UnbindRemoteDevice 0x86 Deactivate authorized device 3 2 ● ● ● 157 GetBoundRemoteDevices 0x87 Read access authorization for remote devices 2 3 ● ● ● 159 GetConnectionQoS
PAGE 99
Appendix Mailbox Commands • 99 6.1.
PAGE 100
• Appendix Mailbox Commands Mailbox command Opcode Description Length query Length response May be executed with mailbox Page 6 12 18 GetReconnectionTimePeriod 0x8A Read time between attempts to establish connection 2 4 ● ● ● 163 GetRemoteDeviceMacID 0x81 Read MAC-ID of a remote Bluetooth® device 2 9 - ● ● 148 GetRemoteDeviceName 0x82 Read device name of a remote Bluetooth® device 2 GetRemotePiMapping 0x33 Query the remote process image parameters within the master proces
PAGE 101
Appendix Return Values of Mailbox Commands • 101 6.
PAGE 102
• Appendix Mailbox Command References 6.3 Mailbox Command References In this section, the requirements for the execution of each mailbox command are represented as follows: Mailbox size (6, 12 or 18 bytes) ● Available The command can be executed. (●) Available to a limited extent Execution of the command is possible, but only as much data as is possible for the current mailbox size is returned. - Not available The command cannot be executed.
PAGE 103
Appendix Mailbox Command References • 103 In addition, configuration of the bytes is described during query and response with arguments and return values. If no return values are present, the related tables are presented in gray. Note If the query is smaller than the mailbox, the remaining bytes in the mailbox should be filled with 0x00 during the query. If the size of the response is smaller than the size of the mailbox, the remaining bytes in the mailbox of the module are filled with 0x00.
PAGE 104
• Appendix Mailbox Command References 6.3.1 General Commands 6.3.1.1 No Task (IDLE, 0x00) If the opcode = 0x00, no task is performed. This command is available in all operating modes for all mailbox sizes. Conditions Mailbox size Operating mode/profile Device role 6 12 18 Config. Realtime Ad hoc Master ● ● ● ● ● ● ● Slave Save config.
PAGE 105
Appendix Mailbox Command References • 105 6.3.2 Block Transfer 6.3.2.1 Download Start of a Block (DLD_START, 0x01) The block transfer starts with the call up. A new DLD_START with no previous DLD_END breaks the transfer off and initializes a new transfer. The command block is concluded by DLD_END. Conditions Mailbox size Operating mode/profile Device role 6 12 18 Config. Realtime Ad hoc Master Slave Save config.
PAGE 106
• Appendix Mailbox Command References Response Byte 27 26 25 0 1 24 23 22 21 20 MBX_DLD_START T MBX_RESULT 2 MBX_DLD_RESULT Return values Parameter Value Description MBX_DLD_ RESULT DLD_OK (0x00) No error. The block transfer has been started. DLD_DOWNLOAD_ NOT_STARTED (0x01) The block transfer has not been started. An undefined block is supposed to be transmitted. DLD_OK_ABORTED (0x02) A block transfer is currently active. No new transfer is being started.
PAGE 107
Appendix Mailbox Command References • 107 6.3.2.2 Continuation of a Block Download or Upload (DLD_CONT, 0x02) With call up, the uploading/downloading of a block is continued. During an upload of data to the module, the data bytes from byte 2 may be ignored. Conditions Mailbox size Operating mode/profile Device role 6 12 18 Config. Realtime Ad hoc Master ● ● ● ● - - ● Slave Save config.
PAGE 108
• Appendix Mailbox Command References Response Byte 27 26 25 0 1 24 23 22 21 20 MBX_DLD_CONT T MBX_RESULT 2 DATA 3 DATA 4 DATA 5 DATA 6 OPTIONAL DATA ... ... 33 OPTIONAL DATA Return values Parameter Value Description MBX_RESULT MBX_CMD_OK No error occurred. The block transfer has been continued. MBX_CMD_DENIED_NOT_ APPLICABLE There is no active transfer. The command is invalid. MBX_CMD_OUT_OF_RANGE An attempt was made to transfer more than 512 bytes.
PAGE 109
Appendix Mailbox Command References • 109 6.3.2.3 End a Block Download or Upload (DLD_END, 0x03) With call up, the uploading and downloading of a block is ended. Conditions Mailbox size Operating mode/profile Device role 6 12 18 Config. Realtime Ad hoc Master Slave Save config. Restart ● ● ● ● - - ● ● ●* ●* * A restart is only conducted after successful writing operations in the configuration mode.
PAGE 110
• Appendix Mailbox Command References Return values Parameter Value MBX_RESULT MBX_CMD_OK MBX_CMD_GENERAL_ERROR DLD_RESULT DLD_OK (0x00) Description Transfer successful An error has occurred. More detailed information in DLD_RESULT No error occurred DLD_ERROR_DOWNLOAD_NOT There is no active transfer. _STARTED (0x01) The command is invalid. DLD_ERROR_CHECKSUM (0x32) Checksum error DLD_ CHECKSUM DLD_ERROR_UNDERFLOW (0x33) Underrun, too little data.
PAGE 111
Appendix Mailbox Command References • 111 6.3.3 Maintenance and Firmware 6.3.3.1 Warm Start of the Bluetooth® Subsystem (RebootHost, 0x10) With call up, the Bluetooth® subsystem is restarted. All wireless connections are broken off. Note This command causes a restart with no prior saving of the configuration. Therefore, changes made since the last time the configuration was saved are lost. Note If "RebootHost" is called up, all wireless connections are broken off.
PAGE 112
• Appendix Mailbox Command References 6.3.3.2 Saving the Configuration with Subsequent Warm Start (FlashRebootHost, 0x11) With call up, the current configuration of the Bluetooth® subsystem is written in the flash memory. Then the Bluetooth® subsystem is restarted. Note If "RebootHost" is called up, all wireless connections are broken off. Conditions Mailbox size Operating mode/profile Device role 6 12 18 Config. Realtime Ad hoc Master Slave Save config.
PAGE 113
Appendix Mailbox Command References • 113 6.3.3.3 Read Host Firmware Version (GetHostFwVersion, 0x12) With call up, version information is read by firmware components of the Bluetooth® subsystem. Conditions Mailbox size Operating mode/profile Device role 6 12 18 Config. Realtime Ad hoc Master ● ● ● ● - - ● Slave Save config.
PAGE 114
• Appendix Mailbox Command References Return values Parameter Value Description MBX_RESULT MBX_CMD_INVALID_ARG Invalid value for MBX_FW_ID MBX_FW_ID MBX_CM_GETHOSTFWVERSION Version of boot loader _BOOTLOADER (0x01) MBX_CM_GETHOSTFWVERSION Version of Bluetooth® subsystem _FIRMWARE (0x02) MBX_CM_GETHOSTFWVERSION Version of configura_CONFIGURATION (0x03) tion MBX_VN_MAJOR [0...255] Main version number MBX_VN_MINOR [0...255] Subversion number MBX_VN_RELEASE [0...
PAGE 115
Appendix Mailbox Command References • 115 6.3.3.4 Read Version of Baseband Controller Firmware (GetBbFwVersion, 0x13) With call up, the version information for the baseband controller is read. Conditions Mailbox size Operating mode/profile Device role 6 12 18 Config. Realtime Ad hoc Master Slave Save config.
PAGE 116
• Appendix Mailbox Command References 6.3.4 Process Image 6.3.4.1 Determine the Size of a Slot for Data Transfer in the Master Process Image (SetRemotePiSize, 0x32) With this command, the process image of a remote bus module is limited to n bytes within the master process image. Therefore, the total of all slave process images in the master may not be larger than the set master process image - 2. This is because two bytes of the total size are necessary for the control/status byte and a reserved byte.
PAGE 117
Appendix Mailbox Command References • 117 Arguments Parameter Value Description MBX_TARGET_TABLE_ Bit 0…3 Table Index AND_INDEX Index 0...6 for WAGO devices of slots 1...7 Index 0...5 for external devices of slots 8...12 Bit 4…7 Target table "2" for WAGO_DEVICE (slots 1...7) "1" for EXTERNAL_DEVICE (slots 8...12) CUTOFF_N_BYTES [0...46] Number of bytes after which the slave process image is cut off. The redundant bytes will be lost.
PAGE 118
• Appendix Mailbox Command References 6.3.4.2 Query the Remote Process Image Parameters within the Master Process Image (GetRemotePiMapping, 0x33) With this command, the settings for a slot in the local process image are queried. There are 13 slots available. Slots 1 through 7 are occupied by the fields of the WAGO device table and slots 8 through 13 by the fields of the table of external devices. Conditions Mailbox size Operating mode/profile Device role 6 12 18 Config.
PAGE 119
Appendix Mailbox Command References • 119 Return values Parameter Value Description MBX_RESULT MBX_CMD_INVALID _ARG No valid target table has been chosen. MBX_CMD_OUT_OF _RANGE The indicated index is too large. MBX_DEVICE_INDEX [0...12] Slot of the slave process image within the master process image OFFSET [0...45] Position of the first byte of the slot in the local process image relative to the C/S byte. Slot 1 always has an offset of 0.
PAGE 120
• Appendix Mailbox Command References 6.3.5 Device Configuration 6.3.5.1 Read the Local Device Name(GetLocalDeviceName, 0x40) The characters of the Bluetooth® name of the local bus module are read by this query. The number of characters returned depends on the configured name, but has a maximum of (mailbox size - 3). Note The complete device name can be a maximum of 15 characters. The complete device name can be queried with DLD commands regardless of the mailbox size.
PAGE 121
Appendix Mailbox Command References • 121 6.3.5.2 Write the Local Device Name (SetLocalDeviceName, 0x41) With this command, the Bluetooth® name of the local bus module is set. The normal set of ASCII characters is available. Note The use of special characters (e.g. word wraps) is possible but should be avoided. The complete device name can be a maximum of 15 characters. The complete device name can be read and written with DLD commands regardless of the mailbox size.
PAGE 122
• Appendix Mailbox Command References Return values Parameter Value Description MBX_RESULT MBX_CMD_OUT_OF_RANGE MBX_NAME_LENGTH is equal to 0 or greater than (mailbox size - 3) WAGO-I/O-SYSTEM 750 I/O Modules
PAGE 123
Appendix Mailbox Command References • 123 6.3.5.3 Read Local MAC ID (GetLocalMacID, 0x42) With this command, the Bluetooth® MAC-ID (48-bit address) of the local Bluetooth® module is read. Conditions Mailbox size Operating mode/profile Device role 6 12 18 Config. Realtime Ad hoc Master - ● ● ● - - ● Slave Save config.
PAGE 124
• Appendix Mailbox Command References 6.3.5.4 Read Local IP Address (GetLocalIPAddress, 0x43) With this command, the IP address (IPv4) of the local bus module is read. Conditions Mailbox size Operating mode/profile Device role 6 12 18 Config. Realtime Ad hoc Master Slave Save config.
PAGE 125
Appendix Mailbox Command References • 125 6.3.5.5 Set Local IP Address (SetLocalIPAddress, 0x44) With this command, the IP address (IPv4) of the local bus module is read. Conditions Mailbox size Operating mode/profile Device role 6 12 18 Config. Realtime Ad hoc Master Slave Save config.
PAGE 126
• Appendix Mailbox Command References 6.3.5.6 Read Local Subnet Mask (GetLocalSubnetMask, 0x45) With this command, the subnet mask (IPv4) of the local bus module is read. Conditions Mailbox size Operating mode/profile Device role 6 12 18 Config. Realtime Ad hoc Master Slave Save config.
PAGE 127
Appendix Mailbox Command References • 127 6.3.5.7 Set Local Subnet Mask (SetLocalSubnetMask, 0x46) With this command, the subnet mask (IPv4) of the local bus module is written. Conditions Mailbox size Operating mode/profile Device role 6 12 18 Config. Realtime Ad hoc Master Slave Save config.
PAGE 128
• Appendix Mailbox Command References 6.3.5.8 Read Local WAGO Device Class (GetLocalDeviceClass, 0x47) With this command, the WAGO device class of the local bus module is read. Types of modules can be differentiated using the device class. A grouping of modules according to their tasks is also possible. When searching for modules with a certain device class, an inquiry using the Bluetooth® Class-of-Device can help.
PAGE 129
Appendix Mailbox Command References • 129 6.3.5.9 Write Local Device Class (SetLocalDeviceClass, 0x48) With this command, the WAGO device class of the local bus module is written. Types of modules can be differentiated using the device class. A grouping of modules according to their tasks is also possible. When searching for modules with a certain device class, an inquiry using the Bluetooth® Class-ofDevice can help. The device classes have only an indirect relation to the Bluetooth® Class-of-Device.
PAGE 130
• Appendix Mailbox Command References 6.3.5.10 Read Local Operation Mode (GetLocalOperationMode, 0x49) With this command, the operating mode and communication profile of the local Bluetooth® module are read. Conditions Mailbox size Operating mode/profile Device role 6 12 18 Config. Realtime Ad hoc Master ● ● ● ● ● ● ● Slave Save config.
PAGE 131
Appendix Mailbox Command References 6.3.5.11 • 131 Set Local Operation Mode (SetLocalOperationMode, 0x4A) With call up, the operating mode and communication profile of the Bluetooth® subsystem are set. The call up is followed by a warm start of the Bluetooth® bus module in the chosen operating mode, saving any changes made to the configuration.
PAGE 132
• Appendix Mailbox Command References Response Byte 27 0 1 26 25 24 23 22 21 20 MBX_SETLOCALOPERATIONMODE T MBX_RESULT Return values Parameter Value Description MBX_RESULT MBX_CMD_INVALID_ARG An invalid value for one of the arguments or an invalid combination was chosen.
PAGE 133
Appendix Mailbox Command References 6.3.5.12 • 133 Read Local Encryption Mode (GetLocalEncryptionMode, 0x4D) With call up, the encryption mode for the wireless transmission is read. Conditions Mailbox size Operating mode/profile Device role 6 12 18 Config. Realtime Ad hoc Master Slave Save config.
PAGE 134
• Appendix Mailbox Command References 6.3.5.13 Set Local Encryption Mode (SetLocalEncryptionMode, 0x4E) With this command, the encryption of the Bluetooth® data transmission is activated or deactivated. This setting can be done independently of the device role, but only affects the master. If encryption is activated, devices that do not use encryption cannot connect. Note Encryption can be activated without activating an authentication.
PAGE 135
Appendix Mailbox Command References 6.3.5.14 • 135 Read Local Authentication Mode (GetLocalAuthenticationMode, 0x4F) With call up, the locally set authentication mode of the Bluetooth® subsystem is read. Conditions Mailbox size Operating mode/profile 6 12 18 Config. Realtime ● ● ● ● - Device role Ad hoc Master - ● Slave Save config.
PAGE 136
• Appendix Mailbox Command References 6.3.5.15 Set Local Authentication Mode (SetLocalAuthenticationMode, 0x50) With the call up "SetLocalAuthenticationMode", the local authentication mode of the Bluetooth® subsystem is set. If the authentication is activated, the modules authenticate each other at each connection establishment. This process occurs, per Bluetooth® standard, under cryptographic safeguards.
PAGE 137
Appendix Mailbox Command References • 137 Request Byte 27 0 26 25 24 23 22 21 20 MBX_SETAUTHENTICATIONMODE 1 T MBX_AUTHENTICATION_MODE Arguments Parameter Value Description MBX_AUTHENTICATION _MODE MBX_AUTHENTICATION _NONE (0x01) No authorization necessary MBX_AUTHENTICATION _PIN (0x02) Authentication is conducted with a PIN created from the password at each establishment of a connection.
PAGE 138
• Appendix Mailbox Command References 6.3.5.16 Read Local Bluetooth® Password (GetLocalPassphrase, 0x51) With call up, the encryption mode for the wireless transmission is read out. The password is transmitted as a byte value representation of ASCII characters and is at least 4 characters long. Conditions Mailbox size Operating mode/profile Device role 6 12 18 Config. Realtime Ad hoc Master Slave Save config.
PAGE 139
Appendix Mailbox Command References 6.3.5.17 • 139 Write Local Bluetooth® Password (SetLocalPassphrase, 0x52) With this command, the local password can be configured. The module calculates the "Link Key" from the locally saved password. This is necessary during active authentication for the establishment and data encryption. The Bluetooth® password must therefore be identical for all devices intended to communicate with each other. Note Security quality depends on the selected password.
PAGE 140
• Appendix Mailbox Command References Response Byte 27 0 1 26 25 24 23 22 21 20 MBX_SETLOCALPASSPHRASE T MBX_RESULT Return values Parameter Value Description MBX_RESULT MBX_CMD_INVALID_ARG The password length is shorter than 4 characters and is not long enough or MBX_PASSPHRASE_Length indicates a value that is larger than the payload of the mailbox.
PAGE 141
Appendix Mailbox Command References 6.3.5.18 • 141 Delete Locally Saved Authorization (EraseLocalAuthentication, 0x53) With call up, the locally saved information for authorization is deleted. Then a warm start is carried out. Conditions Mailbox size Operating mode/profile Device role 6 12 18 Config.
PAGE 142
• Appendix Mailbox Command References 6.3.5.19 Read Length of the Flash Configuration (GetLocalDeviceConfigLen, 0x54) With call up, the length (in bytes) of the locally saved configuration in the flash of the Bluetooth® subsystem is passed back. This information is used by the PLC for interpretation of data from the block commands. Conditions Mailbox size Operating mode/profile Device role 6 12 18 Config. Realtime Ad hoc Master ● ● ● ● - - ● Slave Save config.
PAGE 143
Appendix Mailbox Command References 6.3.5.20 • 143 Read Role of the Local Device (GetLocalDeviceRole, 0x55) This command queries the role of the local Bluetooth® module in the piconet (master or slave). Conditions Mailbox size Operating mode/profile Device role 6 12 18 Config. Realtime Ad hoc Master ● ● ● ● ● ● ● Slave Save config.
PAGE 144
• Appendix Mailbox Command References 6.3.5.21 Set Role of the Local Device (SetLocalDeviceRole, 0x56) This command establishes the role of the local Bluetooth® module in the piconet (master or slave). Conditions Mailbox size Operating mode/profile Device role 6 12 18 Config. Realtime Ad hoc Master ● ● ● ● - - ● Slave Save config.
PAGE 145
Appendix Mailbox Command References 6.3.5.22 • 145 Restore Factory Settings (SetFactorySettings, 0x57) With call up, the locally saved configuration in the flash is overwritten by the factory settings. The Bluetooth® subsystem is then restarted. Conditions Mailbox size Operating mode/profile Device role 6 12 18 Config.
PAGE 146
• Appendix Mailbox Command References 6.3.5.23 Search for Remote Bluetooth® Device in the Wireless Network (ScanRemoteDevices, 0x80) With call up, the search for remote bus modules in the wireless network is triggered. The search process is asynchronous; i.e., the result is not immediately available. As long as the search runs, the wireless module is not available for any other function. Functions that do not use the wireless module are carried out normally.
PAGE 147
Appendix Mailbox Command References • 147 Return values Parameter Value MBX_RESULT MBX_CMD_DENIED_BUSY A running search process or another function is blocking the wireless module. MBX_COD 24 bits WAGO-I/O-SYSTEM 750 I/O Modules Description Class-of-Device for those devices that are to be sought. With MBX_COD = 0x0, the CoD is ignored.
PAGE 148
• Appendix Mailbox Command References 6.3.5.24 Read MAC-ID of a Remote Bluetooth® Device (GetRemoteDeviceMacID, 0x81) This command accesses a list of visible Bluetooth® devices in the environment and queries the Bluetooth® MAC-ID of a remote device. The prerequisite for this command is the prior execution of a search process with the command "ScanRemoteDevices", which initiates the creation of this list.
PAGE 149
Appendix Mailbox Command References • 149 Return values Parameter Value Description MBX_RESULT MBX_CMD_DENIED_ The search process has not yet been BUSY stated or concluded. MBX_CMD_OUT_OF_ The indicated index is greater than or RANGE equal to the number of the devices found. Or, no Bluetooth® device with the indicated Class-of-Device was found.
PAGE 150
• Appendix Mailbox Command References 6.3.5.25 Read Device Name of a Remote Bluetooth® Device (GetRemoteDeviceName, 0x82) With call up, the name of a disconnected I/O module in the wireless network is queried (compare Appendix 6.3.5.24, GetRemoteDeviceMacID). Since this information must be requested via remote device and no quick response can be guaranteed, the first request starts with the name resolution. However, it responds with MBX_CMD_DENIED_BUSY without returning the name.
PAGE 151
Appendix Mailbox Command References • 151 Arguments Parameter Value Description MBX_DEVICE_INDEX [0 ...15] List index for the return of the device name. The index must be smaller than the number of devices found in the search process. Response Byte 27 0 1 26 25 24 23 22 21 20 MBX_GETREMOTEDEVICENAME T MBX_RESULT 2 MBX_NAME_LENGTH 3 CHAR1 ... ...
PAGE 152
• Appendix Mailbox Command References 6.3.5.26 Enter External Device in the Table of Authorized Devices (AllowRemoteDevice, 0x83) This command allows a remote device to access the local device. The MACID of the remote device is also entered in a table of the Bluetooth® subsystem. Two device types are differentiated. Both types are entered in different tables: WAGO devices for real-time communication: WAGO_DEVICE (0x20...
PAGE 153
Appendix Mailbox Command References • 153 Request Byte 27 0 26 25 24 23 22 21 20 MBX_ALLOWREMOTEDEVICE 1 T - 2 MBX_TARGET_TABLE_AND_ INDEX 3 MAC_ID_Byte 0 (LSB) 4 MAC_ID_Byte 1 5 MAC_ID_Byte 2 6 MAC_ID_Byte 3 7 MAC_ID_Byte 4 8 MAC_ID_Byte 5 (MSB) Arguments Parameter Value Description MBX_TARGET_TABLE_ Bit 0…3 Table Index AND_INDEX Index 0...6 for WAGO devices of slots 1...7 Index 0…5 for external devices of slots 8...12 Bit 4…7 Target table "2" for WAGO_DEVICE (slots 1...
PAGE 154
• Appendix Mailbox Command References 6.3.5.27 Read Back External Device from the Table of Authorized Devices (GetAllowedRemoteDevices, 0x84) This command reads out and returns the MAC-ID of a remote device from the table of authorized devices of the Bluetooth® subsystem. There are two types of external devices entered in different tables: WAGO devices for real-time communication: WAGO_DEVICE (0x20...
PAGE 155
Appendix Mailbox Command References • 155 Response Byte 27 0 1 26 25 24 23 22 21 20 MBX_GETALLOWEDREMOTEDEVICE T MBX_RESULT 2 MAC_ID_Byte 0 (LSB) 3 MAC_ID_Byte 1 4 MAC_ID_Byte 2 5 MAC_ID_Byte 3 6 MAC_ID_Byte 4 7 MAC_ID_Byte 5 (MSB) Return values Parameter Value MBX_RESULT MBX_CMD_OUT_OF_RANGE An index greater than 6 was used. MAC ID Byte n WAGO-I/O-SYSTEM 750 I/O Modules Description MBX_CMD_INVALID_ARG No valid target table chosen. [0...
PAGE 156
• Appendix Mailbox Command References 6.3.5.28 Grant Access Authorization for a Device (BindRemoteDevice, 0x85) A remote device from the table of authorized devices in the Bluetooth® subsystem is activated for connection establishment. The MAC-ID of the remote device must have been entered in the table of authorized devices beforehand (see Appendix 6.3.5.26). Conditions Mailbox size Operating mode/profile Device role 6 12 18 Config.
PAGE 157
Appendix Mailbox Command References 6.3.5.29 • 157 Delete Access Authorization for a Device (UnbindRemoteDevice, 0x86) Access authorization of a remote device is deactivated. When this occurs, the MAC-ID entered in the table space and associated data, such as the "UserFriendlyName" are retained. However no connection to the device is established and any pre-existing connection is interrupted.
PAGE 158
• Appendix Mailbox Command References Return values Parameter Value Description MBX_RESULT MBX_CMD_OUT_OF_RANGE An index greater than 6 was used. MBX_CMD_INVALID_ARG No valid target table chosen.
PAGE 159
Appendix Mailbox Command References 6.3.5.30 • 159 Read Access Authorization for Remote Devices (GetBoundRemoteDevices, 0x87) This command reads back which of the remote devices entered in the table have an activated access authorization. The authorization can be activated using the command "BindRemoteDevice" and deactivated using "UnbindRemoteDevice". Conditions Mailbox size Operating mode/profile Device role 6 12 18 Config. Realtime Ad hoc Master Slave Save config.
PAGE 160
• Appendix Mailbox Command References 6.3.5.31 Read Back the QoS Settings (GetConnectionQoS, 0x88) This command reads back the settings of the Quality-of-Service (QoS) of a connection. Conditions Mailbox size Operating mode/profile Device role 6 12 18 Config. Realtime Ad hoc Master ● ● ● ● - - ● Slave Save config.
PAGE 161
Appendix Mailbox Command References 6.3.5.32 • 161 Set the QoS Settings (SetConnectionQoS, 0x89) This command assigns the settings of the Quality-of-Service (QoS) for a connection. The settings do not take effect until the module is switched over to master mode. Note The master can connect to a maximum of 3 slaves with activated QoS. QoS can only be set for WAGO devices. It improves latency by reducing deviations (outliers).
PAGE 162
• Appendix Mailbox Command References Response Byte 27 0 1 26 25 24 23 22 21 20 MBX_SETCONNECTIONQOS T MBX_RESULT Return values Parameter Value Description MBX_RESULT MBX_CMD_OUT_OF_RANGE An index greater than 6 was used. MBX_CMD_INVALID_ARG No valid target table was used or an invalid value for MBX_QOS_SETTINGS was chosen.
PAGE 163
Appendix Mailbox Command References 6.3.5.33 • 163 Read Back Time Settings - Between Two Attempts to Establish a Connection (GetReconnectionTimePeriod, 0x8A) This command reads back the waiting time between two attempts to reestablish the connection to a bus module. Conditions Mailbox size Operating mode/profile Device role 6 12 18 Config. Realtime Ad hoc Master Slave Save config.
PAGE 164
• Appendix Mailbox Command References 6.3.5.34 Set Time Settings - Between Two Attempts to Establish a Connection (SetReconnectionTimePeriod, 0x8B) This command sets the waiting time for the master between two attempts before attempting to establish a new connection with a slave. The settings do not take effect until the module is switched over to master mode. When establishing a network in communication mode, the master first attempts to connect all authorized slaves.
PAGE 165
Appendix Mailbox Command References • 165 Arguments Parameter Value Description MBX_RECONNECTTIME Time in seconds Minimum time in seconds between two attempts to re-establish a connection when the previous attempt has failed.
PAGE 166
• Appendix Mailbox Command References 6.3.5.35 Read the User-Friendly Name of an Authorized Device (GetUserfriendlyName, 0x8C) This query can read the user-friendly name to an entry in the list of authorized devices. If the name is too long for the actual size of the mailbox, then the first (mailbox size - 3) characters are given out. The actual length of the name returns the value of MBX_NAME_LENGTH. Conditions Mailbox size Operating mode/profile Device role 6 12 18 Config.
PAGE 167
Appendix Mailbox Command References • 167 Return values Parameter Value Description MBX_RESULT MBX_CMD_OUT_OF_RANGE An index greater than 6 was used MBX_CMD_INVALID_ARG No valid target table has been chosen. MBX_NAME_LENGTH [0…15] Number of characters of the complete name CHARn [0...
PAGE 168
• Appendix Mailbox Command References 6.3.5.36 Write the User-Friendly Name of an Authorized Device (SetUserfriendlyName, 0x8D) This command adds any alias to an entry in the list of authorized devices. This name allows the user to give an intuitive name to the relevant removed (remote) device, such as "Pump_001", "Gate4" or "Bus node_002". This does not impact the Bluetooth device name of the remote device, as the alias is stored in the local device.
PAGE 169
Appendix Mailbox Command References • 169 Arguments Parameter Value Description MBX_TARGET_TABLE_ AND_INDEX Bit 0…3 Table Index Index 0...6 for WAGO devices of slots 1...7 Index 0...5 for external devices of slots 8...12 Bit 4…7 Target table "2" for WAGO_DEVICE (slots 1...7) "1" for EXTERNAL_DEVICE (slots 8...12) MBX_NAME_LENGTH [0...15] Number of characters of the complete name CHARn [0...
PAGE 170
• Appendix Mailbox Command References 6.3.6 Diagnostics 6.3.6.1 Read Status of the Local Bus Module (GetLocalDeviceStatus, 0xD0) Call up returns the type of bus module, operating mode, operating profile and a general diagnostic status. Note The bus module type is set via "SetLocalDeviceRole" commands (see Appendix 6.3.5.21) and read back via "GetLocalDeviceRole" (see Appendix 6.3.5.20). Both the operation mode and operation profile are set via "SetLocalOperationMode"“ (see Appendix 6.3.5.
PAGE 171
Appendix Mailbox Command References • 171 Return values Parameter Value Description MBX_DEVICE_ROLE MBX_ROLE_COORDINATOR (0x01) Device role of master reserved (0x02) Reserved MBX_ROLE_ENDDEVICE (0x03) Device role of slave MBX_CM_OPMODE_CONF (0x01) Configuration mode MBX_CM_OPMODE_COMM (0x02) Communication mode MBX_OPMODE_ID MBX_COMMROFILE _ID MBX_DIAGNOSTIC _STATE WAGO-I/O-SYSTEM 750 I/O Modules MBX_CM_OPPROFILE_REALTIME Real-time profile (0x01) (communication mode) MBX_CM_OPPROFILE_ADHO
PAGE 172
• Appendix Mailbox Command References 6.3.6.2 Read Status of the Wireless Network (GetNetworkStatus, 0xD1) Call up returns information on the status of the wireless network. Information on WAGO devices and external devices is recorded. Note Because no wireless connection is established in configuration mode, MBX_NETWORK_FAILED (0x01) is always returned in this case. Since no connections are established in configuration mode, the other arguments of this command in this mode always deliver "0".
PAGE 173
Appendix Mailbox Command References • 173 Return values Parameter Value MBX_NETWORK MBX_NETWORK_FAILED _STATE (0x01) Description Configured network not established (e.g., in configuration mode) MBX_NETWORK_OK (0x02) Configured network successfully established. MBX_NETWORK_ INCONSISTENT (0x03) At least one, but not all, configured connections could be established. Assigned bit = 1 Assigned device from the table of WAGO devices is linked and connected.
PAGE 174
• Appendix Mailbox Command References 6.3.6.3 Read Diagnostic Information (GetStatusMessage, 0xD2) The command returns diagnostic information on occurring errors and warnings from the local bus module. When querying, a concrete object identification MBX_OBJECT_ID must be indicated. The response then always contains the same MBX_OBJECT_ID plus a defined status report MBX_STATE_MESSAGE.
PAGE 175
Appendix Mailbox Command References • 175 Arguments Parameter Value Description MBX_ MBX_OBJECTID_GROUP_MASK OBJECT _ID MBX_OBJECTID_GROUP_SYSTEM 0xF000 0x0000 Status of whole system MBX_OBJECTID_GROUP_WIRELESS 0x1000 Status of wireless connections MBX_OBJECTID_GROUP_TIMING 0x2000 Status of time monitoring MBX_OBJECTID_GROUP_PA 0x3000 Status of process image MBX_OBJECTID_GROUP_ISC 0x4000 Status of intersystem communication MBX_OBJECTID_GROUP_CONFIG 0x5000 Status of configuration MBX_O
PAGE 176
• Appendix Mailbox Command References Return values Parameter Value Description MBX_CMD_ RESULT MBX_CMD_DENIED_NOT_ IMPLEMENTED Non-implemented MBX_OBJECT_ID MBX_CMD_DENIED_ BUSY Another MBX command actively being processed MBX_CMD_INVALID_ARG Invalid object ID MBX_ OBJECT _ID See Appendix 6.3.6.3.1, Establishment of the Object ID.
PAGE 177
Appendix Mailbox Command References • 177 6.3.6.3.1 Structure of the Object ID The object ID is composed of a group ID and a target ID. The group ID identifies the functional group for which the status is to be queried. The target ID indicates the target for which the status is to be queried. Either all existing connections (0x0000) or individual connections (0x0001 to 0x0007) can be chosen.
PAGE 178
• Appendix Mailbox Command References Group Group ID Target- Description ID Time monitoring 0x0000 0x2000 and slave: 0x0001 master: 0x0001 to 0x0007 For connected WAGO devices: - MBX_STATE_ERROR_WATCHDOG - the time since the last packet is greater than 60 x (number of active wireless channels + 2 ms) - MBX_STATE_WARNING_WATCHDOG - the time since the last packet is greater than 20 x (number of active wireless channels + 2 ms) - MBX_STATE_OK - the time since the last packet is less than 20 x (number of
PAGE 179
Appendix Mailbox Command References • 179 6.3.6.4 Read Connection Quality (GetLinkQuality, 0xD5) Bit error rate Connection quality ("Link Quality" LQ) returns the bit error rate of the wireless connection.
PAGE 180
• Appendix Mailbox Command References Arguments Parameter Value Description MBX_TARGET_TABLE_ Bit 0…3 Table Index AND_INDEX Index 0...6 for WAGO devices of slots 1...7 Index 0...5 for external devices of slots 8...
PAGE 181
Appendix Mailbox Command References • 181 6.3.6.5 Read Signal Strength for a Connection (GetLinkSignalStrength, 0xD7) RSSI The RSSI value indicates possible overmodulation of the Bluetooth® recipient. It returns "0" if the strength of the received signal lies within the tolerance range. If the received signal is stronger than the upper limit of the tolerance range, a value > "0" is returned; if the received signal is weaker than the lower limit, a value < "0" is returned.
PAGE 182
• Appendix Mailbox Command References Arguments Parameter Value Description MBX_TARGET_TABLE_ Bit 0…3 Table Index AND_INDEX Index 0...6 for WAGO devices of slots 1...7 Index 0…5 for external devices of slots 8...12 Bit 4…7 Target table "2" for WAGO_DEVICE (slots 1...7) "1" for EXTERNAL_DEVICE (slots 8...
PAGE 183
Appendix Mailbox Command References • 183 6.3.6.6 Read Available Hopping Channels (GetAvailableChannelMap, 0xD8) Call up returns information on the status of the environment (i.e., the status of the wireless medium) for a connection channel. For Bluetooth®, the channels available for hopping are indicated. There are 79 channels with 1 MHz available. The channels are numbered serially from 0 through 78.
PAGE 184
• Appendix Mailbox Command References Response Byte 27 0 1 26 25 24 23 22 21 20 MBX_GETAVAILABLECHANNELMAP T MBX_RESULT 2 MBX_AFH_CHANNEL_MAP (LSB) 3 MBX_AFH_CHANNEL_MAP 4 MBX_AFH_CHANNEL_MAP 5 MBX_AFH_CHANNEL_MAP 6 MBX_AFH_CHANNEL_MAP 7 MBX_AFH_CHANNEL_MAP 8 MBX_AFH_CHANNEL_MAP 9 MBX_AFH_CHANNEL_MAP 10 MBX_AFH_CHANNEL_MAP 11 MBX_AFH_CHANNEL_MAP (MSB) Return values Parameter Value Description MBX_RESULT MBX_CMD_OUT_OF_RANGE Too large of an index was used.
PAGE 185
Appendix Mailbox Command References • 185 6.3.6.7 Set an LED (SetLED, 0xD9) Call up sets color and blink code of a defined LED. This can be used to test the functionality of the LED. Note To reinstate normal status information on the LEDs, the module must be restarted. This can be triggered by the corresponding mailbox command or by briefly switching off the power. Conditions Mailbox size Operating mode/profile Device role 6 12 18 Config.
PAGE 186
• Appendix Mailbox Command References Response Byte 27 26 25 0 1 24 23 22 21 20 MBX_SETLED T MBX_RESULT Return values Parameter Value Description MBX_RESULT MBX_CMD_OK No error occurred MBX_CMD_DENIED_NOT_ APPLICABLE Not available in real-time and adhoc profiles MBX_CMD_OUT_OF_RANGE An invalid LED number given. MBX_CMD_INVALID_ARG An invalid color or an invalid behavior indicated.
PAGE 187
Appendix Mailbox Command References • 187 6.3.6.8 Mirror Mailbox for Test Purposes (MirrorMailboxCommand, 0xDA) This command causes the module to immediately copy the full contents of the mailbox query to the contents of the response. The command can be executed to test the acyclic communication between the application and the local Bluetooth® module. Conditions Mailbox size Operating mode/profile Device role 6 12 18 Config. Realtime Ad hoc Master Slave ● ● ● ● ● ● ● ● Save config.
PAGE 188
• Appendix Mailbox Command References 6.3.6.9 Read the Operating Time of the Module (GetLocalUpTime, 0xDB) With call up, the operating time of the module since the last reboot can be read. Note This function serves as an aid for the error search; for example, to test power failures. The accuracy of the time measurement is not designed to enable precise time measurement over longer periods of time. Conditions Mailbox size Operating mode/profile Device role 6 12 18 Config.
PAGE 189
Appendix Mailbox Command References • 189 Return values Parameter Value Description MBX_MINUTES [0...59] Minute portion of the operating time MBX_HOURS [0...24] Hour portion of the operating time MBX_DAYS Mailbox size 6: [0…65.535] Number of days the module has Mailbox size > 6: [0…4.294.967.
PAGE 190
• Appendix Extended Register Structure (Configuration Block) 6.4 Extended Register Structure (Configuration Block) Offset (byte) Register no.
PAGE 191
Appendix Extended Register Structure (Configuration Block) • 191 Offset (byte) Register no. Length (bytes) Data Type Definition Description 36 9…12 16 Local device name See Appendix 6.3.5.1 and 6.3.5.2 52 13…14 8 Reserved 60 15…18 16 Password See Appendix 6.3.5.16 and 6.3.5.17 76 19 1 Inquiry time Maximum duration of a query The exact time results from: Inquiry Time * 1.28sec 1 Reserved 2 Reconnection time Time between two attempts to connection, LSB first (see Appendix 6.3.5.
PAGE 192
• Appendix Extended Register Structure (Configuration Block) Fields identified as reserved are set to 0 and ignored by the module. The extended register structure of each module is saved for the run time in a 512-byte block of 128 registers of 4 bytes each. For all opcodes, for which "Save Config." is marked in the requirements, all current settings are written in the non-volatile flash memory. The structure of the data in the flash memory is differentiated from the extended register structure.
PAGE 193
Appendix Example Configurations using WAGO-I/O-CHECK • 193 6.5 Example Configurations using WAGO-I/O-CHECK 6.5.1 Startup with the Bluetooth® Parameterization Dialog This Section can be used for the startup and configuration of Bluetooth® modules using the WAGO-I/O-CHECK software. The following startup example demonstrates how to start the module up with minimal configuration, and therefore does not describe the entire range of functions.
PAGE 194
• Appendix Example Configurations using WAGO-I/O-CHECK Figure 44: Hardware configuration g064461e 6.5.1.2 Starting up the Bluetooth® Modules 1. Determine which of your Bluetooth® modules will function as the master and which module will function as the slave. 2. Write down the MAC address of the slave: 0 0 : 0 6 : C 6 : _ _ : _ _ : _ _ Write down the MAC address of the master: 0 0 : 0 6 : C 6 : _ _ : _ _ : _ _ 6.5.1.2.1 Configuration of the Bluetooth® Slave using "Net Forming" 1.
PAGE 195
Appendix Example Configurations using WAGO-I/O-CHECK Figure 45: Identify your node configuration • 195 g064462e 3. Click with the right mouse button on the Bluetooth® module that you would like to configure as a slave. 4. In the module's context menu, choose Settings. This opens the Bluetooth®specific parameterization dialog of the module (see Figure 46).
PAGE 196
• Appendix Example Configurations using WAGO-I/O-CHECK Figure 46: Bluetooth®-specific parameter area g064418e Attention In order to perform the following steps, the Bluetooth® module must retain all factory settings (default settings); i.e, you have not yet attempted any configuration. If this is not the case, click on the [Default] button to reset the module's configuration. 5. Click on [Data Frame] in the toolbar. 6.
PAGE 197
Appendix Example Configurations using WAGO-I/O-CHECK • 197 8. Choose Net Forming in the navigation bar. 9. Choose the option All in the area Search for accessible devices and click on the [Search] button to search the network for Bluetooth® devices in the environment. To limit the search results to WAGO 750 Series devices, choose WAGO 750 instead. The MAC addresses of all located Bluetooth® devices are displayed in the list of devices within range (see Figure 48).
PAGE 198
• Appendix Example Configurations using WAGO-I/O-CHECK 13. Give the device a name (UserFriendlyName), e.g. "MyMaster". 14. Mark the MAC Address and choose the value "Yes" in the dropdown field Bind (see Figure 49). Figure 49: Bind device g064464e 15. Click on the [Write] button in the toolbar to write the altered configuration in the module. You have now allocated a master to the Bluetooth® slave (Slave ! Master). 16.
PAGE 199
Appendix Example Configurations using WAGO-I/O-CHECK • 199 6.5.1.2.2 Configuration of the Bluetooth® Master using "Net Forming" 1. Start WAGO-I/O-CHECK software (Version 3 or later). 2. Click on the [Identify] button. Your node configuration is graphically displayed. 3. Click with the right mouse button on the Bluetooth® module that you would like to configure as a slave. 4. Choose Settings in the context menu. This opens a new window for the configuration of the module.
PAGE 200
• Appendix Example Configurations using WAGO-I/O-CHECK vices are hidden for search request in communication operating mode; they may also be entered like other hidden devices or devices being out of reach: 10. Enter the listed MAC address of the slave, which is already set in the communication operating mode, manually in the allocated field. The following steps assume that you are using slot 1. 11. Give the device a name (UserFriendlyName), e.g., "Slave_01". This makes the overview easier for you. 12.
PAGE 201
Appendix Example Configurations using WAGO-I/O-CHECK • 201 6.5.1.2.3 Process Data Allocation Start with point 3 while the Bluetooth® parameterization dialog (siehe Figure 51) is still open. 1. Click with the right mouse button on the Bluetooth® module (master) 2. Choose Settings in the context menu. This opens a new window for module configuration. 3. In the navigation, choose the menu item PI-Mapping. The process data allocation is loaded from the module and graphically displayed in WAGO-I/O-CHECK. 4.
PAGE 202
• Appendix Example Configurations using WAGO-I/O-CHECK 6.5.1.3 Testing the Process Data Exchange The prerequisite for a successful test of the process data exchange is the correct configuration of the Bluetooth® device (see Appendix 6.5.1.2.1 through 6.5.1.2.3). The connection between the Bluetooth® master and slave is indicated by the constant green blinking of LED 2 (see Figure 3) of the Bluetooth® master. 1. Close the Bluetooth® parameterization dialog. 2.
PAGE 203
Appendix Example Configurations using WAGO-I/O-CHECK • 203 6.5.2 Startup using Mailbox Commands in the Process Data Dialog In addition to configuring modules in the Bluetooth® parameterization dialog, it is also possible to configure using mailbox commands. Mailbox commands are entered via function blocks in WAGO-I/O-PRO CAA or in the process data dialog of WAGO-I/O-CHECK. Here, WAGO-I/O-CHECK is used.
PAGE 204
• Appendix Example Configurations using WAGO-I/O-CHECK 6.5.2.2.1 Switch the Mailbox on 1. Switch the mailbox of all modules on by setting the control byte to 0x20 (bit 25=1) (see Table 36). Different error/warning bits can be set in the status byte depending on the delivery condition. The switched on mailbox is confirmed in byte 0 (status byte) with 0x60: 60hex = 0110.
PAGE 205
Appendix Example Configurations using WAGO-I/O-CHECK • 205 6.5.2.2.3 Determining the Master 1. Choose one of the modules to be the master and set byte 4 to 0x01 (MBX_DEVICE_ROLE). 2. Execute the mailbox command "SetLocalDeviceRole" (opcode 0x56) for this module to assign it the role of master. 3. Wait five seconds after the execution so that the internal Bluetooth® subsystem can change over. The remaining four Bluetooth® modules are already configured as slaves by the factory setting.
PAGE 206
• Appendix Example Configurations using WAGO-I/O-CHECK Moving forward, the return values (MAC addresses) of the master will be revealed to the slaves and the return values of the slaves will be revealed to the master. 6.5.2.2.5 Loading the MAC Addresses of the Slaves into the Device List of the Master 1. In bytes 5 through 10 of the master, write the MAC address of the first Bluetooth® slave (see Table 42). 2.
PAGE 207
Appendix Example Configurations using WAGO-I/O-CHECK • 207 Table 44: Mailbox command "AllowRemoteDevice" Byte 10 9 8 7 6 5 4 Toggle Opcode empty C/S PD/O 0x00 0x06 0xC6 0x__ 0x__ 0x__ 0x22 0x00 0x83 0x00 0x20 PD/I 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x83 0x00 0x60 10. In bytes 5 through 10 of the master, write the MAC address of the fourth Bluetooth® slave (see Table 45). 11.
PAGE 208
• Appendix Example Configurations using WAGO-I/O-CHECK 6.5.2.2.6 Loading the MAC Address of the Master into the Device Lists of the Slaves 1. Enter the MAC address of the master in bytes 5 through 10 of the first slave. 2. For each slave, set byte 4 to 0x20 (TABLE_ENTRY). 3. Use the mailbox command "AllowRemoteDevice" (opcode 0x83) to load the master in the device list of the slave (see Table 46). 4. Proceed in the same manner with the remaining slaves.
PAGE 209
Appendix Example Configurations using WAGO-I/O-CHECK • 209 Table 48: Mailbox command "BindRemoteDevice" for binding Slave 2 Byte 10 9 8 7 6 5 4 Toggle Opcode empty C/S PD/O 0x00 0x06 0xC6 0x___ 0x___ 0x___ 0x21 0x80 0x85 0x00 0x20 PD/I 0x00 0x06 0xC6 0x___ 0x___ 0x___ 0x00 0x80 0x85 0x00 0x60 7. Write the MAC address of the third Bluetooth® slave in bytes 5 through 10 of the master (see Table 49). 8.
PAGE 210
• Appendix Example Configurations using WAGO-I/O-CHECK 6.5.2.2.9 Setting the Communication Mode for Master and Slaves 1. Set all Bluetooth® slaves with the mailbox command "SetLocalOperationMode" (opcode 0x4A) to communication mode (0x03 for the ad hoc profile) (see Table 52). 2. Follow the same steps for the Bluetooth® master. 3. Wait 5 seconds after the execution.
PAGE 211
Glossary • 211 Glossary A Acyclic Acyclic processes are triggered as needed and are used, for example, to react to user input or special events. Ad hoc profile The ad hoc profile is one of two profiles in the communication mode supported by the Bluetooth® module. Special feature: In the ad hoc profile, the module can also communicate with Bluetooth® devices from other manufacturers.
PAGE 212
• Glossary B Baseband A baseband is referred to if the desired signal is transmitted in an unaltered frequency range. In wireless communication systems, wireless transmission does not usually take place in the baseband, but rather by modulation of a significantly higher frequency carrier signal with the baseband signal. Binding Bluetooth®-specific process in which a connection between two devices is activated for data exchange. Bit A bit is the smallest information unit.
PAGE 213
Glossary • 213 Bootloader The bootloader is software in the first block of the bootable system. It is loaded and executed by the firmware and, in turn, starts other parts of the operating system. The version status of the bootloader can be separately queried. Broadcast In broadcast mode, this is a report transmitted to all stations connected to the network. Bus cycle Single instance or advice of updating of cyclical process data within an SPS bus node.
PAGE 214
• Glossary Command Instructions for the execution of certain actions. Communication mode Communication mode is an operation mode of the WAGO Bluetooth® module in which cyclical data exchange with connected Bluetooth® devices occurs. Complex bus modules Complex bus modules are a group of I/O modules that significantly exceed the functional and application range of the input and output modules described in the IEC-61131.
PAGE 215
Glossary • 215 Cutoff Generally: limitation to a specific size of the portion of cyclical process data allocated to a device. Bluetooth® context: A Bluetooth® master only deals with excerpts of the process images for connected Bluetooth® slaves. The size of these "excerpts" is set by a "cutoff" in the configuration mode. The current data to be read and written, which is assigned to slots in the master's process image, remains.
PAGE 216
• Glossary Device within range Devices are within physical range and are ready for connection or operation. Diagnostics Diagnostic information provides information on the system status, particularly on disturbances or error conditions. Cyclic diagnostic information is provided by the LED displays and the content of the status bytes. Acyclic diagnostic information can be queried using the mailbox interface.
PAGE 217
Glossary • 217 F FHSS Generally: The frequency hopping process known as "Frequency Hopping Spread Spectrum" (FHSS) involves the division of a frequency range into sub-ranges, between which the data transmission then alternates. This improves co-existence with other networks and provides additional tapping protection and strength against narrow band disturbing influences. Bluetooth® context: subdivision of the wireless channel into 79 subchannels.
PAGE 218
• Glossary H HCI The "Host Controller Interface" (HCI) is an interface in the Bluetooth® protocol suite through which higher layers can directly act on the baseband protocol. Header Information prepended to the user data portion of a data packet that is used, for example, to administer a network or initialize a device. Hexadecimal In a hexadecimal numbering system, the numbers are represented in a base 16 place value system.
PAGE 219
Glossary • 219 L L2CAP The "Logical Link Control and Adaptation Layer Protocol" (L2CAP) is part of the Bluetooth® protocol suite. Latency The latency of the data transmission indicates how long after transmission a data packet to a local interface that same data packet is available to a remote interface. Library Collection of Modules available to the programmer in the WAGO-I/O-PRO CAA programming tool for creating control programs in accordance with IEC61131-3.
PAGE 220
• Glossary Mailbox interface The mailbox interface is an interface for executing acyclic services using the process image (PI). Master In a device network, the master performs administrative tasks. The master of a Bluetooth® network organizes the network and the connections to the slaves. See also "Coordinator" Mini-WSB A Mini-WSB is a quick marking system for WAGO modules. Mirroring For this module: Received data is returned without change, permitting a simple function test of the interface.
PAGE 221
Glossary • 221 Opcode For this module: "Opcode" is the abbreviated form of "operation code". The opcode is part of a mailbox command (1 byte in length). The complete command is formed by the opcode along with its arguments. P Packet For this module: A data/wireless packet consists of user data and header data that are transmitted together. PAN The PAN (Personal Area Network) is a specific Bluetooth® profile. A PAN of Bluetooth® devices is called a piconet.
PAGE 222
• Glossary PI The process image (PI) is an area of the memory in which the process data for and from modules/couplers/controllers is stored. The allocation and meaning of the process data are module-/fieldbus-specific. Piconet A Bluetooth® network consisting of a master and up to seven slaves is called a piconet. Communication may run directly and bi-directionally between master and slaves; however, communication between slaves is only possible indirectly through the master.
PAGE 223
Glossary • 223 Process data size Size in bytes of the available process image Process image mapping Subdivision of a process image into independent parts and allocation of these parts to specific slots for data transmission. Q Quality-of-Service (QoS) Quality of a communication service from the view of the user. The user can define his or her requirements regarding the communication service through the QoS.
PAGE 224
• Glossary Register communication Via register communication, an acyclic interface to the parameterization and configuration data of an I/O module with 1 byte of protocol information and 2 bytes of data (64 addressable data sets) is configured. In register communication, process data is not exchanged and the mailbox is masked. Remote See "Remote device" Remote device A device that is not connected through a local interface (such as the fieldbus); rather, the connection is wireless only.
PAGE 225
Glossary • 225 Signal strength The signal strength is an indicator of reception quality. The higher the signal strength, the better the reception. Slave A slave (also end device) does not accept any administrative tasks in a device network. Opposite: Master (also Coordinator). Slot For this module: A slot represents a part of the process image (PI) that is reserved for data exchange with a specific remote device. SMA SMA (Sub-Miniature-A) indicates a special design for coaxial connectors.
PAGE 226
• Glossary T TCP/IP TCP is a connection-oriented network protocol for the transport layer (Layer 4) of the ISO/OSI model provided with relatively secure transmission mechanisms. Toggling For this module: "Toggling" is the tilting/inverting of a bit/status. In the Bluetooth® module, inverting the toggle bit (bit 7 of the toggle byte in the PIO) triggers the processing of the mailbox command.
PAGE 227
Glossary • 227 Watchdog A watchdog is a system component that monitors certain functions of a system at certain time intervals. If an error or a deviation in relation to previously defined limits is recognized, appropriate measures for solving the problem are introduced. The main application is monitoring of system failures recognized by the watchdog when the system no longer reacts to regular queries by the watchdog. WLAN WLAN (Wireless Local Area Network) refers to a local wireless network.
PAGE 228
WAGO Kontakttechnik GmbH & Co. KG Postfach 2880 • D-32385 Minden Hansastraße 27 • D-32423 Minden Telefon: 05 71/8 87 – 0 Telefax: 05 71/8 87 – 1 69 E-Mail: info@wago.com Internet: http://www.wago.