Technical User Manual Avisaro 4.0 Product Series

Transcription

1 Technical User Manual Avisaro 4.0 Product Series including PC Companion Software RS232 CAN 4..20mA Analog Version / Date

2 1. TABLE OF CONTENT Hint: Use <cntrl> key with mouse click within the table of content and on links within the document to jump to the destination. 1. Table of Content 2 2. This Document Document links Current document version History 5 3. Quick-Guide Power Supply Configuration Connect your device Add storage or Connect wirelessly 6 4. User Interface Blink-Codes Start and stop operation 7 5. USB stick 8 6. Using the RS232 interfaces RS232 Data logging Merge ( Sniffing ) data from two RS232/RS485 into one file More details Configuration 9 7. Using the CAN bus interfaces CAN Data logging example More details Quick configuration guide Initial Operating CAN filter options Filter CAN ID range Filter single CAN IDs with interval Pre-defined profiles 16 jump to TOC Page: 2

3 9. Data storage options Storing 4..20mA data Wireless Option WPA Enterprise Cloud and wireless access FTP Server (Download from logger) Recommended FTP client and settings How to download files from the logger 18 Typical error messages FTP Client (Upload to server) PC Companion Software Driver installation Concept of operation Initial Set-Up Using the PC Companion Tool Device Configuration General Settings Device Configuration Global HW Settings Interfaces (1st) RS232/RS485 and (2nd) RS232/RS Interfaces (1st) CAN and (2nd) CAN Data Processing Serial data (generic) Data Processing CAN data (generic) Backup and Recover Configuration Interface description and Pin Layout Power (Barrel) RS232 Interface Default RS232 settings Signal levels D-Sub Connector x RS232 Interface ( M41124 / C41124 ) x RS232 SILVER ( M41076, C41076 ) RS WAGO Connector 30 Page: 3 jump to TOC

4 13.4. CAN Bus Interface CAN configuration and default settings Signal Levels D-Sub Connector ( M43014, C43014 ) WAGO Connector ( M43324 / C43324 ) Screw type connector (M43076, C Analog Current loop (4..20 ma) Interface WAGO Connector Screw type connector Electrical Characteristics Recommended settings Analog 10V Interface Electrical Characteristics Analog Resistive Sensor Input x Analog Board Interface ( M4AB24 ) Analog 2V Interface Electrical Characteristics Internal and external sensors Internal GPS receiver Firmware Update Appendix Understanding product serial numbers CAN Storage Format Example Text (CSV) CAN Storage Format Example Vector CANalyzer 45 jump to TOC Page: 4

5 2. THIS DOCUMENT 2.1. DOCUMENT LINKS Links within the document are active - click to jump back and forth. The document is read best online with a PDF reader CURRENT DOCUMENT VERSION Check for the latest document version the following link: (German site) Active links: This document has active links. Click within the PDF on internal and external references to navigate quickly to the target HISTORY Added: CAN Single ID filter External GPS settings Analog electrical limits Added: RS232 details Added: FTP download information CAN example use case and storage format Added: More details and error corrections Added: More interfaces Added: Initial version Page: 5 jump to TOC

6 3. QUICK-GUIDE This should get you started in 5 minutes: 3.1. POWER SUPPLY To operate the logger, connect regular power (6..32V) to the appropriate connector. Quite a few functions (i.e. analog converter) need the regular power supply to work properly. For configuration, a micro USB cable can be used to power the device, however for normal operation a regular power supply is mandatory CONFIGURATION Download the PC Companion Tool from the Avisaro website. (German) This tool is used to make all the settings - like baudrate and sample rates depending on your interface. All products are shipped pre-configured, thus only a few settings are necessary if at all CONNECT YOUR DEVICE Connect your device to the Avisaro product. The interface description is found further down in this documentation ADD STORAGE OR CONNECT WIRELESSLY Plug in a USB memory stick to the appropriate slot. That s it. The device starts automatically with data logger or transfer. jump to TOC Page: 6

7 4. USER INTERFACE 4.1. BLINK-CODES There is one multicolor LED to signal states of the Avisaro device. Code What is means Action Green & blue fading All is fine None Idle state, no data arriving Green flashing Data are coming in (RS232, CAN interface) 1) Red flashing No USB stick or button was pushed Insert USB stick Or press button again 1) On analog loggers (e.g. 4 20mA) and similar interfaces, data are read continuously, thus no green flashing is shown 4.2. START AND STOP OPERATION The Avisaro 4.0 starts with operation right after power on if an USB stick is inserted. Also, after re-inserting a USB stick, the operation start automatically. Page: 7 jump to TOC

8 5. USB STICK USB Memory sticks from 4 to 256 GByte can be used. The stick needs to be formatted as FAT or FAT32 (preferred) jump to TOC Page: 8

9 6. USING THE RS232 INTERFACES 6.1. RS232 DATA LOGGING To record a RS232 data stream, configure the logger as follows: using the PC companion, navigate to: General Stetting: Global function: Generic Device 1st / 2nd RS232: Protocoll: "Regular RS232" Stream to "generic RS232" select the baudrate you like and click 'Write config" Commands Device Control -> Reboot Now you are ready to go Insert a USB Stick. When data are received, the LED is flashing green and data are stored on USB stick. You can stop the logging by pressing the button (and restart with it). Extract the USB drive to read the data you logged MERGE ( SNIFFING ) DATA FROM TWO RS232/RS485 INTO ONE FILE Merging data from two RS232/RS485 interfaces into one file is often useful for debugging the communication with a device More details See paragraph RS232 Interface on information for the hardware interface description Configuration Device Configuration Global HW setting : Page: 9 jump to TOC

10 Interfaces (1st) RS232/RS485 / (2nd) RS232/485 : Configure the baudrate and interface setting to your application. Select the char field to match the end of line field. In this case it is Hex 20 which translates into a space as text. Data Processing Serial data (generic) : Data Endpoints USB Stick Select 1st file to Every hour and set the other one to Off Last but not least, reboot the Logger: Commands Simple CMDs jump to TOC Page: 10

11 Page: 11 jump to TOC

12 7. USING THE CAN BUS INTERFACES 7.1. CAN DATA LOGGING EXAMPLE More details See paragraph CAN Bus Interface on information for the hardware interface description. See paragraph 11. PC Companion Software for all the configuration details. See paragraph CAN Storage Format Example Text (CSV) on the text storage format Quick configuration guide To configure the Logger for basic CAN Bus data logging, follow the steps: Use PC Companion Software to enable the CAN interface (which usually are already enabled): Device Configuration Global HW setting : Click on Write Config to store send the setting to the Logger. Set the proper CAN baud rate - which depends on your application: Interfaces (1st) CAN / (2nd) CAN : jump to TOC Page: 12

13 To start with you initial testing, disable Filter setting (= off ), select Collect time to 100 ms which is a good starting value and select Stream to Generic CAN. Click on Write Config. Data Processing CAN data (generic) : Select Storage format to Text (CSV) data which gives to you readable text file to check whether data arrived. Select Storage endpoint to Generic file (A). Data Endpoints USB Stick Page: 13 jump to TOC

14 Select 1st file to Every hour and set the other one to Off Last but not least, reboot the Logger: Commands Simple CMDs Initial Operating Plug in USB stick into logger, the LED should switch from red flashing to green/blue fading. Send CAN data from you application. The LED should flash green/blue with data coming in. Extract the USB stick and connect to a PC. Read the file generated in the logs_1 folder - this is a text file which can be opened with any editor: See CAN Storage Format Example Text (CSV) on reading the format of stored CAN data. There are more options - check this documentation table of content for all the details CAN FILTER OPTIONS Filter CAN ID range.. to be filled in later.. jump to TOC Page: 14

15 Filter single CAN IDs with interval Single CAN IDs can be filtered on both channels. To activate single CAN IDs: To define the CAN IDs and the intervals, a configuration file is placed on USB stick. The file names are can1flt.txt for CAN 1 and can2flt.txt for CAN 2. The content of the file is (example): , , , , , , 5000 Use a regular text editor to create the files. The first number is the CAN ID in decimal format, the second number is the time interval in millisecond. I.e the CAN ID is stored once every 500 ms. Maximal 50 entries are allowed. Page: 15 jump to TOC

16 8. PRE-DEFINED PROFILES For custom and future use only. Ask for separate documentation 9. DATA STORAGE OPTIONS 9.1. STORING 4..20MA DATA Example: $ADC, 2018/04/19,17:17:23,753, ma, ma $ADC, 2018/04/19,17:17:24,753, ma, ma $ADC, 2018/04/19,17:17:25,753, ma, ma $ADC, 2018/04/19,17:17:26,753, ma, ma Storage time With roughly 50 Bytes per entry and assuming one entry per second, it is 4.3 Mbyte per day. A 4 GByte USB drive would store roughly 930 days or 2.5 years worth of data. See interface pin layout: Analog Current loop (4..20 ma) Interface 10. WIRELESS OPTION Getting started Basic settings AvisaroSoftAP WPA ENTERPRISE The server certificate needs to be updated. The system clock needs to be up to dated. jump to TOC Page: 16

17 11. CLOUD AND WIRELESS ACCESS FTP SERVER (DOWNLOAD FROM LOGGER) Recommended FTP client and settings The recommended FTP client the the FileZilla client. This settings needs to be made, all others are default settings: Page: 17 jump to TOC

18 How to download files from the logger 1) Check for the IP address of the logger. In this case: ) Enter this address in FileZilla: User is admin and password 1234, port number is 21 3) Click connect to get the directory listing: 4) Select the files to download (remember, that the currently written file can t be downloaded) jump to TOC Page: 18

19 Typical error messages 1) Try to transfer the file which is currently written to 2) No USB stick at the logger: FTP CLIENT (UPLOAD TO SERVER) Activate with Cloud settings -> Data Upload / Mode : FTP Requirement: File policy has to be set to hourly Data Endpoints -> USB Stick -> 1st file : Every hour Limitation: Works only for first file channel The upload file gets a prefix this is the name of the logger stored in: Device Configuration -> General Settings -> Device name : e.g. sensor_xyz Page: 19 jump to TOC

20 12. PC COMPANION SOFTWARE The PC Companion Software is used to configure the Avisaro 4.0 Devices. The software is available for download from the Avisaro homepage: (German site) (English site) There are two version to download: Install and Direct start the first runs an installer which requires administrative rights on the PC, the second one can be started without an install process. If unsure, check with your IT department which version to download DRIVER INSTALLATION If you connect the Avisaro Device to the PC using a Micro USB cable, a virtual COM port driver is installed. If this driver does not install automatically, you can download and install this manually: (German site) (English site) CONCEPT OF OPERATION The Avisaro 4.0 is divided into sections: Data are received through an Interface and than forwarded to the Data Processing section. All formatting happens here and then data is forwarded to the Data Endpoint. jump to TOC Page: 20

21 12.3. INITIAL SET-UP After starting the companion software, the virtual COM port number needs to be entered. You can find this number in the Windows Device Manager. This setting is stored for future use. Click on open COM port which will turn green if successful. You can use the check button to verify that the connection is alive. All other settings are deactivated if there is no Avisaro Device attached. You can use the Check button to verify the connection to the Avisaro Device. It should light up green when clicked. The baudrate setting for if connected through real RS22.. can be ignored. This setting is used only in special projects and not scope of this document USING THE PC COMPANION TOOL Click on Write Config to transmit changes in the PC tool to the Avisaro device. Click on Read Config to display the currently stored values (if you navigate between options, the latest settings are read of course automatically). Most settings become active after reboot. This can be done in Commands Device Control: Reboot Device DEVICE CONFIGURATION GENERAL SETTINGS The Global Function defines the main function of the Avisaro device. This setting should not be changed - and for the most part, it is hard wired and can not be changed. Some functions or interfaces are enabled or disabled based on this Global Function setting. The Device name can be user defined and is used for documentation only. Firmware version and WiFi version are displayed here. If no WiFi version is shown, no WiFi is build-in or it is disabled. Page: 21 jump to TOC

22 12.6. DEVICE CONFIGURATION GLOBAL HW SETTINGS The Avisaro 4.0 devices are shipped in a wide range of hardware configurations. If the corresponding hardware is build-in, it can be activated there. = function is enabled, = function is disabled System functions TCP Stack internal function, leave enabled File System internal function, leave enabled Networking Wifi Module see: LAN Interface Mobile Data see: see: Interfaces (Digital) 1st/2nd RS232/RS485 see: RS232 1st/2nd CAN see: CAN Interfaces (Analog) 1st/2nd AD Converter used for 4..20mA and 0..10V: see: Analog Current loop (4..20 ma) Interface see: Analog 10V Interface Sensor (Build-In) Motion Sensor see: jump to TOC Page: 22

23 12.7. INTERFACES (1ST) RS232/RS485 AND (2ND) RS232/RS485 The 1st and 2nd RS232/RS485 settings are identically See paragraph RS232 Interface for the hardware interface description. The Baudrate settings follow typical industry settings and need to match the target application. The Protocoll settings are as follows: Regular RS232 : data are passed on with no further interpretation. Char Terminated : data are grouped as one block until the end of line identifier is reached. GSP(uBlox) : the NMEA strings are treated as one block of data. The Collect Time defines a time period in ms for how long data are collected into one block. A 0 lets the logger process each received character one at a time. A good value is 100ms - thus the logger collects for 100ms data before starting to process them. The End of Line identifier defines the character which ends one block of data. This is only active with the Char Terminated protocol. Page: 23 jump to TOC

24 12.8. INTERFACES (1ST) CAN AND (2ND) CAN The 1st and 2nd CAN Interface settings are identically. See paragraph CAN Bus Interface for the hardware interface description. The Baudrate has to match the baudrate used in the application. The filter settings allow to limit the number of CAN messages logged: Off : not filter is active, all messages are logged Range : This defines a from CAN ID.. to CAN ID pass through filter. CAN IDs lower and higher are filtered. The IDs shown are logged. Enter values as decimal format (note: some application list CAN IDs as HEXx values). Single IDs : Select this option to to filter for single CAN IDs. Single CAN IDs are stored in a configuration file together with the time interval they should be monitored. See Filter single CAN IDs with interval for details. The Collect setting defines how long CAN messages are collected before they are processed. A 0 defines that all messages are processed one by one. A good value is ms. A low number increases the system load and can cause issues particularly when data is forwarded through a network. The Stream to parameter defines how the data should be processes further. The default value is Generic CAN - all other settings are application specific and should not be used. Click on Write Config to transmit any changes. jump to TOC Page: 24

25 12.9. DATA PROCESSING SERIAL DATA (GENERIC) This configuration defines how RS232/RS485 data are processed. Choose the type of formatting and the target. Storage format defines how RS232 data are stored: Off : data are not stored Raw data : data are stored without any formatting as they come from the interface Timestamp+ASCII : data are stored with a leading timestamp followed by the data. This works well for ASCII/Text data, but not good for binary data. Tmestamp+HEX : data are stored with a leading timestamp followed by the data as HEX format. This works well for binary data. Page: 25 jump to TOC

26 DATA PROCESSING CAN DATA (GENERIC) This configuration defines how CAN messages are processed. Choose format and target. The settings are for both CAN channels identically. Storage format defines how CAN messages are stored: Off : data are not stored Text (CSV) data is a text file which can be i.e. imported into EXCEL or text editor. See example: CAN Storage Format Example Text (CSV) Vector CANalyzer is a text file defined used in other loggers as well and can be imported into several other tools. See example: CAN Storage Format Example Vector CANalyzer Storage endpoint defines where to store the data: Off : data are not stored Generic file (A) : default setting jump to TOC Page: 26

27 BACKUP AND RECOVER CONFIGURATION Section: Commands -> Device Control A complete set of settings can be downloaded and retrieved. The xml file can be edited manually to remove a block of configuration which should not be restored. Page: 27 jump to TOC

28 13. INTERFACE DESCRIPTION AND PIN LAYOUT POWER (BARREL) The matching plug has the following dimensions (which are widely used and very much a standard ): Diameter outside: 5.5 mm, inside: 2.1 mm and a shaft of 9.5 mm RS232 INTERFACE This is an industry standard RS232 connection Default RS232 settings Baudrate: No of bits: 8 Parity bits: none Stop bits: 1 Flow control: none Signal levels Max Input voltage range on signal pins: -24 to 24 V Output level provided: -5V to 5V D-Sub Connector Standard SubD-9 connector (male) Connector Interface Pin Signal Direction D-Sub, 9 pol, male 1 st RS232 1 n.c. (optional DCD) 2 RxD - Data in 3 TxD - Data out 4 n.c. (optional DTR) 5 GND Power & Signal 6 n.c. (optional DSR) 7 RTS - Signal out jump to TOC Page: 28

29 8 CTS - Signal in 9 n.c. (optional: VCC (6..32V)) Power Supply voltage does not carry an output voltage thus if the device is powered via barrel connector, Pin 9 does not show the input voltage (internal diode). This is for security reason. If needed, Avisaro can modify the device such that this pin can be used to power other devices x RS232 Interface ( M41124 / C41124 ) Connector Interface Pin Signal Direction WAGO A 2 nd RS232 1 CTS in 2 RTS out 3 RxD in 4 TxD out 5 VCC (6..32V) Power 6 GND Power & Signal WAGO B 1 st RS232 1 CTS in 2 RTS out 3 RxD in 4 TxD out 5 VCC (6..32V) Power 6 GND Power & Signal Cable are connected with the WAGO 734 series connectors. In most product configurations, those adapters are shipped with the box. Check the 'scope of delivery' list. Page: 29 jump to TOC

30 x RS232 SILVER ( M41076, C41076 ) Connector Interface Pin Signal Direction Screw Type 1 st RS232 1 GND Power & Signal 2 VCC (6..32V) Power 3 RxD in 4 TxD out 5 RTS out 6 CTS in 7 n.c. 8 n.c RS485 This is an industry standard RS485 bus interface WAGO Connector Pin layout: 1.) not connected 2.) not connected 3.) Signal B (+) 4.) Signal A (-) 5.) Supply voltage (6-32 V) 6.) Supply and Signal Ground (GND) jump to TOC Page: 30

31 Cable are connected with the WAGO 734 series connectors. In most product configurations, those adapters are shipped with the box. Check the 'scope of delivery' list CAN BUS INTERFACE This is an industry standard CAN bus interface CAN configuration and default settings See paragraph 6.2. CAN Data logging example on an initial configuration and usage example. See paragraph Interfaces (1st) CAN and (2nd) CAN and onwards on how to configure the CAN interfaces. See paragraph CAN Storage Format Example Text (CSV) on the text storage format Signal Levels Voltage range on CAN-H / CAN-L: 4-16V Transceiver used: SN65HVD family by Texas Instruments. Other transceivers upon request D-Sub Connector ( M43014, C43014 ) Note the the D-Sub Interface is using the 2nd CAN interface. Connector Interface Pin Signal Direction D-Sub, 9 pol, male 2 nd CAN 1 n.c. (optional: VCC) Power 2 CAN-L Bus 3 GND Power & Signal 4 n.c. 5 n.c. 6 GND Power & Signal Page: 31 jump to TOC

32 7 CAN-H Bus 8 n.c. 9 VCC (6..32V) Power WAGO Connector ( M43324 / C43324 ) Connector Interface Pin Signal Direction WAGO A 1 st CAN 1 Ground (Signal) 2 CAN-L 1 st CAN Bus 3 CAN-H 1 st CAN Bus 4 Future Use (not connected) 5 VCC (6..32V) Power 6 GND Power & Signal WAGO B 2 nd CAN 1 Ground (Signal) 2 CAN-L 2 nd CAN Bus 3 CAN-H 2 nd CAN Bus 4 Future Use (not connected) 5 VCC (6..32V) Power 6 GND Power & Signal Cable are connected with the WAGO 734 series connectors. In most product configurations, those adapters are shipped with the box. Check the 'scope of delivery' list. jump to TOC Page: 32

33 Screw type connector (M43076, C43076 Connector Interface Pin Signal Direction Screw Type CAN 1 GND Power & Signal 2 VCC (6..32V) Power 3 n.c. 4 n.c. 5 n.c. 6 n.c. 7 CAN-H 2 nd CAN Bus 8 CAN-L 2 nd CAN Bus Page: 33 jump to TOC

34 13.5. ANALOG CURRENT LOOP (4..20 MA) INTERFACE The analog 20mA interface is a differential current input with an internal resistance of 49.9 Ohms. This allows to interface industrial standard 4 20mA sensors to the data logger. See general description: 9.1. Storing 4..20mA data WAGO Connector Connector Interface Pin Signal Direction WAGO A WAGO B 1 st & 2 nd 4..20mA 3 rd & 4 th 4..20mA 1 1 st ma (+) 2 1 st ma (-) 3 2 nd ma (+) 4 2 nd ma (-) 5 VCC (6..32V) Power 6 GND Power & Signal 1 3 rd ma (+) 2 3 rd ma (-) 3 4 th ma (+) 4 4 th ma (-) 5 VCC (6..32V) Power 6 GND Power & Signal jump to TOC Page: 34

35 Screw type connector Connector Interface Pin Signal Direction Screw Type 1 st & 2 nd 4..20mA 1 GND Power & Signal 2 VCC (6..32V) Power 3 1 st ma (-) 4 2 nd ma (+) 5 2 nd ma (-) 6 1 st ma (+) 7 Future Use (not connected) 8 Future Use (not connected) Electrical Characteristics To avoid sensor signal clipping, the voltage levels of analog channels must be kept within the range: negative Pin Voltage 0V positive Pin Voltage 3V referenced to GND Recommended settings Recommended settings to enable data logging for the current loop interface are: Menu Submenu Item Value Page: 35 jump to TOC

36 Device Configuration Global HW setting Interface (Analog) AD Converter Interfaces ADC Settings Sample Rate.. your choice.. Gain All channels to 1 Mode All differential Stream to Generic ADC Data Processing Analog data (generic) Storage format 4xCurrent(mA) NMEA Storage endpoint Generic file Add timestamp Data Endpoints USB Stick Create new file policy 1 st : Every Day 2 nd : off Measuring other currents is possible by changing the gain settings. To cover the full range from 0 to +/- 40mA, the gain needs to be set to 1 with the PC companion software. Recommended setting: Gain 1 Gain 1 Current Input Range 0 +/- 40 ma Gain 2 Current Input Range 0 +/- 20 ma Gain 4 Current Input Range 0 +/- 10 ma Gain 8 Current Input Range 0 +/- 5 ma Gain 16 Current Input Range 0 +/- 2.5 ma Gain 32 Current Input Range 0 +/ ma ANALOG 10V INTERFACE The analog 10V Interface is a differential voltage input with an input voltage range of +/- 10V (at gain 1). The input resistance is 1MOhm. Connector Interface Pin Signal Direction WAGO A 1 st & 2 nd 0..10V 1 1 st 0..10V 2 1 st 0..10V 3 2 nd 0..10V 4 2 nd 0..10V 5 VCC (6..32V) Power 6 GND Power & Signal jump to TOC Page: 36

37 WAGO B 3 rd & 4 th 0..10V 1 3 rd 0..10V 2 3 rd 0..10V 3 4 th 0..10V 4 4 th 0..10V 5 VCC (6..32V) Power 6 GND Power & Signal Electrical Characteristics To avoid sensor signal clipping, the voltage levels of analog channels must be kept within the range: negative Pin Voltage 0V positive Pin Voltage 15V referenced to GND ANALOG RESISTIVE SENSOR INPUT The Analog Resistive Sensor Input is an interface for directly connecting resistive Sensors to the Data Logger. A constant current source of 0.1mA is connected to the sensor lines in the data logger. The input range for resistive sensors is from 0 to 20kOhms (gain set to 1). To allow best accuracy, the gain setting needs to match the sensor resistance range. This allows to directly interface e.g. resistive temperature sensors like KTY81, Pt100, Pt1000 or resistive pressure sensors to the data logger. Gain 1 Resistance Input 0 20 kohms Gain 2 Resistance Input 0 10 kohms Gain 4 Resistance Input 0 50 kohms Gain 8 Resistance Input 0 2 kohms Gain 16 Resistance Input 0 1 kohms Gain 32 Resistance Input Ohms x Analog Board Interface ( M4AB24 ) WAGO (A) WAGO (B) Interface ma and Resistive Sensor 2x Resistive Sensor Page: 37 jump to TOC

38 Signal A m A A ma A3 Analo g resi stiv e A4 Analo g resi stiv e VCC V G N D A5 Analo g resi stiv e A6 Analo g resi stiv e A7 Analo g resi stiv e A8 Analo g resi stiv e VCC V G N D Direction IN IN IN IN IN IN IN IN For details for the 4..20mA interface see: 12.5 Analog Current loop (4..20 ma on page For details for the Resistive Sensor interface see: 12.6 Analog Resistive Sensor Input on page VCC and GND are the same across the two ports. Supply voltage is V DC. Pin layout: 1) First Sensor (Constant Current Output) 2) First Sensor (Return Line) 3) Second Sensor (Constant Current Output) 4) Second Sensor (Return Line) 5) Supply Voltage (6 32 V) 6) Supply Ground (GND) ANALOG 2V INTERFACE The analog 2V Interface is a differential voltage input with an input voltage range of +/- 2V. By changing the Gain settings, the voltage range can be set to lower values. Gain 1 Voltage Input Range +/- 2V Gain 2 Voltage Input Range +/- 1V Gain 4 Voltage Input Range +/- 0.5V Gain 8 Voltage Input Range +/- 0.25V Gain 16 Voltage Input Range +/- 125 mv Gain 32 Voltage Input Range +/ mv jump to TOC Page: 38

39 Electrical Characteristics To avoid sensor signal clipping, the voltage levels of analog channels must be kept within the range: negative Pin Voltage 0V positive Pin Voltage 3V referenced to GND Page: 39 jump to TOC

40 14. INTERNAL AND EXTERNAL SENSORS INTERNAL GPS RECEIVER Internal GPS option is available for some Avisaro 4.0 products. The GPS is usually connected to the 2nd RS232 port. To add GPS data to the log files, choose the following settings: jump to TOC Page: 40

41 Data Processing Serial data (generic): The data received looks similar to: 2019/01/11,13:58:59,557, $R1, $PUBX,00, , ,N, ,E, ,G3, /01/11,13:58:59,566, $R1, $GNZDA, ,11,01,2019,,*4D 2019/01/11,13:58:59,770, $R1, $PUBX,00, , ,N, ,E, ,G3, /01/11,13:58:59,963, $R1, $PUBX,00, , ,N, ,E, ,G3, /01/11,13:59:00,166, $R1, $PUBX,00, , ,N, ,E, ,G3, /01/11,13:59:00,369, $R1, $PUBX,00, , ,N, ,E, ,G3,... Page: 41 jump to TOC

42 jump to TOC Page: 42

43 15. FIRMWARE UPDATE There are three ways to update the firmware of the Avisaro 4.0 family: 1) Via USB Stick If the Avisaro 4.0 product has a USB Host port, a new firmware can be uploaded using a USB stick. See details below. 2) Via PC Companion software If the Avisaro 4.0 product is connected to a PC via USB cable, the firmware can be updated using the PC companion software. See details below. 3) Via Remote Update For selected products, a remote firmware update via Internet is provided. This feature is not available for off-the-shelf products. The latest firmware version can be found online: Page: 43 jump to TOC

44 16. APPENDIX UNDERSTANDING PRODUCT SERIAL NUMBERS This is to explain the product serial numbers. Not all combinations are possible. Function Series Interface 1 Interface 2 Connector Housing M = Logger 4 = 4.0 Family 0 = none Same numbering 1 = SubD 1 = raw PCB 4.0 W = WiFi 1 = RS232 as Interface 1, only 2 = WAGO 2 = raw PCB 2.0 C = Wifi + Logger 2 = RS485 if P than: 3 = RJ45 + WAGO 3 = 2.0 BOX E = Extension 3 = CAN 4 = RJ45 + Barrel 4 = 4.0 AZURE G = Mobile Data 4 = Ethernet 1 = IMU (intern 5 = RJ45 6 = CUBE / SILVER 7 = 2x ma 2 = GPS (intern) 7 = Screw Type 9 = 2x 0..10V 3 = UMTS-WiFi A = Internal AEB A = 4..20mA+Resist B = 2x Resistive C = 2x 0..2V P = I2C (intern) S = digital I/O Example: C41124 : Avisaro 2x RS232 Datalogger with WiFi interface in an Azure enclosure CAN STORAGE FORMAT EXAMPLE TEXT (CSV) See PC Companion setup to select format: paragraph Data Processing CAN data (generic) I.e. file name txt : Date, Time, Millisecond, CAN Bus Nr., CAN ID, Message length, Data 2018/11/02,15:06:27,480, $C2, 0fffffff, 8, 00, 00, 00, 00, 00, 00, 00, /11/02,15:06:28,512, $C2, 0fffffff, 8, 00, 00, 00, 00, 00, 00, 00, /11/02,15:06:29,387, $C2, , 6, 02, 03, 04, 05, 06, 07, 00, /11/02,15:06:31,096, $C1, 18ff0233, 8, 01, 02, 03, 04, 05, 06, 07, /11/02,15:06:31,840, $C1, 18ff0233, 8, 01, 02, 03, 04, 05, 06, 07, /11/02,15:06:32,048, $C1, 18ff0233, 8, 01, 02, 03, 04, 05, 06, 07, /11/02,15:06:32,216, $C2, 18ff0233, 8, 01, 02, 03, 04, 05, 06, 07, /11/02,15:06:32,407, $C2, 18ff0233, 8, 01, 02, 03, 04, 05, 06, 07, /11/02,15:06:33,129, $C2, 0fffffff, 8, 00, 00, 00, 00, 00, 00, 00, /11/02,15:06:33,348, $C2, , 1, 12, 00, 00, 00, 00, 00, 00, /11/02,15:06:33,449, $C2, 0fffffff, 8, 00, 00, 00, 00, 00, 00, 00, 00 jump to TOC Page: 44

45 2018/11/02,15:12:50,499, $C2, , 8, 00, 00, 00, 00, 00, 00, 00, /11/02,15:12:50,844, $C2, , 8, 00, 00, 00, 00, 00, 00, 00, /11/02,15:12:51,147, $C2, , 8, 00, 00, 00, 00, 00, 00, 00, /11/02,15:12:51,447, $C2, , 8, 00, 00, 00, 00, 00, 00, 00, /11/02,15:12:52,163, $C2, , 8, 00, 00, 00, 00, 00, 00, 00, /11/02,15:12:52,387, $C2, , 8, 00, 00, 00, 00, 00, 00, 00, /11/02,15:13:12,446, $C2, , 1, 12, 00, 00, 00, 00, 00, 00, /11/02,15:20:24,227, $C2, 18ff0233, 8, 01, 02, 03, 04, 05, 06, 07, /11/02,15:20:24,227, $C2, 18ff0233, 8, 01, 02, 03, 04, 05, 06, 07, /11/02,15:21:44,635, $C2, 18ff0233, 8, 01, 02, 03, 04, 05, 06, 07, /11/02,15:21:54,900, $C1, 18ff0233, 8, 01, 02, 03, 04, 05, 06, 07, /11/02,15:39:00,561, $C1, , 8, 00, 00, 00, 00, 00, 00, 00, /11/02,15:39:07,469, $C2, , 8, 00, 00, 00, 00, 00, 00, 00, /11/02,15:39:33,882, $C1, , 1, 12, 00, 00, 00, 00, 00, 00, /11/02,15:49:44,075, $C1, , 1, 12, 00, 00, 00, 00, 00, 00, 00 Lines are terminated with <cr><lf> CAN STORAGE FORMAT EXAMPLE VECTOR CANALYZER See PC Companion setup to select format: paragraph Data Processing CAN data (generic) I.e. file name asc : date 2018/11/02 16:12:33 base hex timestamps absolute no internal events logged // version Rx d Rx d Rx d Rx d Rx d Rx d Rx d Rx d Rx d Rx d Rx d Rx d Rx d Rx d Lines are terminated with <cr><lf> Page: 45 jump to TOC