11.01.2014 Views

netGateway DTM for netTAP, netBRICK and netLINK - Hilscher

netGateway DTM for netTAP, netBRICK and netLINK - Hilscher

netGateway DTM for netTAP, netBRICK and netLINK - Hilscher

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Configuration Sequence <strong>for</strong> Gateway <strong>and</strong> Proxy 28/256<br />

6. Signal Mapping: Transfer status info of Port X3 to Port X2<br />

‣ If necessary, map the status in<strong>for</strong>mation of Port X3 (Port X3 generated,<br />

which are generated device internal) to signals which should be sent on<br />

Port X2 (Port X2 send)<br />

‣ For this mark the status signal (Port X3) <strong>and</strong> the signal which should be<br />

sent (Port X2) <strong>and</strong> click the button Map Signals<br />

Or<br />

Map the signal using drag <strong>and</strong> drop. For this, drag the status signal<br />

(Port X3 generated) <strong>and</strong> drop it on the signal to be sent (Port X2 send)<br />

An example of the Signal Mapping window shows the following figure<br />

Figure 13: Gateway Signals mapped<br />

<strong>netGateway</strong> <strong>DTM</strong> <strong>for</strong> <strong>netTAP</strong>, <strong>netBRICK</strong> <strong>and</strong> <strong>netLINK</strong> | Configuration of Gateway <strong>and</strong> Proxy Devices<br />

DOC081201OI04EN | Revision 4 | English | 2011-03 | Released | Public © <strong>Hilscher</strong>, 2009-2011

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!