Related Manuals for Bosch IVAS 0273600075
Summary of Contents for Bosch IVAS 0273600075
- Page 1 IVAS Sensor Device (Ethernet) Part No 0273600075 Operating Instructions Version 0.5...
- Page 2 This preliminary operating instructions present the status of the specifications. It will be confirmed when validation has been completed with positive results. Product part number: 0273600075...
-
Page 3: Table Of Contents
Table of contents 1 Scope of delivery 2 General product description 2.1 Main functions and properties of the product 2.2 Intended use and environment 2.2.1 Installation situation 2.2.2 Security measures 2.2.3 Operating conditions 2.3 Key features 3 Safety and warning notes 4 Technical description 4.1 Working principle 4.2 Overview... - Page 4 9 Installation, handling and storage 9.1 Fixation 9.2 Connecting the module 9.2.1 Electrical connection 9.3 Handling 9.4 Storage 10 IVAS Ecosystem 10.1 Hardware Setup 10.1.1 Required Equipment for testing and data logging 10.2 Software Setup 10.3 Script Functionality 10.3.1 Script List 10.3.1.1 Network Configurator 10.3.1.2 Data Collector 10.3.1.3 Data Post Processor...
- Page 5 Table of figures Figure 1: Picture of the IVAS sensor device Figure 2: Front and back with labelling Figure 3: Main dimensions of the device Figure 4: Pin configuration IVAS-ETH referring to DIN EN 61076-2-109 Figure 5: Installation Figure 6: Ethernet CAT6A (10 Gbps), shielded with Plug straight M12 SPEEDCON Figure 7: Axis of low g and high g sensors Figure 8: Assembly surface Figure 9: Overview system setup...
-
Page 6: Scope Of Delivery
For process monitoring, this technique enables an integrated continuous quality control and gives the informa- tion to set the optimal process parameters. Other applications, uses or specifi cations must be imperatively evaluated and released by Bosch Connected Devices and Solutions (BCDS). -
Page 7: Intended Use And Environment
6,6 (2x) Figure 3: Main dimensions of the device 10 Mbits/sec, 100 Mbits/sec, 1000 Mbits/sec, Twisted Pair 1: TXD1+ 5: BID4+ 2: TXD 1- 6: BID4- 3: RXD2+ 7: BID3- 4: RXD2- 8: BID3+ Figure 4: Pin configuration IVAS-ETH referring to DIN EN 61076-2-109 2.2 Intended use and environment The IVAS-ETH is CE marked and is in conformity with the essential requirements of 2014/30/EU (EMC Directive) for the intended use conditions, environments, and installation conditions described in the following:... -
Page 8: Installation Situation
industrial, scientific, and/or medical devices (non-life sustaining) large inductive and capacitive loads with frequent switching high currents and high magnetic field strengths Machine tools as specified in EN 50370-1 and -2 This European Standard specifies the EMC limits of machine tools (with exception of electric discharge machines (EDM)) which are dedicated for industrial and similar applications, and using electricity with a voltage below 1000 V AC / 1500 V DC. -
Page 9: Security Measures
IVAS sends data to the originating host on the respective sensor ports (see chapter 5 for details). The IVAS-ETH with the current Firmware v0.1.x is not a series product and does not support Bosch standards for device security. -
Page 10: Safety And Warning Notes
3 Safety and warning notes A list of comprehensive notes and regulations for the safe use, handling, or maintenance of the product (e.g. transport, assembly, production process, design, installation notes, etc.), which must be observed by the customer, OEM, end custom- er, service technician, or other relevant persons or groups. -
Page 11: Overview
Single axis sensor Sampling rate: 62.5 KHz Range: +/- 96 g Low frequency sensor 3-axis sensor Sampling rate: 6.4 KHz Range: +/- 16 g Reference: https://www.bosch-connectivity.com/media/product_detail_ivas/ivas_datasheet.pdf Legend: Legend: accelerometer axis X, Y, Z: X, Y, Z: (low g sensor) X: accelerometer axis... -
Page 12: Mqtt Communication Overview
5.2 MQTT Communication Overview 5.2.1 MQTT Topics on which IVAS device publish data TIPIC DESCRIPTION FORMAT ivas/<device_id>/startup Startup message JSON ivas/<device_id>/sensor/hf High frequency sensor data format ivas/<device_id>/sensor/lf Low frequency sensor data format Table 4: MQTT topics I Example Usage User can subscribe and monitor incoming data from the sensors using the basic Mosquito tools: mosquito_sub -v -t „<topic>“... -
Page 13: Configuration
Example Startup message from the sensor is with the following payload format (JSON): „SelfTest“: „BMI280“:“Success“, „SMB470“:“Success“, „TMP112“:“Not performed“, „MQTT“:“Success“, „External flash“:“Success“ „TimeStamp“:[„1585841213“], „ResetCause“:“SOFTWARE_RESET“, „Version“: „FwVersion“:“v0.2.0_TestSpec“, „HwVersion“:“HW_R1“ 5.4 Configuration You can configure the following parameters in the IVAS application: Device Network configuration Sensor selection Note: For User convenience, the user is provided with python scripts that can easily change the overall device configuration. -
Page 14: Device Configuration
5.4.2 Device configuration Under Device Configuration we can: Switch between the static/dynamic IP for the device, Configure the device static IP settings, Configure MQTT broker IP settings, Configure SNTP server IP settings We can enable/disable the sensors for raw data streaming. The IVAS device always takes the client and server network configurations from NVM. -
Page 15: Sensor Configuration
5.4.4 Sensor Configuration ivas/<device_id>/sensor/config Sensor configuration topic allows enable/disable of specific sensor on the device “Enable”: “smb470” : <true/false>, “bmi280” : <true/false>, “temp” : <true/false>, Note: Streaming of Temperature data is not supported Responce: device/sensorConfig/<status>” <status> denotes the result of processing the command: parseFailure : Parsing of payload has failed configStoreSuccess : Configuration is successfully stored in NVM configStoreFailure : Storing the configuration in NVM has failed... -
Page 16: Jumping To Bootloader & Fota
Data format: BASE TIMESTAMP** SAMPLE 1 SAMPLE 2 ... SAMPLE 42 uint64* int16* int16* int16* int16 int16 int16 int16 int16 int16 8 bytes 2 bytes 2 bytes 2 bytes 2 bytes 2 bytes 2 bytes 2 bytes 2 bytes 2 bytes Table 8: IVAS payload –... -
Page 17: Bootloader
6 Bootloader 6.1 Release notes DATE VERSION CHANGELOG 31.1.2020 v0.2.1 Initial bootloader for Datastreamer PoC Table 9: IVAS Bootloader history 6.2 Preface IVAS bootloader consists of 2 stages : Stage-1 Bootloader Main Bootloader. Main bootloader functionality are, 1. Jumps to valid application if available 2. -
Page 18: Flash Programming
The IVAS Device needs access to the following file structure to be served from the server: DOWNLOAD FILE NAME FILE CONTENTS DESCRIPTION IvasUserConfig.txt User update request “Boot”: “AppUpdate” : true, “BootUpdate” : true, “BootConfig” : true IvasBootloaderConfig.txt { “http”: { “ip” : “192.168.178.100”, “port” : 8000 } } Bootloader Configuration IvasApplication.bin Application firmware... -
Page 19: Main Bootloader/Application Firmware Update
FILE DESCRIPTION AppUpdate IVAS downloads IvasApplication.bin BootUpdate IVAS downloads IvasBootloader.bin BootConfig IVAS downloads IvasBootloaderConfig.txt Table 11: Update process 6.6 Main Bootloader/Application Firmware update FILE SEQUENCE DETAIL Main Bootloader Download With BootUpdate flag true in IvasUserConfig.txt, IVAS Main Bootloader(IvasBoot- loader.bin) will be downloaded from the server Upon download failure, 3 download retry Verification After successful download, firmware and its signature (Key) will be verified... -
Page 20: Bootloader Example Timing
6.7 Bootloader example timing DETAILS TIME REMARKS Initialization time (until startup message post) DHCP wait time If DHCP is not successful, static IP will be assigned after timeout HTTP GET timeout 100s HTTP POST timeout 100s User config HTTP GET request timeout Occurrences - 1. -
Page 21: Device Log
6.9 Device log IVAS device log messages will be sent to HTTP server as POST message in JSON format with the following format: “{\”DEVICE MAC ID\”:\”POST message\”}” 6.10 Main Boot HTTP POST Message Information SCENARIO POST MESSAGE 1. Bootloader startup info, IVAS Device Mac ID and Bootloader Version {"$(DEVICE_MAC_ID)":"{\"$(DEVICE_MAC_ID)\":\"0.2.1\"}"} Reset Cause... -
Page 22: Application Download
6.10.2 Application Download AppUpdate or AppUpdateRetry or AppTesting flag set Download “{\”$(DEVICE_MAC_ID)\”:\”Application download in progress\”}” ”{\”$(DEVICE_MAC_ID)\”:\”Application download success\”}” “{\”$(DEVICE_MAC_ID)\”:\”Application download failed\”}” Verification “{\”$(DEVICE_MAC_ID)\”:\”Application verification success\”}” “{\”$(DEVICE_MAC_ID)\”:\”Application verification failed\”}” Swap “{\”$(DEVICE_MAC_ID)\”:\”Application swap in progress...\”}” Retry “{\”$(DEVICE_MAC_ID)\”:\”Firmware download and verification failed, retry again...\”}” “{\”$(DEVICE_MAC_ID)\”:\”Firmware download failed after 3 attempts. -
Page 23: Known Limitations
Retry “{\”$(DEVICE_MAC_ID)\”:\”Firmware download and verification failed, retry again...\”}” “{\”$(DEVICE_MAC_ID)\”:\”Firmware download failed after retries\”}” 7 Known Limitations 1. If the system resets in middle of download, it will not start again after reset. To download again, the user should request again through config file 2. -
Page 24: Figure 8: Assembly Surface
Note: The hole in the sensor is dedicated for mounting the sensor with a screw (no screw threads in the sensor housing) Assembly surface of 85 mm is fitting if you are using cables with 90°-socket only. STP files from the IVAS housing are available to download from the BCDS website. Assembly surface: Figure 8: Assembly surface DIMENSION... -
Page 25: Connecting The Module
9.2 Connecting the module 9.2.1 Electrical connection Connector M12: Pole: X-coded 8 poles M12 connector IEC 61076-2-109, According to IEEE 802.3 9.3 Handling The use of a high pressure cleaner or chemicals is not permitted. For cleaning, it is recommended to use a rag lightly humid- ified with water. -
Page 26: Software Setup
Figure 9: Overview system setup Note: The easiest way to power up your system is to use a POE-Injector. Therefore we recommend an injector e.g. PD-9001GC from Microchip with 30 W and 1 ETH-port: https://www.microchip.com/wwwproducts/en/PD-9001GC Figure 10: POE Injector, 1 port, 30W, IEEE 802.3at-compliant, indoor 10.2 Software Setup Step by step commands for Linux environment. -
Page 27: Script Functionality
Use the following confi guration for DHCP lease in dhcpd.conf subnet 192.168.178.0 netmask 255.255.255.0 {range 192.168.178.2 192.168.178.99; option routers 192.168.178.100; option subnet-mask 255.255.255.0; use-host-decl-names true;} Restart DHCP Service sudo service isc-dhcp-server restart sudo service isc-dhcp-server start sudo service isc-dhcp-server stop Ensure that your Linux Host device (Rhasperry Pi have static IP confi guration: sudo nano /etc/network/interfaces Add the following confi guration for your ethernet interface (Connected to the IVAS Sensor Network) -
Page 28: Data Collector
The script requires an argument. If mac is specified, the script will only update the specified device. If otherwise the –all argument is specified, it will update all sensors listed in the config.py. “--mac” Specify the mac addresses of the sensors to update “--all”... -
Page 29: Data Post Processor
“--mac” MAC addresses of the devices “--all” Use all MAC addresses listed in the configuration “--ip” The ip address of the broker “--port” The port of the broker “--httplog” File for the HTTP post request logs “--dir” The output directory “--ftype”... -
Page 30: Testing
11 Testing Testing is a key discipline to master product related risks. The following tests have been performed. Conformity with EMC Directive: Tests have been done under the requirements specified in harmonized standards listed in chapter 9: Conformity with PoE specifications: In order to demonstrate conformity with PoE (Power on the Ethernet) standard the following test has been performed: Isolation tests according EN 60950-1 Information technology equipment - Safety - Part 1: General requirements 12 Information on disposal and recycling... -
Page 31: Target Markets
13.2 Target markets EU: The IVAS-ETH is CE marked and authorized for operation and sales to end users in the European Union (the target market). China: The IVAS-ETH does not require certification for sales and operation in China (Source: TÜV Rheinland Apr.2019, no radio product, no product under CCC list). - Page 32 * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE * DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR * SERVICES;...
- Page 33 and the Program if, at the time the Contribution is added by the Contributor, such addition of the Contribution causes such combination to be covered by the Licensed Patents. The patent license shall not apply to any other combinations which include the Contribution.
- Page 34 Contributor must: a) promptly notify the Commercial Contributor in writing of such claim, and b) allow the Commercial Con- tributor to control, and cooperate with the Commercial Contributor in, the defense and any related settlement negotiations. The Indemnified Contributor may participate in any such claim at its own expense. For example, a Contributor might include the Program in a commercial product offering, Product X.
- Page 35 Exhibit A - Form of Secondary Licenses Notice “This Source Code may also be made available under the following Secondary Licenses when the conditions for such avail- ability set forth in the Eclipse Public License, v. 2.0 are satisfied: {name license(s), version(s), and exceptions or additional permissions here}.”...
- Page 36 cJSON Copyright (c) 2009-2017 Dave Gamble and cJSON contributors Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
- Page 37 Bosch Connected Devices and Solutions GmbH Ludwig-Erhard-Straße 2 Postfach 1342 72760 Reutlingen 72703 Reutlingen Germany Germany support@bosch-connectivity.com www.bosch-connectivity.com...