
150/176 Web interface
Bosch Rexroth AG
, MIT: ID 40, 3 842 530 344/2014-05
10.7.3.2 Examples of read commands
Read actual link state
This read command returns the byte with the link state coding. The coding is
described in Chapter 5.3.1 “Actual link state”.
http://id40/xid/bal-mem?adrset=0x30000
XML output
, whereby the link state value read here = 4:
<?xml version=”1.0” encoding=”ISO-8859-1” ?>
<?xml-stylesheet href=”/id40xml.css” type=”text/css”?>
<xid><bal-mem><bal-range><offset>0x30000</offset><data>
<b>0x04</b></data></bal-range>
</bal-mem></xid>
Read bytes from MDT and SLK register
First address range 0 – 99:
100 bytes of MDT data
Second address range 0x1200 –4700:
93 bytes of MDT data
Third address 0x00030000:
1 byte for link state
Hexadecimal output formats for address and data:
http://id40/xid/bal-mem?adrset=0.99+0x1200.4700+0x30000&fmt-
offset=hex&fmt-data=hex
Reading the Profibus node number
The Profibus node number is read using a special system command.
The URL
http://id40-slk/xid/univar/pdp
returns the following XML string:
<?xml version=”1.0” encoding=”ISO-8859-1” ?>
<?xml-stylesheet href=”/id40xml.css” type=”text/css”?>
<xid><pdp><node-id><var><desc>pdp.node-id
</desc><value>100</value></var></node-id>
</pdp>
</xid>
The node number is in the range
<value ... </value>
, in this example = 100
10.7.3.3 Web interface prefetch
With the URL parameter
&prefetch=1
, the SLK address ranges specified in
adrset
are read from the current MDT and also automatically copied from each subsequent
MDT to the SLK, however they are
not
transmitted from the web interface by event.
The MDT data buffered in the SLK can then be retrieved using the same read
command once the MDT has left the HF link.
Attention:
The next MDT overwrites the buffered data, so the read access has to
occur beforehand.
The prefetch function is described in Chapter 6.4.1. The web interface prefetch is
similar to the buffered prefetch in Chapter 6.4.2.1 “Single transmit”.
PROOF COPy 1 | 20.05.2014 | FOR INTERNAL USE ONLy