CiA 150 DS V1.1 CAN power management layer specification(TC_150_205v01010002)

LC1F150i s c l a ime r : T h i s d o c u m e n t a t i o n i s n o t i n t e n d e d a s a s u b s t i t u t ef o r a n d i s n o t t o b e u s e d f o r d e t e r m i n i ng s u i t a b i l i t y o r r e l i a b i l i t y o f th e s e p r o d u c t s f o r s p e ci f i c u s e r a p p l i c a t i o n sProduct data sheetCharacteristicsLC1F150TeSys F contactor - 3P(3 NO) - AC-3 - <= 440 V 150 A - without coilMainRange TeSys Product nameTeSys F Product or component type Contactor Device short name LC1F Contactor application Motor control Resistive load Utilisation categoryAC-4AC-1AC-3Poles description 3P Pole contact composition 3 NO[Ue] rated operational voltage <= 1000 V AC 50/60 Hz <= 460 V DC[Ie] rated operational current 250 A (<= 40 °C) at <= 440 V AC AC-1150 A (<= 55 °C) at <= 440 V AC AC-3Motor power kW65 kW at 1000 V AC 50/60 Hz AC-375 kW at 380...400 V AC 50/60 Hz AC-390 kW at 500 V AC 50/60 Hz AC-3100 kW at 660...690 V AC 50/60 Hz AC-322 kW at 400 V AC 50/60 Hz AC-480 kW at 415 V AC 50/60 Hz AC-380 kW at 440 V AC 50/60 Hz AC-340 kW at 220...240 V AC 50/60 Hz AC-3Complementary[Uimp] rated impulse withstand voltage 8 kV Overvoltage categoryIII[Ith] conventional free air thermal current250 A at <= 40 °CIrms rated making capacity 1500 A AC conforming to IEC 60947-4-1Rated breaking capacity1200 A conforming to IEC 60947-4-1[Icw] rated short-time withstand current1200 A <= 40 °C 10 s700 A <= 40 °C 30 s600 A <= 40 °C 1 min450 A <= 40 °C 3 min350 A <= 40 °C 10 minAssociated fuse rating160 A aM at <= 440 V250 A gG at <= 440 VAverage impedance0.35 mOhm at 50 Hz - Ith 250 A[Ui] rated insulation voltage1000 V conforming to IEC 60947-4-11500 V conforming to VDE 0110 group CPower dissipation per pole22 W AC-18 W AC-3Mounting support PlateStandards JIS C8201-4-1IEC 60947-4-1EN 60947-4-1EN 60947-1IEC 60947-1Product certifications LROS (Lloyds register of shipping)CSAULDNVABSBVRMRoSRINACBConnections - terminals Power circuit : connector 1 cable(s) 120 mm²Power circuit : lugs-ring terminals 1 cable(s) 120 mm²Power circuit : bolted connectionPower circuit : bar 2 x (25 x 3 mm)Tightening torque Power circuit : 18 N.mEnvironmentIP degree of protection IP2x front face with shrouds (ordered separately) conforming to IEC 60529IP2x front face with shrouds (ordered separately) conforming to VDE 0106 Protective treatment THAmbient air temperature for operation-5...55 °CAmbient air temperature for storage-60...80 °C-40...70 °CPermissible ambient air temperaturearound the deviceOperating altitude3000 m without derating in temperatureMechanical robustness Vibrations contactor closed 6 Gn, 5...300 HzShocks contactor open 9 Gn for 11 msVibrations contactor open 2 Gn, 5...300 HzShocks contactor closed 15 Gn for 11 msHeight170 mmWidth163.5 mmDepth171 mmProduct weight 3.83 kgOffer SustainabilitySustainable offer status Green Premium productRoHS (date code: YYWW)Compliant - since 0843 - Schneider Electric declaration of conformitySchneider Electric declaration of conformityREACh Reference not containing SVHC above the thresholdReference not containing SVHC above the thresholdProduct environmental profile AvailableProduct environmentalProduct end of life instructions AvailableEnd of life manual Contractual warrantyWarranty period18 monthsLC1F150。

Content1CANopen 2 1.1EDS Files 2 1.2Support 2 1.3Features 2 1.3.1Basic information 2 1.3.2Basics based on CiA DS-301, V4.2.0 2 1.3.3Basics based on CiA DSP-406, V3.2 3 1.3.4Basics SDO communication 3 1.3.5Basics PDO communication based on CiA 301, V4.2.0 3 1.4Object Library 4 1.4.1Communication Profile Area based on DS 301 V4.2.0 4 1.4.2Device Profile Area 6 1.4.3Manufacturer specific Area 8 1.5Explanations to Object Library 9 1.5.1Object 0x6300 Encoder Cams 9 1.5.2Cam state registers 9 1.5.3Object 0x6400 Work Area 9 1.5.3.1Work Area Supervision 9 1.5.3.2Work Area State 9 1.6LSS / Layer Setting Service 9 1.6.1Configuration of Node-ID 10 1.6.2Configuration of Bit Rate 10 1.6.3Store Configuration Data 11 1.7SDO Services 11 1.7.1SDO Download 11 1.7.2SDO Upload 12 1.7.3SDO Abort 12 1.8Process Data PDO 12 1.8.1PDO Default Setting 12 1.8.2PDO Parameter Setting 12 1.9Error Handling 14 1.9.1Emergency Messages 14 1.10Error Objects 15 1.10.1Manufacturer-specific Status 15 1.11Non-Volatile Storage and Data Restoration 16 1.12Abbreviations 17 1.13Document Changes 171 CANopenThis document reflects the Novotechnik sensor protocol implementation of the standard CANopen protocol.A basic knowledge of the CAN Bus is required for a proper understanding of this document.Most of the definitions made are according to the following CiA Standard specifications.For making use of all the features that these specifications offer, a knowledge about them is absolutely necessary. The sensor supports the CANopen Communication profile DS-301, V4.2.0, Encoder profile DSP-406, V3.2 and Layer Setting Services (LSS) DSP-305, V1.1.2.1.1 EDS FilesFor integration in a common CANopen projecting tool, electronic data sheet (*.eds) files are provided.These files can be downloaded from the Novotechnik Web Site, see Downloads/Operating manualswhere also this document can be found.Electric data sheet see file Product series_CANopen.1.2 SupportIfyouhaveanyquestions,******************************************************.Electronic data sheets or user manuals for previous software versions are available on request.1.3 Features1.3.1 Basic informationVendor ID: 386 = 0x0182 (Novotechnik)Product code: TP1: 04035 = 0x0FC3, TH1: 04042 = 0x0FCA, TM1: 04228 = 0x1084, TF1: 04052 = 0x0FD4 Rev.-No.: f.e 196613 = 0x30005Serial No.: see product label, “YYMMxxxx”1.3.2 Basics based on CiA DS-301, V4.2.01.3.3 Basics based on CiA DSP-406, V3.21.3.4 Basics SDO communication1.3.5 Basics PDO communication based on CiA 301, V4.2.01.4 Object Library1.4.1 Communication Profile Area based on DS 301 V4.2.01) for 1 position marker2) for 2 position markers1.4.2 Device Profile Area* for 1 position marker: default value 0x01** for 1 position marker and product series TM1 / TF1: not available 1.4.3 Manufacturer specific Area1.5 Explanations to Object Library1.5.1 Object 0x6300 Encoder CamsEncoder cams are used to indicate if a position falls below or exceeds a defined value.1.5.2 Cam state registersCam active: the current position value is between the higher and lower cam-limitCam inactive: the current position value is not between the higher and lower cam-limit.The values for low limit (0x631x) and high limit (0x632x) regard the values for preset (0x6010) and measuring steps (0x6005). The value of hysteresis (0x633x) is added in direction of motion.Note: the cam high limit value can have a lower value than the cam low limitA change in cam state causes an EMCY message.The cam state objects (0x6300) are able to be mapped to the TPDOs.1.5.3 Object 0x6400 Work AreaIt is possible for encoders to define a so-called user defined working area.The main purpose for a work area is to get a high-priority information (via EMCY message) when the transducer’s p o-sition leaves its predefined working area.The actual work area information with work area low limit and work area high limit may be stored in object 0x6401 and 0x6402. This way, the area state object (0x6400) may also be used as software limit switches.1.5.3.1 Work Area SupervisionEach work area channel is fixedly linked to a position channel:1.5.3.2 Work Area StateThe values for low limit (0x6401) and high limit (0x6402) regard the values for preset (0x6010) and scaling (0x6501, 0x6502).A change in work area state causes an EMCY message.The work area state objects (0x6400) are able to be mapped to the TPDOs.1.6 LSS / Layer Setting ServiceTo configure the encoder via the LSS(according CiA DS 305) the encoder is handled as a slave, thePLC must have a LSS master functionality.A LSS-message is composed as follows:This applies to the COB-ID:• LSS-Master ⇒ LSS-Slave: 2021 (0x7E5)• LSS-Slave ⇒ LSS-Master: 2020 (0x7E4)LSS can only be used when the encoder is in the stopped status or pre-operational status.The NMT command for setting the encoder in stopped status is:To program via LSS the sensor has to be switched to LSS configuration state.There are two possible ways to do so:• Switch Mode Selective:only the addressed CANopen device is switched to the LSS configuration stateLSS requires data content in the following objects:Example:Vendor-ID (see index 1018/1) 0x0182 LSS-Command 0x40 Product code (see index 1018/2) 0x0BE0 LSS-Command 0x41 Rev.No. (see index 1018/3) 0x10003 LSS-Command 0x42 Serial-No. (see index 1018/4) 0x12345678 LSS-Command 0x43 After receiving the identification objects, the encoder answers with LSS-Command 0x44.• Switch Mode Global: all CANopen devices supporting LSS are switched to the LSS configuration stateWhen the CAN devices are in configuration state the Node-ID and/or the bit rate can be changed. 1.6.1 Configuration of Node-IDThe Node-ID can be programmed with the LSS-Command 0x11N ID: new Node-ID in the range of 1 (127)Err Code: 0: protocol successfully completed / 1: Node-ID out of rangeChange of Node-ID will cause:•Automatic alteration of COB-ID’s for SDO1, EMCY and Heartbeat and TPDOs.•Non-volatile Node-ID storage through …Store Configuration“ in the LSS mode configur ation.1.6.2 Configuration of Bit RateThe Bit Rate can be programmed with LSS-Command 0x13Table Index: 0x07: 20 kBaud0x06: 50 kBaud0x04: 125 kBaud0x03: 250 kBaud0x02: 500 kBaud0x01: 800 kBaud0x00: 1000 kBaudErr Code: 0: protocol successfully completed 1: Bit timing not supportedChange of Bit rate will cause:•The bit rate gets active•Non-volatile CAN bit rate storage through …Store Configuration“ in the LSS mode configuration1.6.3 Store Configuration DataThe LSS configuration data (Node-ID and Bit Rate) are stored to the non-volatile memory of the sen-sor using LSS-Command 0x17Err Code: 0: protocol successfully completed 2: storage media access error1.7 SDO ServicesService Data Objects SDO (according to CiA DS 301) manage the parameter data exchange, e.g. thenon-cyclical execution of the preset function.Parameters of device object library (object index/subindex see chapter 1.4 Object Library) can beread, written or stored by means of SDO.1.7.1 SDO DownloadThe SDO download service is used to configure the parameters.Command 0x2_: 0x22 write command, parameter to encoder0x23 write command, 4 Byte parameter to encoder0x27 write command, 3 Byte parameter to encoder0x2B write command, 2 Byte parameter to encoder0x2F write command, 1 Byte parameter to encoderCommand 0x60: confirmation: parameter receivedNODE-IDUsing writing to object 0x2000, non-volatile storage has to be done by w riting the“save”- signature (0x65766173) on object 0x1010/1 (TP1/TH1) or 0x1010/4 (TF1). These changes will become effective after a communication restart or a power up.Changing the Node-ID will affect all COB-IDs according to the “predefined co nnection s et”.Example: COB-ID TPDO1 = 0x180 + (Node-ID)BIT-RATEUsing writing to object 0x2001; non-volatile storage has to be done by writing the“save”- signature (0x65766173) on ob-ject 0x1010/1 (TP1/TH1) or 0x1010/4 (TF1). These changes will become effective after a communication restart or a power up.1.7.2 SDO UploadThe SDO upload service is used to read the parameters.Command 0x40: read command, parameters from encoderCommand 0x4_: 0x42 read command, parameter to encoder0x43 read command, 4 Byte parameter to encoder0x47 read command, 3 Byte parameter to encoder0x4B read command, 2 Byte parameter to encoder0x4F read command, 1 Byte parameter to encoder1.7.3 SDO AbortIf the SDO download or SDO upload service fails for any reason, the sensor responds with a SDO abort protocol. Abort Code: 0x06090011 subindex does not exist0x06090030 value exceeded0x06020000 object does not exist0x06010001 object is write only0x06010002 object is read only0x06060000 access error0x08000020 data transport error0x08000000 general error0x08000022 wrong state1.8 Process Data PDOProcess Data Objects (according CiA DS 301)manage the process data exchange, f.e the cyclical transmission of the position value. The process data exchange with the CANopen PDOs is a very slim process without protocol overhead.1.8.1 PDO Default Setting2 Transmit PDOs (TPDO) with each max. 8 bytes are provided:0x1800 TPDO1: default: Event-driven with event timer switched off (changeable to synchronous)0x1801 TPDO2: default: synchronous1.8.2 PDO Parameter SettingThe contents of the encoder-specific TPDOs can be configured by variable mapping according to cus-tomer´s requirements. This mapping has to be performed for the encoder as well as for the receiver.The PDO is limited to a maximum size of 8 bytes and 5 mappings per each PDO.Step 1: For changing of mapping, the sensor must be in properational mode and the MSB of PDOCOB-ID has to be set to 1 to deactivate it.Step 2: Clearing entries in mapping table of PDO1 (PDO2) => subindex 0x0 of object 1A00 (1A01)has to be set to 0x00.Step 3: Mapping of objects into PDOExample:A PDO shall be mapped in a way that the "current position", the "current speed" and the "current chiptemperature" are transmitted in one PDO .Mapping #1 “current position”:Mapping #2 “current speed”:Mapping #3: “current chip temperature”.Step 4: Setting entries in mapping table => subindex 0x0 of object 1A00 has to be set to the numbers of mapping en-tries (e.g. 0x03)Step 5: For re-activating the PDO, the MSB of PDO COB-ID has to be set to 0.Note:TPDO1 value for Event Timer must always be higher than the value for Inhibit Time (except for value 0).Failed sending of TPDOs can occur if:•more TPDOs shall be sent than the CANbus may accept due to insufficient CAN bit rate compared to TPDO/Event Timer •excessive bus load or unfavourable setting of COB-ID in the CANopen network prevents TPDOsending•Object 0x1800/5- event timer- is set to 0.1.9 Error HandlingDepending on the type of error occured, the sensor will react accordingly:* according to DS-301, see chapter 1.7 SDO Services** details see chapter 1.9.1 Emergency Messages1.9.1 Emergency MessagesCOB-ID EMCY in object 0x1014.Error-Register in object 0x1001.0x50xx Device Hardware 0x60xx Device Software 0x80xx Monitoring 0x90xx External Error1.10 Error Objects1.10.1 Manufacturer-specific StatusThe object 0x1002 shows the sensor status bit code and is used for internal process control purposes. For servicing this information can be requested via SDO (see chapter 1.7 SDO Services).Bit Definition (if bit value = 1)2 CAN Bus-Off Timer started0-1 NMT Condition of Sensor%11 stopped%10 operational%01 pro-operational%00 initialisation1.11 Non-Volatile Storage and Data RestorationDefault values for all data objects are stored in the non-volatile program memory.Data encryption to the non-volatile memory is only admitted in the pre-operational status.• Storage via LSS:Data must be stored through the LSS Service Configuration/Store while in LSS Configuration Mode (see chapter 1.6 LSS / Layer Setting Service)• Storage via SDO:Object 0x1010:Data is stored in the non-volatile memory during encryption of object 0x1010 with …save“ signature (0x65766173).Object 0x1011:Encryption of object 0x1011 with the sig nature …load“ (0x64616F6C) will upload data from the non-volatile memory. Default settings are being restored (see chapter 1.7 SDO Services).CAUTION: In case of custom programmed parameters like node-ID, averaging, bit rate etc. these will be reset to default in case of the corresponding reset command below (default values see chapter 1.4 Object Library).Object 0x1010 Object 0x1011 Subindex /1AllSubindex /2CommunicationSubindex /3ApplicationSubindex /4ManufacturerCOB-ID SyncGuard Time X XLife Time Factor X XHeartbeat Timer X XTPDO COB-ID D XTPDO Trans Typ X XTPDA Inhibit Time X XTPDO Event Timer X XTPDO Mapping X XNMT Startup X XNode-ID X (TP1/TH1) X (TF1) BitRate X (TP1/TH1) X (TF1) Number of position markers (only TP1 / TH1) XCustom (only TP1 / TH1) X Operating Parameters X XLinear Encoder Measuring Step Settings X XPreset Value X XCAM Enable X XCAM Polarity X XCAM Low Limit X XCAM High Limit X XCAM Hysterese XWork Area Low Limit XWork Area High Limit XX: data saved or restoredD: data set to default value• Delete via SDO Object 0x1010:Additionally to the functionality defined in CiA standard DS-301, CANopen library offers the possibility to delete data inthe non-volatile memory. Del ete process is initiated by sending the signature “kill” (0x6C6C696B) to object 0x1010.• Manufacturing Mode Object 0x1010▪Only TM1 series:If the sensor is out of function and the signature “boot” 0x746F6F62 in object 0x1000 (device type) is active, the sensor is in manufacturing mode. This mode can be left by power off-on or via the operationalcommand.1.12 AbbreviationsCAN Controller Area Networkch channelCOB-ID Communication Object Identifierconst constant parameter, only readableDLC Data Length CodeDS Draft StandardEMCY Emergency ServiceNMT Network-ManagementPDO Process Data ObjectPos Position (value)ro read only, parameter can changerw read/writeRx Novotechnik sensor is consumer of the CAN data frameRTR Remote Transmission RequestSDO Service Data ObjectSYNC Synchronisation messageTPDO Transmit Process Data ObjectTx Novotechnik sensor is producer of the CAN data frame1.13 Document ChangesRevision Changes Date WhoV00 First edition 16.07.14 VM/mm V07 1.2.5 / 1.3.1 object 1801x2: event driven transmission deleted for TPDO2. 1.3.1 objects:TPDO1 and TPDO2: name modified. 1.3.object 1800/2 and 1801/2 comment: synchronous1...240 instead 1...239, TPDO off: 0 added01.04.20 VM/mmV08 1.3.1 object 1010/4 user parameter data instead of manufacturer defined parameters.1.3.1 1010/5 added (Manufacturer data parameter). 1.10. signature kill 6C6C696B insteadof 6B696C6C, comment regarding manufacturing mode added21.01.21 VM/mmV09 1.2 Support added, all further chapter numbers changed1.8.3 Textual modifications 07.09.2117.11.22VM/mm。

CiA Draft Standard 419CAN open Device profile for battery chargersVersion 1.0.101 January 2005© CAN in Automation (CiA) e. V.HistoryDate Version Changes2003-03-15 1.0Released as Draft Standard Proposal2005-01-01 1.0.1Publication as Draft Standard-Partly re chaptered-Minor editorial corrections-Detailed description of PDO parametersGeneral information on licensing and patentsCAN in AUTOMATION (CiA) calls attention to the possibility that some of the elements of this CiA specification may be subject of patent rights. CiA shall not be responsible for identifying any or all such patent rights.© CiA 2005-01-01All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from CiA at the address below.CAN in Automation e. V.Am Weichselgarten 26DE - 91058 Erlangen, GermanyTel.: +49-9131-69086-0Fax: +49-9131-69086-79Url: Email:headquarters@ii© CiA 2005 – All rights reservedContents1Scope (5)2References (6)3Abbreviations and definitions (7)3.1Abbreviations (7)3.2Definitions (7)4Operating principles (8)4.1General (8)4.2Physical layer (8)4.2.1Connector (8)4.2.2CAN transceiver (8)5Error handling (9)5.1Principle (9)5.2Error behavior (9)5.3Additional error code meanings (9)6Communication object definitions (10)6.1Introduction (10)6.2Detailed object definitions (10)6.2.1Object 1000h: Device type (10)6.2.2Object 1001h: Error register (10)6.2.31st RPDO (11)6.2.3.1General (11)6.2.3.2Object 1400h: Communication parameter (11)6.2.3.3Object 1600h: Mapping parameter (12)6.2.41st TPDO (13)6.2.4.1General (13)6.2.4.2Object 1800h: Communication parameter (13)6.2.4.3Object 1A00h: Mapping parameter (14)6.2.52nd RPDO (15)6.2.5.1General (15)6.2.5.2Object 1401h: Communication parameter (15)6.2.5.3Object 1601h: Mapping parameter (16)6.2.62nd TPDO (18)6.2.6.1General (18)6.2.6.2Object 1801h: Communication parameter (18)6.2.6.3Object 1A01h: Mapping parameter (19)© CiA 2005 – All rights reserved iii6.2.73rd RPDO (20)6.2.7.1General (20)6.2.7.2Object 1402h: Communication parameter (20)6.2.7.3Object 1602h: Mapping parameter (21)6.2.83rd TPDO (22)6.2.8.1General (22)6.2.8.2Object 1802h: Communication parameter (22)6.2.8.3Object 1A02h: Mapping parameter (24)7Application object definitions (26)7.1Introduction (26)7.2Detailed object definition (26)7.2.1Object 6000h: Battery status (26)7.2.2Object 6001h: Charger status (26)7.2.3Object 6010h: Temperature (27)7.2.4Object 6052h: Ah returned during last charge (27)7.2.5Object 6060h: Battery voltage (28)7.2.6Object 6070h: Charge current requested (29)7.2.7Object 6080h: Charger state of charge (29)7.2.8Object 6081h: Battery state of charge (30)Appendix A (informative): Battery type parameter (31)Appendix B (normative): Pilot signal (31)Appendix C (informative): Overview on application objects (31)iv© CiA 2005 – All rights reserved1S copeThis device profile defines the battery charger communication and application objects in order to obtain sufficient information from the battery module to allow a charge to be carried out. Optional data is a selection of data commonly used in the industry to provide enhanced features. Chargers compliant to this standard shall use communication techniques, which conforms to those described in the CANopen application layer and communication profile.© CiA 2005 – All rights reserved 52 References/CiA301/CiA 301, CANopen application layer and communication profile/CiA302/CiA 302, Framework for programmable CANopen devices (not published)/CiA303-1/CiA 303-1, CANopen cabling and connector pin assignment/CiA418/CiA 418, CANopen device profile for battery modules/ISO11898-2/ISO 11898-2, Road vehicle – Controller area network (CAN) – Part 2: High-speed medium access unit6© CiA 2005 – All rights reserved3 Abbreviations and definitions3.1 AbbreviationsCAN Controller area networkCAN-ID CAN identifierCOB-ID Communication object identifierPDO Process data objectRPDO Receive process data objectSDO Service data objectTPDO Transmit process data object3.2 DefinitionsThe definitions given in /CiA301/ apply to this specification, too.© CiA 2005 – All rights reserved 74 Operating principles4.1 GeneralThe purpose of the charger is to provide information to a battery module sufficient to allow a charge to be carried out. All devices conforming to this specification shall provide the mandatory objects in the manner defined. Optional objects may be implemented in the manner defined.One default RPDO is defined to receive the battery temperature and status information. Optional RPDOs are defined for receive battery voltage, current requests and state of charge.One default TPDO is defined to transmit charger status. One optional TPDO adds charge returned to the data received. Charger parameter information may be configured by SDO services.The charger module shall support the heartbeat function, and may optionally be a time-stamp producer.layer4.2 Physical4.2.1 ConnectorThe charger shall have a 5-wire interconnect. The communications bus shall use three of these lines (CAN_L, CAN_H, and ground), and two shall be used for the pilot signal. The actual connector used and its pin configuration will vary depending on the charger’s application, and thus is outside of the scope of this document.transceiver4.2.2 CANThe CAN bus shall use standard high-speed differential transceivers compliant to /ISO11898-2/. The charger shall support at least the 125 kbit/s default bit-rate. A termination resistor of 124 Ohm shall be included in the default charger configuration if the charger is connected to a single battery module.In case the charger device is hooked up to the in-vehicles CANopen network, it shall support automatic bit-rate detection and shall not use a termination resistor. The maximum length of the stub length cable is given in /CiA303-1/.8© CiA 2005 – All rights reserved5 Errorhandling5.1 PrincipleEmergency messages are triggered by internal errors in the device, and are assigned the highest possible priority to minimize latency on access to the bus. The emergency message contains the emergency error code and the error register object /CiA301/. Additional data bytes are included in the message, which may be used for manufacturer-specific information.5.2 Error behaviorIf a serious device failure is detected, the module shall enter the pre-operational state by default. If object 1029h is implemented, the module may be configured to enter the stopped state or remain in the current state as alternatives. Device failures shall include the following communication errors:•CAN bus-off condition•Heartbeat event with the state ‘occurred’Device failure may also be caused by internal module failures, e.g. missing the pilot signal.5.3 Additional error code meaningsThe CANopen standard error codes are given in /CiA301/. There are no additional error codes defined.© CiA 2005 – All rights reserved 96 Communication object definitions6.1 IntroductionThe default RPDOs and TPDOs shall be not valid (bit 31 of COB-ID is 1) because of the not pre-defined COB-ID parameters. These COB-ID parameters shall be configured dynamically. In order to achieve that, the charger module scans the network for the battery module by reading the object 1000h of all nodes. If the battery module is detected, the charger module reads the configured COB-IDs of the PDOs and assigns these values to its PDOs correspondingly. In order to request dynamically an SDO connection to the battery module, the charger device shall support dynamic SDO requests as defined in /CiA302/. The in-vehicle CANopen manager shall support dynamic establishment of SDO connections, too.6.2 Detailed object definitionsBattery charger modules compliant with this device profile shall have default values for some communication objects (1000h to 1FFF h), which are not fully specified in /CiA301/.1000h: Device type6.2.1 ObjectThis object describes the type of battery charger and its functionality.VALUE DEFINITION3116150Additional information Device profile numberMSB LSBDevice profile number: 419dAdditional information: Reserved (00h)OBJECT DESCRIPTIONSee /CiA301/.ENTRY DESCRIPTIONSee /CiA301/.6.2.2 Object1001h: Error registerThe device specific bit of the error register is reserved for future use.10© CiA 2005 – All rights reserved6.2.3 1st RPDO6.2.3.1 GeneralThis RPDOs shall receive asynchronously the value of the battery status and temperature information. The battery charger may trigger this RPDO by remote frame.6.2.3.2 Object1400h: Communication parameterVALUE DEFINITIONSee /CiA301/.OBJECT DESCRIPTIONINDEX1400hName RPDO parameterObject code RECORDData type PDO CommParCategory MandatoryENTRY DESCRIPTIONSub-index00hDescription highest sub-index supportedEntry category MandatoryAccess roPDO mapping NoValue range see /CiA301/Default value NoSub-index01hDescription COB-IDEntry category MandatoryAccess rwPDO mapping NoValue range see /CiA301/Default value bit 31=1 (other bits =don’t care)Sub-index02hDescription transmission typeEntry category MandatoryAccess roPDO mapping NoValue range see /CiA301/Default value255d© CiA 2005 – All rights reserved 11Sub-index05hDescription Event timerEntry category OptionalAccess rwPDO mapping NoValue range Unsigned16Default value0d1600h: Mapping parameter6.2.3.3 ObjectVALUE DEFINITIONSee /CiA301/.OBJECT DESCRIPTIONINDEX1600hName RPDO mappingObject code RECORDData type PDO mappingCategory MandatoryENTRY DESCRIPTIONSub-index00hDescription highest sub-index supportedEntry category MandatoryAccess wPDO mapping NoValue range see /CiA301/Default value02hSub-index01hDescription temperatureEntry category MandatoryAccess roPDO mapping NoValue range see /CiA301/Default value6010 00 10h12© CiA 2005 – All rights reservedSub-index02hDescription Battery statusEntry category MandatoryAccess roPDO mapping NoValue range see /CiA301/Default value6000 00 08h6.2.4 1st TPDO6.2.4.1 GeneralThe charger module shall transmit periodically status information, if this TPDO has been enabled. The data shall be updated before transmission.1800h: Communication parameter6.2.4.2 ObjectVALUE DEFINITIONSee /CiA301/.OBJECT DESCRIPTIONINDEX1800hName TPDO parameterObject code RECORDData type PDO CommParCategory MandatoryENTRY DESCRIPTIONSub-index00hDescription highest sub-index supportedEntry category MandatoryAccess roPDO mapping NoValue range see /CiA301/Default value05hSub-index01hDescription COB-IDEntry category MandatoryAccess ro or rw (if PDO linking is supported)PDO mapping NoValue range see /CiA301/Default value Bit 31=1 (other bits = don’t care)© CiA 2005 – All rights reserved 13Sub-index02hDescription transmission typeEntry category MandatoryAccess roPDO mapping NoValue range see /CiA301/Default value255dSub-index03hDescription inhibit timerEntry category MandatoryAccess wPDO mapping NoValue range Unsigned16Default value0dSub-index05hDescription event timerEntry category OptionalAccess roPDO mapping NoValue range Unsigned16Default value200d1A00h: Mapping parameter6.2.4.3 ObjectVALUE DEFINITIONSee /CiA301/.OBJECT DESCRIPTIONINDEX1A00hName TPDO mappingObject code RECORDData type PDO mappingCategory Mandatory14© CiA 2005 – All rights reservedENTRY DESCRIPTIONSub-index00hDescription highest sub-index supportedEntry category MandatoryAccess wPDO mapping NoValue range see /CiA301/Default value01hSub-index01hDescription charger statusEntry category MandatoryAccess roPDO mapping NoValue range see /CiA301/Default value6001 00 08h6.2.5 2nd RPDO6.2.5.1 GeneralThis RPDO is an optional substitute for the 1st RPDO and adds the battery voltage to the transmission of the temperature and status. If the battery module supports the corresponding TPDO, the charger may disable the 1st RPDO and enable this one if desired. The battery charger may trigger this RPDO by remote frame.1401h: Communication parameter6.2.5.2 ObjectVALUE DEFINITIONSee /CiA301/.OBJECT DESCRIPTIONINDEX1401hName RPDO parameterObject code RECORDData type PDO CommParCategory Optional© CiA 2005 – All rights reserved 15ENTRY DESCRIPTIONSub-index00hDescription highest sub-index supportedEntry category MandatoryAccess roPDO mapping NoValue range see /CiA301/Default value NoSub-index01hDescription COB-IDEntry category MandatoryAccess rwPDO mapping NoValue range see /CiA301/Default value Bit 31 = 1 (other bits = don’t care)Sub-index02hDescription transmission typeEntry category MandatoryAccess roPDO mapping NoValue range see /CiA301/Default value255dSub-index05hDescription event timerEntry category OptionalAccess rwPDO mapping NoValue range Unsigned16Default value0d1601h: Mapping parameter6.2.5.3 ObjectVALUE DEFINITIONSee /CiA301/.16© CiA 2005 – All rights reservedOBJECT DESCRIPTIONINDEX1601hName RPDO mappingObject code RECORDData type PDO mappingCategory MandatoryENTRY DESCRIPTIONSub-index00hDescription highest sub-index supportedEntry category MandatoryAccess roPDO mapping NoValue range see /CiA301/Default value03hSub-index01hDescription temperatureEntry category MandatoryAccess roPDO mapping NoValue range see /CiA301/Default value6010 00 10hSub-index02hDescription battery statusEntry category MandatoryAccess roPDO mapping NoValue range see /CiA301/Default value6000 00 08hSub-index03hDescription battery voltageEntry category MandatoryAccess roPDO mapping NoValue range see /CiA301/Default value6060 00 20h© CiA 2005 – All rights reserved 176.2.6 2nd TPDO6.2.6.1 GeneralThis TPDO is optional and contains in addition to the charger status the Ah returned during the charge in progress. The data shall be updated before transmission.6.2.6.2 Object1801h: Communication parameterVALUE DEFINITIONSee /CiA301/.OBJECT DESCRIPTIONINDEX1801hName TPDO parameterObject code RECORDData type PDO CommParCategory OptionalENTRY DESCRIPTIONSub-index00hDescription highest sub-index supportedEntry category MandatoryAccess roPDO mapping NoValue range see /CiA301/Default value05hSub-index01hDescription COB-IDEntry category MandatoryAccess rwPDO mapping NoValue range see /CiA301/Default value Bit 31 = 1 (other bits = don’t care)Sub-index02hDescription transmission typeEntry category MandatoryAccess roPDO mapping NoValue range see /CiA301/Default value255d18© CiA 2005 – All rights reservedSub-index03hDescription inhibit timerEntry category OptionalAccess rwPDO mapping NoValue range Unsigned16Default value0dSub-index05hDescription event timerEntry category MandatoryAccess rwPDO mapping NoValue range Unsigned16Default value200d1A01h: Mapping parameter6.2.6.3 ObjectVALUE DEFINITIONSee /CiA301/.OBJECT DESCRIPTIONINDEX1A01hName TPDO mappingObject code RECORDData type PDO mappingCategory OptionalENTRY DESCRIPTIONSub-index00hDescription highest sub-index supportedEntry category MandatoryAccess rwPDO mapping NoValue range see /CiA301/Default value02h© CiA 2005 – All rights reserved 19Sub-index01hDescription charger statusEntry category MandatoryAccess roPDO mapping NoValue range see /CiA301/Default value6001 00 08hSub-index02hDescription Ah returned during last chargeEntry category MandatoryAccess roPDO mapping NoValue range see /CiA301/Default value6052 00 10h6.2.7 3rd RPDO6.2.7.1 GeneralThis RPDO is an optional additional object with which the charger can receive a requested current value and the battery status of charge. The battery charger may trigger this RPDO by remote frame.1402h: Communication parameter6.2.7.2 ObjectVALUE DEFINITIONSee /CiA301/.OBJECT DESCRIPTIONINDEX1402hName RPDO parameterObject code RECORDData type PDO CommParCategory OptionalENTRY DESCRIPTIONSub-index00hDescription highest sub-index supportedEntry category MandatoryAccess roPDO mapping NoValue range see /CiA301/Default value No20© CiA 2005 – All rights reservedSub-index01hDescription COB-IDEntry category MandatoryAccess rwPDO mapping NoValue range see /CiA301/Default value Bit 31 = 1 (other bits = don’t care)Sub-index02hDescription transmission typeEntry category MandatoryAccess roPDO mapping NoValue range see /CiA301/Default value255dSub-index05hDescription event timerEntry category OptionalAccess rwPDO mapping NoValue range Unsigned16Default value0d1602h: Mapping parameter6.2.7.3 ObjectVALUE DEFINITIONSee /CiA301/.OBJECT DESCRIPTIONINDEX1602hName RPDO mappingObject code RECORDData type PDO mappingCategory Optional© CiA 2005 – All rights reserved 21ENTRY DESCRIPTIONSub-index00hDescription highest sub-index supportedEntry category MandatoryAccess rwPDO mapping NoValue range see /CiA301/Default value02hSub-index01hDescription charge current requestedEntry category MandatoryAccess roPDO mapping NoValue range see /CiA301/Default value6070 00 10hSub-index02hDescription battery state of chargeEntry category MandatoryAccess roPDO mapping NoValue range see /CiA301/Default value6081 00 08h6.2.8 3rd TPDO6.2.8.1 GeneralThis TPDO is optional and shall contain the charger status the Ah returned during the charge in progress to the transmission of the charger status and the charger state of charge. The data shall be updated before transmission.1802h: Communication parameter6.2.8.2 ObjectVALUE DEFINITIONSee /CiA301/.22© CiA 2005 – All rights reservedOBJECT DESCRIPTIONINDEX1802hName TPDO parameterObject code RECORDData type PDO CommParCategory OptionalENTRY DESCRIPTIONSub-index00hDescription highest sub-index supportedEntry category MandatoryAccess roPDO mapping NoValue range see /CiA301/Default value02hSub-index01hDescription COB-IDEntry category MandatoryAccess rwPDO mapping NoValue range see /CiA301/Default value Bit 31 = 1 (other bits = don’t care)Sub-index02hDescription transmission typeEntry category MandatoryAccess roPDO mapping NoValue range see /CiA301/Default value255dSub-index03hDescription inhibit timerEntry category OptionalAccess rwPDO mapping NoValue range Unsigned16Default value0d© CiA 2005 – All rights reserved 23Sub-index05hDescription event timerEntry category MadatoryAccess rwPDO mapping NoValue range Unsigned16Default value200d1A02h: Mapping parameter6.2.8.3 ObjectVALUE DEFINITIONSee /CiA301/.OBJECT DESCRIPTIONINDEX1A02hName TPDO mappingObject code RECORDData type PDO mappingCategory OptionalENTRY DESCRIPTIONSub-index00hDescription highest sub-index supportedEntry category MandatoryAccess rwPDO mapping NoValue range see /CiA301/Default value03hSub-index01hDescription charger statusEntry category MandatoryAccess roPDO mapping NoValue range see /CiA301/Default value6001 00 08h24© CiA 2005 – All rights reservedSub-index02hDescription Ah returned during last chargeEntry category MandatoryAccess roPDO mapping NoValue range see /CiA301/Default value6052 00 10hSub-index03hDescription chargers state of chargeEntry category MandatoryAccess roPDO mapping NoValue range see /CiA301/Default value6080 00 08h© CiA 2005 – All rights reserved 257 Application object definitions7.1 IntroductionObject description and entry description attributes are specified in /CiA301/. The default value attribute defines the value of an object with access attribute of the value ‘rw’ and ‘wo’ after power-on or application reset7.2 Detailed object definition6000h: Battery status7.2.1 ObjectThis object shall indicate readiness of the battery to accept a charge.VALUE DEFINITIONThe status byte shall have the following format:710Reserved (0)Bit 0MSB LSBBit 0 0= not ready1= readyOBJECT DESCRIPTIONIndex6000hName battery_statusObject code VARData type Unsigned8Category MandatoryENTRY DESCRIPTIONSub-index00hAccess rwPDO mapping DefaultValue range See value definitionDefault value00h6001h: Charger status7.2.2 ObjectThis object shall provide readiness of the charger to deliver a charge to the battery.VALUE DEFINITIONThe status byte has the following format:710Reserved (0)Bit 0MSB LSBBit 00 = not ready1 = ready26© CiA 2005 – All rights reservedOBJECT DESCRIPTIONIndex6001hName charger_statusObject code VARData type Unsigned8Category MandatoryENTRY DESCRIPTIONSub-index00hAccess roPDO mapping DefaultValue range See value definitionDefault value No6010h: Temperature7.2.3 ObjectThis object shall indicate the temperature of the battery pack as measured by a temperature reading device physically mounted somewhere on the battery module.VALUE DEFINITIONTemperature shall be given in °C with resolution 0.125 °C per bit. The minimum range of values shall be -320 to +680 (i.e. -40.0 °C to +85.0 °C). A value of FFFF h shall indicate an invalid measurement. OBJECT DESCRIPTIONIndex6010hName battery_temperatureObject code VARData type Integer16Category MandatoryENTRY DESCRIPTIONSub-index00hAccess rwPDO mapping DefaultValue range FEC0h to 02A8hDefault value FFFF h6052h: Ah returned during last charge7.2.4 ObjectThis object shall provide the number of Ampere-hours delivered to the battery by the charger during the last charge event. The charger device reads the previous value from the battery module by SDO and writes back the current value at the completion of charge. A value of FFFF h shall indicate an invalid value.VALUE DEFINITIONThe resolution shall be 0.125 Ah per bit.© CiA 2005 – All rights reserved 27OBJECT DESCRIPTIONIndex6052hName ah_returned_during_last_chargeObject code VARData type Unsigned16Category Conditional: if TPDO2 is supportedENTRY DESCRIPTIONSub-index00hAccess roPDO mapping Default if TPDO2 is supportedValue range Unsigned16Default value No7.2.5 Object6060h: Battery voltageThis object shall indicate the instantaneous voltage across the battery terminals as measured by a voltage-measuring device on the battery or charger. A value of FFFF FFFF h shall indicate an invalid measurement.VALUE DEFINITIONThe resolution shall be 1/1024 V per bit.OBJECT DESCRIPTIONIndex6060hName battery_voltageObject code VARData type Unsigned32Category Conditional: if RPDO2 is supportedENTRY DESCRIPTIONSub-index00hAccess rwPDO mapping Default if RPDO2 is supportedValue range Unsigned32Default value FFFF FFFF h28© CiA 2005 – All rights reserved7.2.6 Object6070h: Charge current requestedThis object shall indicate the electrical current in Amperes requested by the battery module to be delivered by the charger to the battery.VALUE DEFINITIONThe resolution shall be 1/16 A per bit. FFFF h shall indicate an invalid value.OBJECT DESCRIPTIONIndex6070hName charge_current_requestedObject code VARData type Unsigned16Category Conditional: if RPDO3 is supportedENTRY DESCRIPTIONSub-index00hAccess rwPDO mapping Default if RPDO3 is supportedValue range Unsigned16Default value FFFF h6080h: Charger state of charge7.2.7 ObjectThis object shall provide the charger's estimation of the amount of energy contained in the battery, expressed as a percentage of the total amount of energy the battery can store.VALUE DEFINITIONThe resolution shall be 1 % per bit. FF h shall indicate invalid value.OBJECT DESCRIPTIONIndex6080hName charger_state_of_chargeObject code VARData type Unsigned8Category Conditional: if TPDO2/3 is supportedENTRY DESCRIPTIONSub-index00hAccess roPDO mapping Default if TPDO2/3 is supportedValue range00h to 64h and FF hDefault value No© CiA 2005 – All rights reserved 297.2.8 Object6081h: Battery state of chargeThis object shall indicate the battery's measurement of the amount of energy contained in the battery, expressed as a percentage of the total amount of energy the battery can store.VALUE DEFINITIONResolution shall be 1 % per bit.OBJECT DESCRIPTIONIndex6081hName battery_state_of_chargeObject code VARData type Unsigned8Category Conditional: if RPDO3 is supportedENTRY DESCRIPTIONSub-index00hAccess rwPDO mapping Default if RPDO3 is supportedValue range00h to 64h and FF hDefault value FF h30© CiA 2005 – All rights reservedDS 419 V1.0.1CANopen device profile for battery charger CiA© CiA 2005 – All rights reserved 31Appendix A (informative): Battery type parameter See /CiA418/Appendix B (normative): Pilot signal See /CiA418/Appendix C (informative): Overview on application objectsCharger module specific mandatory and optional objects are listed in following table:Table 1: Overview on application objectsIndex Object code NameData type Access Category6000h VAR Battery status Unsigned8rw M 6001h VAR Charger statusUnsigned8ro M 6010h VAR Battery temperatureInteger16rw M 6052h VAR Ah returned during last charge Unsigned16ro C 16060h VAR Battery voltageUnsigned32rw C 16070h VAR Charge current requested Unsigned16rw C 16080h VAR Charger state of charge Unsigned8ro C 16081hVARBattery state of chargeUnsigned8rwC11Mandatory if PDOs are implemented that maps this object by default。

State-of-the-art platform for tomorrows demanding applicationsPlatform Advantages• NX32L execution architecture. • Secure platform.• Hardware accelerated security. • Free RTCU IDE development tool. • Huge standard API. • Open platform SDK.• Comprehensive protocol support. • Instrumented Execution.• Sophisticated deployment tools. • Fast and free email support.World Leader in Advanced and Professional M2M / IoT Technology since 1999.Device Advantages• RTCU MX2 turbo compatible. • High-Performance LX IoT Core. • Large 4 GB Internal Flash drive.• Worldwide LTE Cat.4 Cellular Engine. • Dual SIM card readers. • Bluetooth LE 5.3.• High-precision Dual-band GNSS. • Dead Reckoning and RTK support. • Accelerometer and Gyroscope. • Dual full CAN 2.0B channels.• Multiple RS232/RS485 channels. • Modbus expandable I/O. • 1-Wire bus.• Digital and Analog input/outputs. • Digital audio sub-system.• Durable Aluminium encapsulation. • Integrated battery backup.Experience and Know-howFor almost 25 years Logic IO has been committed to offer the most sophisticated platform for advanced and highly demanding M2M / IoT applications.The RTCU LX2 pro is the result of this accumulatedexperience combined with valuable feedback from hundreds of professional and mission critical applications by major organizations around the world.RTCU products are deployed underground , stationary , on the road , at sea , on the rail and in the skies ! - In any imaginable application and environment.For Professional M2M / IoT ApplicationsThe RTCU LX2 pro is designed for the most sophisticated M2M and Internet of Things applications that demand the most advanced product available on the market today.The RTCU LX2 pro rests on the RTCU M2M Platform, that brings all the necessary tools together to develop, implement and maintain the most sophisticated M2M/IoT applications.The development task is supported by the free RTCU IDE development environment, complemented by a large and comprehensive documentation and application example library.The RTCU Communication Hub is the cornerstone of the communication infrastructure ensuring reliable two-way device communication in any network environment.Deploying and maintaining new application and firmware versions for devices in the field are handled by the powerful RTCU Deployment Server.Two decades of know-how in one product!Platform:• Based on the RTCU M2M Platform .• NX32L (NX32 for Linux) execution architecture.• RTCU IDE development tool.• Operates under a full and highly optimized Linux variant.• Secure communication with TLS and hardware assisted encryption/authentication. • Open and extendable with Platform SDK.Wireless Communication:• Worldwide LTE Cat. 4 Multi-Band Cellular Engine. • Dual SIM-card readers and support for eSIM. • Bluetooth Low-Energy - BLE 5.3.• High-precision Dual-band L1/L5 Multi-Constellation GNSS positioning engine . • Optional: Dead-Reckoning and RTK with sub-meter accuracy.Wired Communication:• 2 x Full CAN 2.0B channels with hardware filtering and multi-speed support. • 1-Wire bus for accessories such as ID-button reader, temperature sensors, etc. • 2 x RS232 channels and 1 x RS485 channel.I/O Interfaces:• 6 x digital inputs.• 4 x high-power solid-state digital outputs .• 2 x analog inputs with flexible range of 0..10VDC or 0..30VDC (12 bits). • Expandable I/O with standard Modbus modules.User Interaction:• Digitized audio subsystem.• DTMF support for Interactive Voice Response applications . • High-speed Mini-USB service-port connector. • On-board Accelerometer and Gyroscope .Storage:• Internal flash drive with 4 GB total capacity. • Persistent memory and circular datalogger .Encapsulation:• Housed in a durable Aluminium case.Find out more and start developing today!Learn more about the RTCU M2M platform and the NX32L architecture in the ”The RTCU M2M Platform” data sheet.To learn more about the technical details and usage of the RTCU LX2 pro, please download the ”RTCU LX2 pro Technical Manual ”.Also make sure to get the FREE RTCU IDE Development Environment, RTCU Communication Hub and theDeployment Server to get a hands-on experience how rapid development/deployment of game changing M2M/IoT applications were meant to be.Wired Communication • 2 x Full CAN2.0B with hardwarefiltering and multi-speed support. • 1 x RS232 with control signals.• 1 x RS232 with RX/TX.• 1 x RS485 with Modbus support. • 1-Wire bus.• USB service/programming port. Cellular Engine• LTE Cat.4 Engine (Worldwide).Max 150 Mbps(DL)/Max 50 Mbps(UL). LTE FDD: 15 bands. LTE-TDD: 4 bands. WCDMA: 7 bands. GSM: Quad-band.• DTMF decoding / transmission.• Digitized voice playback / IVR. • Dual SIM card reader (int/ext). • Mini-SIM 1.8/3 volt• Application controlled SIM card. • Optional eSIM.User Interaction • 4 x bi-colour LED. • 2 x DIP-switches.• Switches for RS485 /CAN termination. • CAN write enable switch. • Reset / recovery switch.RTCU M2M Platform• NX32L Execution Architecture. • Fully NX32 compatible.• Open and user-extendable API. • RTCU M2M Platform SDK.Bluetooth• Bluetooth Low Energy 5.3. • IEEE 802.15.4-2011 PHY• Optional: Zigbee and OpenThread.Audio• Fully digitized audio system. • Transfer, store and play audio. • Digitized cellular audio.GNSS• Multi-constellation.• Dual-Band using L1 / L5 bands. • GPS, Galileo, GLONASS, BeiDou, and QZSS.• SBAS: WAAS, EGNOS, MSAS, and GAGAN.• AGPS capable.• RTCM v2.3 and v3.3 output capable. • Accuracy: < 1m CEP (@-130 dBm). • Anti-jamming, Noise cancellation. • Active 3 volt GNSS antenna.• RTK (optional) with sub-centimeter accuracy.• Dead Reckoning with IMU (optional). • Optional dual GNSS receiver.I/O Interface• 4 x digital solid-state digital output.Max. 36 volt / 1.5 A per. channel.Short-circuit, ESD, Inductive kick-back protected up to 20 mH.• 6 x digital inputs with ignition. Logic high: 8 to 40 VDC. Logic low: -5 to 3 VDC.Impedance: 13 kohm @ 12V. • 2 x analog inputs.Range is 0..10VDC or 0..30VDC. Resolution: 12 bitAccuracy: Typ. ±0.3% FSR @ 25°C. Impedance: 40 kohm.• Protected against transients and low-pass filtered.Logic IO Worldwide HeadquartersHolmboes Allé 14 8700 Horsens DenmarkPhone: +45 7625 0210 Fax: +45 7625 0211Commercialenquiries:*****************Technicalsupport:*******************Sensors• Temperature sensor.• 3-axis Accelerometer. ±16g@16b. • 3-axis Gyroscope. ±2000dps @16b.LX Hardware Core• Powerful 32-bit ARM processor. • Hardware floating point and DSP. • 128 Mbyte RAM.• Up-to 512 Mbyte NAND flash.• Real-time clock with battery-backup. Storage• 4 GB Internal flash drive. • Persistent data flash.• Multiple circular dataloggers.Logic IO Worldwide HeadquartersHolmboes Allé 14 8700 Horsens DenmarkPhone: +45 7625 0210 Fax: +45 7625 0211Commercialenquiries:*****************Technicalsupport:*******************Models AvailableSKU: RT-LX2P RTCU LX2 pro.LX2P DS V1.00 UK - All rights reserved.Power Management • Low-power modes. • Wait for Event:Timer, Digital input, Accelerometer, RS232, RS485, CAN, Cellular, and Power change state.• Wait for event, from: 0.4 mA@12V.• Supervision of supply voltage / type.Environmental Specification • Operating temperature: -40 to 65°C. • Battery charge temperature: -10 to 45 °C.• Recommended storage temperature: 0 to 45°C.• Humidity: 5..90% (non condensing). • Ingress Protection: IP20 .Physical Characteristics • Encapsulation: Aluminium profile. • Colour: Anodized natural grey. • Material: Aluminum and plastic.• Approx. 300 gram without accessories. • W 97 x H 35 x D 132 mm. (without connectors).• Optional mounting bracket Warranty• Two-years return to factory parts and labor.• Optional warranty up to 5 years. (restrictions apply).Approvals• 2007/46/EC UN ECE R10 Rev. 06 (E1). • 2014/53/EU Radio Equipment Directive. • 2011/65/EU RoHS Directive. • Cellular:GCF/CE/FCC/PTCRB/IC/Anatel/SRRC/NAL/ CCC/KC/NCC/JATE/TELEC/RCM/IFETEL/FAC/NBTC/ICASA .Battery and Charger• On-board 2 Ah (nominal) Li-Ion battery. • Intelligent charger with temperature throttle and sub-zero degrees support.Electrical• Operating voltage: 8 to 36 VDC. • Short and reverse power protected. • 5 VDC-out @ 500 mA.External Interfaces• Plug-compatible with the MX2 turboand the RTCU NX-200.• SIM-card slot for a mini-SIM card• SIM card tray presence detection.• 4 x LED indicators and 2 x DIP switches. • Reset/recovery switch.• RJ45 for RS232 with full control signals. • Dip-switch under frontplate:• CAN/RS485 termination. • CAN write enable.• SMA Female connector for cellular. • SMA-RP Female connector for BT. • SMA Female connector for GNSS. • USB 2.0 service port mini-USB. • TE-Connectivity ”Mate’n’Lok’:• Power • I/O.• RS232 / RS485 • CAN • 1-wire。