Node-RED je gafick箪 programovac鱈 jazyk s podtitulem A visual tool for wiring the Internet of Things. V pedn叩邸ce se pod鱈v叩me jak Node-RED nainstalovat, jak辿 je z叩kladn鱈 pou転it鱈 i slo転itj邸鱈 sc辿n叩e.
Pedn叩邸ka SUT, 17.11.2015 (http://sut.sh.cvut.cz/)
The webinar presentation covered flexibility and reporting capabilities for design failure mode and effects analysis (DFMEA) processes. It included a brief overview of Aras Innovator software and its interface, a demonstration of creating a DFMEA and collaboratively managing it, and information on how to ask questions. The presentation also discussed DFMEA methodology, provided a sample DFMEA spreadsheet with details, and showed reporting features in Aras Innovator for DFMEAs. Attendees were then invited to try out Aras Innovator and related resources themselves.
The document outlines an agenda for an FMEA training workshop. It discusses Failure Mode and Effects Analysis (FMEA), including its history, purpose, and process. FMEA is a methodology used to ensure potential problems are addressed in product and process development. The agenda includes explaining FMEA, its use as a design tool, the development process, management's role, team member responsibilities, and examples. It provides details on FMEA scope, functions, failure modes, effects, occurrence, detection, and criticality analysis. The workshop aims to train participants on effectively developing and applying FMEAs.
The document discusses problems with the current failure mode and effects analysis (FMEA) process at a company called RPL. It notes that before 2010 there was no formal FMEA conducted during new model introductions, leading to inconsistent quality. In 2012 an FMEA template was introduced based on a 5-scale system, but this was found to have issues with accurately capturing severity, occurrence, and detection ratings. Compared to industry standards, the company's FMEA process differs in using a 5-scale instead of a more common 1-10 scale and in not requiring a cross-functional team approach. The document investigates these facts to develop an improved FMEA template and methodology to meet the company's robust manufacturing
Making wearables with NodeMCU - FOSDEM 2017Etiene Dalcol
油
The document discusses creating wearable devices using NodeMCU, a firmware based on the ESP8266 chip, detailing its specifications, firmware building, and flashing processes. It includes code snippets for setting up Wi-Fi and serving web pages, along with various tips for animation and performance improvements. Additionally, it provides resources for further learning and inspiration for projects involving NodeMCU.
Innovative Approach to FMEA FacilitationGovind Ramu
油
This document discusses an innovative approach to facilitating failure mode and effects analysis (FMEA). It provides background on the history and traditional approach to FMEA, then outlines an improved approach using brainstorming software, cause-and-effect diagrams, and a focus on identifying root causes and prioritizing corrective actions. Key aspects of the new approach include utilizing cross-functional teams, observing processes first-hand, quantifying severity, occurrence, detection ratings, and regularly reassessing FMEA findings as improvements are made.
The document outlines a training agenda on Design Failure Mode and Effects Analysis (DFMEA) for Litens Automotive, emphasizing its significance in ensuring product safety and compliance with Canadian law. It discusses the consequences of not conducting DFMEA properly, including potential legal liabilities, and provides guidelines for its implementation, including critical dimensions and tolerances. Real-world examples, such as the GM ignition switch failure, highlight the importance of thorough and proactive design evaluations to prevent negligence claims.
The document discusses an FMEA training presented by Mccain.Koo from June 10-12, 2005. It introduces FMEA definitions, purposes, benefits and types. It discusses when and why FMEAs should be conducted, who is responsible for developing them, and when they should be updated. The training also covers FMEA scope, the design FMEA process, and establishing a design FMEA team.
The document provides information on potential failure mode and effects analysis (FMEA) for design (DFMEA) audits according to ISO TS 16949. It outlines the objectives of understanding how to audit DFMEAs, their link to other documentation, and how to complete a DFMEA. Key points covered include the purpose and benefits of FMEAs, the two types (design and process), and how to determine the risk priority number and ensure recommended actions are implemented. The document provides guidance on the specific steps to complete a DFMEA, including potential failure modes, effects, causes, controls, and corrective actions.
This document provides guidance on conducting a Design Failure Mode and Effects Analysis (DFMEA). It begins with defining the purpose of a FMEA and what it involves. It then discusses current DFMEA practices and concerns. The remainder of the document offers detailed instructions on performing a DFMEA, including how to construct a process flow diagram, interface matrix, evaluate potential failure modes and their effects/severity, occurrence, detection, and risk priority numbers. It provides examples and criteria for properly analyzing risk and prioritizing corrective actions. The overall summary is that the document aims to refine the approach to DFMEAs by outlining the full process and key considerations for effectively conducting a thorough design risk assessment.
The document outlines the concept of 'Design for Reliability' (DFR) as a systematic approach to enhance product robustness during development, emphasizing tools and methodologies to identify and mitigate reliability risks. It details the DFR roadmap, which includes reliability requirements, application stresses, failure modes, and verification processes, all aimed at improving customer satisfaction and product performance. Additionally, it highlights the importance of cross-functional collaboration and continuous monitoring post-launch to ensure compliance with reliability standards and improve future designs.
The document discusses the application of Design Failure Mode and Effects Analysis (DFMEA) to enhance prototype development and reduce design errors. It outlines key steps in DFMEA including function evaluation, identifying failure modes, severity assessment, and prioritizing risks to improve product reliability and performance. Additionally, it emphasizes the need for a strategic approach to design changes and testing to mitigate potential failures.
The document discusses using the ESP8266 microcontroller for home automation projects. It provides an overview of the ESP8266, including its specifications, firmware options like Arduino and NodeMCU, and communication protocols supported. Examples are given of using the ESP8266 to build an IoT home automation network with MQTT and Home Assistant or create devices like a solar-powered irrigation controller or quadcopter controller.
The document discusses failure mode and effects analysis (FMEA) of engine systems to identify potential failures, analyze their causes and effects, and determine corrective actions to improve reliability. It provides details on conducting a DFMEA, including assembling a cross-functional team, documenting functions and potential failure modes, analyzing severity, occurrence, and detection of failures, and calculating a risk priority number. The goal is to iteratively conduct the DFMEA, take corrective actions, and reduce the risk priority numbers to design more reliable engine components and systems.
The NodeMCU is an ESP8266 development board that contains a 32-bit RISC CPU, 64KB of instruction RAM, 96KB of data RAM, and external flash memory. It supports WiFi, GPIO pins, SPI, I2C, PWM and ADC interfaces. Official firmware includes Lua, Micropython, and Espruino scripting languages as well as support for Arduino IDE. It is inexpensive, functional, and has a large community supporting its use and development.
The document provides an overview of design and process Failure Mode and Effects Analysis (FMEA). It discusses FMEA as a systematic approach to prioritize risks associated with specific causes of failure. The document outlines the key steps in conducting a design FMEA, including defining potential failure modes and their effects, identifying potential causes, assigning severity, occurrence, and detection ratings, and calculating a risk priority number. It also provides a hypothetical example of a design FMEA for an email response process.
The document discusses failure mode and effects analysis (FMEA). It provides definitions and descriptions of different types of FMEAs, including design FMEA (DFMEA) which focuses on potential design failures, and process FMEA (PFMEA) which focuses on potential process failures and their causes. The document outlines the key steps in conducting a PFMEA, including developing a process flow diagram, identifying potential failure modes and their effects and causes, analyzing the risks associated with failures, and creating a process control plan to address potential failures.
The document discusses the 10 most common mistakes in Failure Mode and Effects Analysis (FMEA) and outlines quality objectives to achieve effective FMEAs. Key mistakes include failure to drive design improvements, inadequate team composition, and improper procedures, among others. By addressing these mistakes and focusing on defined quality objectives, practitioners can enhance the effectiveness and reliability of FMEA processes.
The document discusses the concept of 'world class' quality in manufacturing, emphasizing the importance of defect elimination rooted in preventive measures rather than detection. It introduces Failure Mode and Effects Analysis (FMEA) as a systematic approach to identifying risks, improving designs, and enabling better quality control through robust verification processes. The text outlines methods for evaluating product functions, potential failures, and the necessity of cross-functional collaboration to enhance customer satisfaction and reduce risks.
This document provides an overview of design failure mode and effects analysis (DFMEA). It begins with an introduction to DFMEA, including its purpose and importance in identifying potential failures early in the design process. It then covers key aspects of conducting a DFMEA such as identifying failure modes and their causes and effects. It also discusses how to analyze and prioritize potential failures using a risk priority number based on severity, occurrence, and detection ratings. The document provides examples of how these aspects are evaluated in a DFMEA. It concludes with emphasizing the role of DFMEA in guiding necessary design changes to improve reliability, safety and quality.
The document discusses the features and capabilities of various Wi-Fi modules, particularly the ESP8266 and NodeMCU. It highlights their advantages over older Arduino interfaces, including built-in Wi-Fi and increased processing power, making them suitable for IoT applications. The document also outlines a workshop agenda focused on programming the NodeMCU with practical projects involving sensors and web integration.
This document provides an introduction to programming the ESP8266 WiFi chip. It outlines ESP8266 basics, including an overview of the ESP-01 and ESP-12 models. It then demonstrates how to connect an ESP8266 to an Arduino and use the Blynk app and library to control an LED over WiFi. Wiring diagrams and code examples are provided to showcase setting up and programming the ESP8266 for basic WiFi functionality and Blynk integration.
This document provides an overview of Failure Mode and Effects Analysis (FMEA). It discusses that FMEA is a systematic group activity to recognize and evaluate potential failures, identify actions to address failures, and document findings. The document outlines the different types of FMEAs, including Design FMEA and Process FMEA. It also describes the typical steps to conduct a Process FMEA, including developing a process flow, identifying failure modes and their causes and effects, and estimating the risk priority number. The FMEA is presented as a team tool to prevent failures.
Making wearables with NodeMCU - FOSDEM 2017Etiene Dalcol
油
The document discusses creating wearable devices using NodeMCU, a firmware based on the ESP8266 chip, detailing its specifications, firmware building, and flashing processes. It includes code snippets for setting up Wi-Fi and serving web pages, along with various tips for animation and performance improvements. Additionally, it provides resources for further learning and inspiration for projects involving NodeMCU.
Innovative Approach to FMEA FacilitationGovind Ramu
油
This document discusses an innovative approach to facilitating failure mode and effects analysis (FMEA). It provides background on the history and traditional approach to FMEA, then outlines an improved approach using brainstorming software, cause-and-effect diagrams, and a focus on identifying root causes and prioritizing corrective actions. Key aspects of the new approach include utilizing cross-functional teams, observing processes first-hand, quantifying severity, occurrence, detection ratings, and regularly reassessing FMEA findings as improvements are made.
The document outlines a training agenda on Design Failure Mode and Effects Analysis (DFMEA) for Litens Automotive, emphasizing its significance in ensuring product safety and compliance with Canadian law. It discusses the consequences of not conducting DFMEA properly, including potential legal liabilities, and provides guidelines for its implementation, including critical dimensions and tolerances. Real-world examples, such as the GM ignition switch failure, highlight the importance of thorough and proactive design evaluations to prevent negligence claims.
The document discusses an FMEA training presented by Mccain.Koo from June 10-12, 2005. It introduces FMEA definitions, purposes, benefits and types. It discusses when and why FMEAs should be conducted, who is responsible for developing them, and when they should be updated. The training also covers FMEA scope, the design FMEA process, and establishing a design FMEA team.
The document provides information on potential failure mode and effects analysis (FMEA) for design (DFMEA) audits according to ISO TS 16949. It outlines the objectives of understanding how to audit DFMEAs, their link to other documentation, and how to complete a DFMEA. Key points covered include the purpose and benefits of FMEAs, the two types (design and process), and how to determine the risk priority number and ensure recommended actions are implemented. The document provides guidance on the specific steps to complete a DFMEA, including potential failure modes, effects, causes, controls, and corrective actions.
This document provides guidance on conducting a Design Failure Mode and Effects Analysis (DFMEA). It begins with defining the purpose of a FMEA and what it involves. It then discusses current DFMEA practices and concerns. The remainder of the document offers detailed instructions on performing a DFMEA, including how to construct a process flow diagram, interface matrix, evaluate potential failure modes and their effects/severity, occurrence, detection, and risk priority numbers. It provides examples and criteria for properly analyzing risk and prioritizing corrective actions. The overall summary is that the document aims to refine the approach to DFMEAs by outlining the full process and key considerations for effectively conducting a thorough design risk assessment.
The document outlines the concept of 'Design for Reliability' (DFR) as a systematic approach to enhance product robustness during development, emphasizing tools and methodologies to identify and mitigate reliability risks. It details the DFR roadmap, which includes reliability requirements, application stresses, failure modes, and verification processes, all aimed at improving customer satisfaction and product performance. Additionally, it highlights the importance of cross-functional collaboration and continuous monitoring post-launch to ensure compliance with reliability standards and improve future designs.
The document discusses the application of Design Failure Mode and Effects Analysis (DFMEA) to enhance prototype development and reduce design errors. It outlines key steps in DFMEA including function evaluation, identifying failure modes, severity assessment, and prioritizing risks to improve product reliability and performance. Additionally, it emphasizes the need for a strategic approach to design changes and testing to mitigate potential failures.
The document discusses using the ESP8266 microcontroller for home automation projects. It provides an overview of the ESP8266, including its specifications, firmware options like Arduino and NodeMCU, and communication protocols supported. Examples are given of using the ESP8266 to build an IoT home automation network with MQTT and Home Assistant or create devices like a solar-powered irrigation controller or quadcopter controller.
The document discusses failure mode and effects analysis (FMEA) of engine systems to identify potential failures, analyze their causes and effects, and determine corrective actions to improve reliability. It provides details on conducting a DFMEA, including assembling a cross-functional team, documenting functions and potential failure modes, analyzing severity, occurrence, and detection of failures, and calculating a risk priority number. The goal is to iteratively conduct the DFMEA, take corrective actions, and reduce the risk priority numbers to design more reliable engine components and systems.
The NodeMCU is an ESP8266 development board that contains a 32-bit RISC CPU, 64KB of instruction RAM, 96KB of data RAM, and external flash memory. It supports WiFi, GPIO pins, SPI, I2C, PWM and ADC interfaces. Official firmware includes Lua, Micropython, and Espruino scripting languages as well as support for Arduino IDE. It is inexpensive, functional, and has a large community supporting its use and development.
The document provides an overview of design and process Failure Mode and Effects Analysis (FMEA). It discusses FMEA as a systematic approach to prioritize risks associated with specific causes of failure. The document outlines the key steps in conducting a design FMEA, including defining potential failure modes and their effects, identifying potential causes, assigning severity, occurrence, and detection ratings, and calculating a risk priority number. It also provides a hypothetical example of a design FMEA for an email response process.
The document discusses failure mode and effects analysis (FMEA). It provides definitions and descriptions of different types of FMEAs, including design FMEA (DFMEA) which focuses on potential design failures, and process FMEA (PFMEA) which focuses on potential process failures and their causes. The document outlines the key steps in conducting a PFMEA, including developing a process flow diagram, identifying potential failure modes and their effects and causes, analyzing the risks associated with failures, and creating a process control plan to address potential failures.
The document discusses the 10 most common mistakes in Failure Mode and Effects Analysis (FMEA) and outlines quality objectives to achieve effective FMEAs. Key mistakes include failure to drive design improvements, inadequate team composition, and improper procedures, among others. By addressing these mistakes and focusing on defined quality objectives, practitioners can enhance the effectiveness and reliability of FMEA processes.
The document discusses the concept of 'world class' quality in manufacturing, emphasizing the importance of defect elimination rooted in preventive measures rather than detection. It introduces Failure Mode and Effects Analysis (FMEA) as a systematic approach to identifying risks, improving designs, and enabling better quality control through robust verification processes. The text outlines methods for evaluating product functions, potential failures, and the necessity of cross-functional collaboration to enhance customer satisfaction and reduce risks.
This document provides an overview of design failure mode and effects analysis (DFMEA). It begins with an introduction to DFMEA, including its purpose and importance in identifying potential failures early in the design process. It then covers key aspects of conducting a DFMEA such as identifying failure modes and their causes and effects. It also discusses how to analyze and prioritize potential failures using a risk priority number based on severity, occurrence, and detection ratings. The document provides examples of how these aspects are evaluated in a DFMEA. It concludes with emphasizing the role of DFMEA in guiding necessary design changes to improve reliability, safety and quality.
The document discusses the features and capabilities of various Wi-Fi modules, particularly the ESP8266 and NodeMCU. It highlights their advantages over older Arduino interfaces, including built-in Wi-Fi and increased processing power, making them suitable for IoT applications. The document also outlines a workshop agenda focused on programming the NodeMCU with practical projects involving sensors and web integration.
This document provides an introduction to programming the ESP8266 WiFi chip. It outlines ESP8266 basics, including an overview of the ESP-01 and ESP-12 models. It then demonstrates how to connect an ESP8266 to an Arduino and use the Blynk app and library to control an LED over WiFi. Wiring diagrams and code examples are provided to showcase setting up and programming the ESP8266 for basic WiFi functionality and Blynk integration.
This document provides an overview of Failure Mode and Effects Analysis (FMEA). It discusses that FMEA is a systematic group activity to recognize and evaluate potential failures, identify actions to address failures, and document findings. The document outlines the different types of FMEAs, including Design FMEA and Process FMEA. It also describes the typical steps to conduct a Process FMEA, including developing a process flow, identifying failure modes and their causes and effects, and estimating the risk priority number. The FMEA is presented as a team tool to prevent failures.
eMan Dev Meetup: Postavte si chytrou dom叩cnost (2.8.2016, Hradec Kr叩lov辿)eMan s.r.o.
油
https://www.facebook.com/events/1047417035338252/
Pojmy internet vc鱈 (Internet of Things, IoT), smart home, smart car a spousty dal邸鱈ch smart-nco n叩s obklopuj鱈 na ka転d辿m kroku. Pojte s n叩mi d叩t pr叩zdn箪m a trochu zprofanovan箪m zakl鱈nadl哲m dne邸n鱈 doby konkr辿tn鱈 obsah.
O EM TO BUDE
Je mo転n辿 si sv辿pomoc鱈 postavit chytrou dom叩cnost? S vyu転it鱈m technologi鱈, jako jsou Arduino, ESP8266, Raspberry Pi nebo Apple Watch, to jde docela jednodu邸e
Chceme rozsvcovat svtla mobilem?
Chceme otev鱈rat gar叩転 mobilem?
Chceme m鱈t r叩no hotov辿 kafe, kdy転 vstaneme z postele?
Chceme zatopit v pokoji pro hosty, kdy転 se dozv鱈me, 転e tch箪n neekan doraz鱈 na n叩vstvu?
Uk叩転eme si jak na to. Vyu転ijeme Arduino, RabbitMQ s MQTT pluginem, iPhone, Apple Watch, web a dal邸鱈 technologie. Pedvedeme si, jak lze jednodu邸e propojit Arduino s jeho senzory sn鱈maj鱈c鱈mi teplotu, vlhkost a adu dal邸鱈ch parametr哲 se serverem, kter箪 bude data zobrazovat na iPhonu, Apple Watch a webu. Meze fantazii se nekladou, tak転e vyzkou邸et si m哲転eme t辿m cokoli, co v dan辿m ase zvl叩dneme:)
CO JE EMAN DEV MEETUP
eMan zahajuje seri叩l setk叩n鱈 v箪voj叩哲 s n叩zvem eMan Dev Meetup. Na akc鱈ch se budeme bavit o nejnovj邸鱈ch technologi鱈ch, jejich praktick辿m vyu転it鱈 a k坦dov叩n鱈 softwaru pro n. Br箪le pro virtu叩ln鱈 realitu, chytr辿 hodinky, auta, domy, n叩ramky a nejr哲znj邸鱈 krabiky spojen辿 se svtem internetu vc鱈. A samozejm v邸udyp鱈tomn辿 smartphony.
KDE
Akce se uskuten鱈 ve zbrusu nov箪ch prostor叩ch na邸鱈 kralov辿hradeck辿 poboky na adrese: eMan s.r.o., imkova 1224/2B, Hradec Kr叩lov辿 (mapa: https://mapy.cz/s/sk3k).
ORIENTAN ASOV PLN AKCE
16:30 - 17:00 P鱈chod + oberstven鱈
17:00 - 17:20 Pedstaven鱈 eManu
17:30 - 19:00 Arduino a dal邸鱈 hardware - pedstaven鱈, k坦dn鱈, propojen鱈 se serverem, komunikace se smartphonem
19:00 - 20:00? Voln叩 diskuse a beerparty
KDO ZA AKC STOJ
Akci po叩d叩 pedn鱈 esk辿 v箪voj叩sk辿 studio eMan (www.eman.cz). esk箪m i zahranin鱈m z叩kazn鱈k哲m dod叩v叩me pedev邸鱈m mobiln鱈 aplikace a webov叩 e邸en鱈. Vyv鱈j鱈me aplikace pro celou 邸k叩lu za鱈zen鱈, mezi kter箪mi vedle smartphon哲 a tablet哲 nechyb鱈 br箪le pro virtu叩ln鱈/roz邸鱈enou realitu, hodinky, chytr叩 auta nebo nejr哲znj邸鱈 za鱈zen鱈 pipojen箪ch k internetu (IoT). Mezi na邸e z叩kazn鱈ky pat鱈 nap鱈klad koda Auto, O2, Honeywell, Jablotron, Edenred, UNIQA a dal邸鱈. Vedle Prahy, kde m叩 eMan s鱈dlo a hlavn鱈 kancel叩e, p哲sob鱈me tak辿 v Plzni a Hradci Kr叩lov辿, kde jsme ned叩vno oteveli nov辿 poboky (foto hradeck辿 poboky zde: https://goo.gl/VszYdH). N叩邸 t箪m v souasn辿 dob tvo鱈 65 lid鱈.
Od roku 2016 je eMan sou叩st鱈 JABLOTRON GROUP (http://www.jablotrongroup.com/).
IoT - m箪ty, povry, co to je, co to nen鱈 a co je nutn辿 vdt d鱈v, ne転 v叩s napadne, 転e byste se do tohoto oboru pustili. K tomu p叩r tip哲 na HW platformy, na software a na komunikan鱈 kan叩ly.
Pedn叩邸ka o tom, jak n叩m na Strahov dl叩 vr叩tn辿 Debian, JavaScript a asistuje jim u toho Ruby on Rails a PostgreSQL. Zkr叩tka o tom jak navrhnout RFID p鱈stupov箪 syst辿m do z叩jmov箪ch m鱈stnost鱈 v are叩lu, kde 転ije 4000 lid鱈.
Pedn叩邸ka na konferenci InstallFest 2014
Pedn叩邸ka z konference Softecon 2016. Hod鱈 se je邸t dneska k nemu program叩torsk辿 znalosti z osmibitov辿 辿ry? Budou fungovat star辿 osvden辿 triky pi psan鱈 bankovn鱈ch aplikac鱈 v Jav? A co pi psan鱈 obslu転n辿ho softwaru pro IoT? Plus kr叩tk叩 exkurze do historie, kter叩 ukazuje, 転e osmibity je邸t nejsou mrtv辿 a ani jenb tak nebudou.
13. ESP8266
Software
NodeMCU eLua
NodeLua (+ NodeLua Web IDE)
ESP8266 BASIC
MicroPython
Espruino (JavaScript)
Arduino esp8266 (GitHub)
Espressif Systems
AT prikazy
OTA update
802.11 (b +20dBm) /g/n, TCP/
IP stack, 2.4GHz, support
WPA/WPA2
STA/AP/STA+AP
32-bit MCU
Deep sleep power < 10uA
Wake up and transmit packets
in < 2ms
PWM, GPIO, UART, I2C, ...
EEPROM !!!
25. Use case
ESP8266 PCB + 3D print, DHT22 shield, OLED shield - LDR -
DS18B20 - dualbase, smokeTester, PIR senzor - buzzer, rellay
26. Use case - Turris Omnia
Open-source, 1.6Ghz 2core, 2GB RAM, 8GB 鍖ash, 5 x Gbit LAN,
1 x Gbit WAN, 2 x USB 3.0, Mini PCI Express, mSATA,
Wi-Fi 802.11 a/c/b/g/n, GPIO, OpenVrt, AutoUpdater, HoneyPot,
programmable RGB, Cryptochip
27. LXC container - Elasticsearch
Turris Omnia hosti LXC konteiner s Elasticsearch a jako persistentni
uloziste se pouziva dodatecne pridany 120GB mSata disk
60. Teplotni senzor
Zadani - postavte teplotni senzor z dostupnych soucastek,
ktery
se pripoji k Wi-Fi a nastaveni si ulozi
nastavi limit mereni na 30000ms a nastaveni ulozi
zmeri teplotu
blika LED diodou po 200ms
1x start zarizeni
2x uspesne pripojeno k Wi-Fi
3x neuspesne pripojeno k Wi-Fi
4x nepodarilo se zjistit cas ze site
blika LED diodou po 50ms
1x namerena hodnota byla odeslana do Elasticsearch
2x namerenou hodnotu se nezdarilo odeslat
Zmeri hodnotu osvetleni
Na OLED displeji vypise
IP adresu pro pripojeni
Noti鍖kaci o startu zarizeni
Noti鍖kaci o (ne) uspesnem nahrani kon鍖gurace
Namerenou teplotu
Informaci o neuspesnem odeslani namerenych
hodnot do Elasticserach
Informaci o neuspesnem zjisteni casu z NTP
Zjisti dostupnost Elasticsearch
Odesle namerenou hodnotu do Elasticsearch a
zvaliduje odpoved
U zarizeni by melo jit zmenit URI Elasticsearch a
interval mereni
63. Prakticke cviceni - WemosD1 mini
step1: Serial link example
step2: OLED example
step3: LED example
step4: LDR example
step5: LDR and LED example
step6: LDR & OLED & LED (bug)
step7: dallas example
step8: dallas and led example
step9: dallas & led & oled
step10: wi鍖-manager example
https://github.com/rdpanek/arduino/commits/hackathon
step11: wi鍖-manager & LED status example
step12: wi鍖-manager & LED status & OLED RSSI
& IP example
step13: wi鍖-manager & OLED & Dallas & IF
Statement (bug)
step14: Dallas & OLED and custom font
step15: SPIFFS & ArduinoJSON example
step16: wi鍖-manager & NTP example
step17: wi鍖-manager & web-server example
step18: wi鍖-manager ang GET request example
71. Pajeni
Vyzkousime si sestaveni celeho zarizeni a napajime
OLED display
Zarizeni je pripraveno na oziveni. Muzeme nahrat
prvni kod z Arduino IDE
72. Arduino IDE
https://www.arduino.cc/download_handler.php
Nastaveni Arduino IDE
Vyber desky
Pridani podpory pro desky s ESP8266
Soubor > Vlastnosti > Spravce dalsich desek URL
http://arduino.esp8266.com/stable/package_esp8266com_index.json
Nastroje > Vyvojovych desek > Manazer Desek > ESP > Instalace
73. Pripojeni zarizeni
Po pripojeni zarizeni k pocitaci bude
zarizeni reprezentovano dalsim portem
- po pripojeni zarizeni blikne modrou diodou
- Upload Speed: 115200
- po odpojeni zarizeni a znovu zapojeni -
zkontrolovat nastaveny PORT a zvolenou
Vyvojovou desku
81. Prakticke cviceni - step3: LED example
Podle barevneho oznaceni rezisotru vybereme ten spravny a podle pinu v kodu
jej napajime na dany pin do protoboardu
82. Prakticke cviceni - step3: LED example
Pripajime rezistor, stejne tak LED diodu
102. Prakticke cviceni - step8: dallas and led example
Pokud teplota dosahne 30 C, rozsviti se LED dioda, pokud teplota klesne pod 30
C, LED dioda zhasne