Code: |
AS + 507 |
Symbolic: |
bccSysInfo |
This command will query system information from the connected device. Request has no parameters.
On success, a bccAck will received with following data:
Offset |
Type |
Label |
Description |
|---|---|---|---|
0 |
U32 |
MANUFACTURER |
Manufacturer identification: 0=Generic 1=Robox standard 2=Robox custom 3=Motorola 4=Parker |
4 |
U32 |
MODEL |
Model identification, depending of manufacturer. Always valid: 0 = Generic 1 = Virtual or hardware emulator
16 =DSP56803 (obsolete, with vendor=3) 16 = Robox RBXM 17 = Robox RBXE or RBXC 18 = Robox RPM 19 = Robox uRbx 20 = Robox CANSIN 21 = Robox RBXM G2 22 = Robox CPU PPC Hi-Drive 23 = Robox NIOS (ethercat) 24 = Robox uRMC 25 = Robox IMD20 26 = Robox CANSIN RTE 27 = Robox RMC G2 28 = Robox RBXM P2020 29 = Robox µRMC2 30 = Robox µRMC3 31 = Robox IMD30 32 = Robox µRIO 33 = Parker generic device 34 = Robox EthIP/PNET board 35 = Robox RP-1 36 = Robox RP-2 37 = Robox ECATSIN 38 = Robox EC2A 39 = Robox RP-0 40 = Robox Safety Board 41 = Robox ECATSIN RTE 42 = Robox Dongle 43 = Robox Integrated Drive RID20-E 44 = Robox RP-2 (Bus Slave) 45 = Robox RHAM |
8 |
U32 |
OSTYPE |
Operating system identification: 0=Generic 1=OSF 16bit 2=OSF 16bit with integrated language 3=OSF 32bit 4=OSF 32bit with integrated language 5=Embedded OS for DSP56 6=Embedded OS for CANSIN 7=Eprom (OSE) 8=Embedded OS for NIOS (ethercat) 9=Embedded OS for IMD 10=Embedded OS for Parker generic 11=Ethernet IP interface for EthIP/PNET board 12=ProfiNET interface for EthIP/PNET board 13=Embedded OS for EC2x |
12 |
U32 |
OSVERSION |
Operating system version (nvMake format) |
16 |
U32 |
FIRMWTYPE |
Firmware type identification: 0=Generic 1=RRT 16bit 2=RTT 16bit integrated in OS 3=RHLL 16bit 4=RHLL 16bit integrated in OS 5=RHLL 32bit integrated in OS 6=Device specific firmware (integrated in OS) 7=RRT 32bit integrated in OS 8=RTE 32bit integrated in OS |
20 |
U32 |
FIRMWVERSION |
Firmware version (nvMake format) |
24 |
B[32] |
USERTEXT |
User software description |
56 |
U32 |
USERVERSION |
User software version (nvMake format) |
60 |
U32 |
ATTRIB |
Device attributes: 0x00000001 Remote variable set available 0x00000002 Intel 32bit HW variable available 0x00000004 BCC protocol translation active (#1) |
64 |
U8 |
TBTYPE |
Taskbin type identification: 0=None 1=Classic taskbin 2=Taskbin++ 16bit version 3=Taskbin++ 32bit version |
65 |
U32 |
TBVERSION |
Taskbin version (nvMake format) |
69 |
U32 |
VARSETID |
Variable current set unique ID |
73 |
U32 |
SLIBTYPE |
System library type: 0=Generic 1=RBXLIB (Robox customized GCC library) |
77 |
U32 |
SLIBVERSION |
System library version (nvMake format) |
81 |
U8 |
BIOSTYPE |
BIOS type identification: 0=None 1=Robox BIOS |
82 |
U32 |
BIOSVERSION |
BIOS version (nvMake format) |
86 |
U32 |
FIRMWEXT |
Firmware extensions: 0x00000001 Robox Path Executor (RPE) 0x00000002 Robox XPL Executor (XPL) |
90 |
U32 |
RPEVERSION |
RPE version (nvMake format) |
94 |
U16 |
LANGUAGE |
System language: 0x0000=Neutral (or not set) 0x0004=Cinese semplificato (ZH) 0x0007=Tedesco (DE) 0x0009=Inglese (UK/US) 0x000a=Spagnolo (ES) 0x000c=Francese (FR) 0x0010=Italiano (IT) 0x0012=Coreano (KO) 0x0016=Portoghese (PO) 0x0019=Russo (RU) |
96 |
U32 |
XPLVERSION |
XPL version (nvMake format) |
100 |
U32 |
XPLLANGS |
XPL languages supported 0x00000001 RPL 0x00000002 GCODE RS274 |
104 |
U16 |
IB_TX |
Inter-block transmit capacity |
106 |
U16 |
IB_RX |
Inter-block receive capacity |
108 |
U8 |
OSETYPE |
OSE type identification: 0=None 1=Robox OSE |
109 |
U32 |
OSEVERSION |
OSE version (nvMake format) |
Notes:
•To validate the structure you must have at least a data area of 69 bytes (aka the base version of the bccSysInfo command): extra missing data must be considered as 0 filled.
•This command is (and must be) always authorized.
•The attribute #1 means that someone (the device hardware or the software) is translating BCC protocol from / to another protocol; this should be considered as a warning that not all documented BCC command could be available and communication timings can be different than the native BCC protocol timings.
•If IB_TX (or IB_RX) field has value of 0 it will be assumed as default value: the default value is 4 (for backward compatibility reasons).
On failure, a bccNack is received.
