Scanlab RTC6 PCIe Board - Page 919

RTC6 boards
Doc. Rev. 1.0.21 en-US
16 Appendix A: The RTC6 Ethernet Board
919
innovators for industry
16.9.5 Disabling
Remote Interface Mode
Permanently
The RTC6 Ethernet Board is reset to
“Standalone Full State“ when the
Remote Interface Mode is permanently disabled.
In this state, the RTC6 Ethernet Board can be
controlled via the conventional RTC6 DLL-based
(1)
connection.
(1) Disable Remote Interface Mode temporarily as
described in Chapter 16.9.4 ”Disabling
Remote Interface Mode Temporarily”, page 918.
(2) Do one of the following:
– Call eth_set_remote_tgm_format( 0 ) in
Boot Phase 1 (or remove
eth_set_remote_tgm_format( 1 ) from
Boot Phase 1)
– Set up “Standalone Basic State“, see
Chapter 16.7.2 ”Preparing the
“Standalone Basic State“”, page 909
( store_program ( 0 ))
– Switch off the Standalone Operation Mode at
all, see Chapter 16.7
”Standalone Functionality”, page 908
( store_program ( 1 ) or set_eth_boot_control ( 0 )
16.9.6 Error Codes for
get_error/get_last_error
Occurring in
Remote Interface Mode Only
Bit #31 (invalid Command Telegram) is set in
Remote Interface Mode only.
The Error code can be queried by wrapper function
get_remote_error:
Error code Description
0 No error.
1 Invalid size of Command Telegram.
Must be: > TGM_HEADER
(a)
or
 TGM_MAX_SIZE
(a)
.
(a) See telegrams.h .
2 version
(a)
value in Command Telegram
is not compatible with BIOS.
Make sure that C++ Remote Interface
Wrapper and BIOS are from the same
RTC6 Software Package.
3 Invalid length
(a)
value.
The received telegram size does not
match the size specified in telegram
header.
4 Invalid type
(a)
value.
Must be: 0 with a Command Telegram.
5 Invalid format
(a)
value.
Must be: Same value as previously set
by eth_set_remote_tgm_format.
6 Invalid Remote Command-ID.
Must be: Valid Remote Command-ID
from enum REMOTE_ID
(a)
.
7 Invalid payload.
Must be: 1 Remote Control Command
oder 1…n Remote List Command(s).