Products
Technology
SMS solutions
PBX systems
Databases
Robotics
Building robot hardware
Building electronics
Building robot software
Introduction/Protocols
Architecture
How to develop a devhandler
Line protocol
DeviceHandlers
Oz433Mhz Transceiver
OzAnalogJoystickController
OzAnalogSensor
OzBatteryController
OzBuzzerController
OzButtonController
OzDCMotorControllerL298N
OzDHTController
OzDoorphoneController
OzEEPROMController
OzKeyboardController
OzGyroscopeSensor
OzIDManager
OzIRTransceiver
OzLCDController
OzNfcReader
OzOpticalGateController
OzRegisterManipulation
OzRF24Transceiver
OzRGBLEDController
OzRotaryController
OzServoController
OzStepCounter
OzStepperMotorMultiController
OzSwitchController
OzTemperatureController
OzTimer
OzUltrasonicSensor
Examples
Bootloader
Company


DeviceHandlers

System overview

On the microcontroller program modules are running, which operate different kind of devices. Every device has its own independent identification (Device ID). The program modul which controls the device is communicating through a serial port with the program which is developed in .NET. The program developed in .NET is running on the PC.

As multiple devices can be found on a microcontoller, but typically, only one serial port is used for the communication with .NET, then we have to include in all the messages within the communication which device is concerned. This is what we use for Device ID.


Figure 1 - Main concept

Basic concepts

EventA message which is sent by the microcontroller for .NET
CommandA message which is sent by .NET for the microcontroller
Command_respAn event which is sent by the micrcontroller for .NET. This is where it is ensured that the order is processed and the next order can follow

Communication sequence


Figure 2 - Main concept

Currently available device implementations

Copyright © 2000- - Ozeki Informatics Ltd. | info@ozeki.hu | Tel: +36 1 371 0150
Home > Technology > Robotics > Building robot software > Introduction/Protocols > DeviceHandlers
Page: 1557