Scanlab RTC6 PCIe Board - Page 917

RTC6 boards
Doc. Rev. 1.0.21 en-US
16 Appendix A: The RTC6 Ethernet Board
917
innovators for industry
16.9 Remote Interface Mode
Remote Interface Mode serves to control
RTC6 Ethernet Boards without RTC6 DLL
(1)
.
For this purpose Command Telegrams are sent via the
network (UDP) to the RTC6 Ethernet Board. A C++
Remote Interface Wrapper that simplifies usage is
included in RTC6 Software Package.
In this Chapter:
• Prerequisites for Remote Interface Mode,
page 917
• Restrictions in Remote Interface Mode, page 917
• Enabling Remote Interface Mode, page 918
• Disabling Remote Interface Mode Temporarily,
page 918
• Disabling Remote Interface Mode Permanently,
page 919
• Error Codes for get_error/get_last_error
Occurring in Remote Interface Mode Only,
page 919
• About C++ Remote Interface Wrapper, page 920
16.9.1 Prerequisites for
Remote Interface Mode
• RTC6 Software Package  V1.16.0
• The RTC6 Ethernet Board is equipped with
 BIOS-ETH 38, see also Chapter 16.7.1
”Upgrading BIOS-ETH”, page 909.
• The RTC6 Ethernet Board is configured for
Standalone Operation Mode in
“Standalone Full State“, see Chapter 16.7
”Standalone Functionality”, page 908.
• In Boot Phase 1, eth_set_remote_tgm_format is
called.
16.9.2 Restrictions in
Remote Interface Mode
• A conventional RTC6 DLL-based connection to
the RTC6 Ethernet Board cannot be established.
Therefore, RTC6 Commands that require a
connection can not be called.
• RTC6 Ethernet Board can only still be searched
for:
– Via RTC6 DLL by eth_search_cards
• Most RTC6 Commands are available in a
corresponding functionality as
Remote Commands, see in rtc6_rif_wrapper.h .
(1) Or, without Linux Shared Library, see Subfolder Linux,
page 33.