I am new to WSO2 and like to evaluate the product for a specific IoT use case involving Raspberry Pi.
I found this nice article with the IoT demo, but could need some help reproducing it:
http://wso2.com/library/articles/2014/09/demonstration-on-architecture-of-internet-of-things-an-analysis/
Github repository is here:
https://github.com/dulichan/iot-ref-arch/releases/tag/0.0.1
There are three components involved:
Message Broker
Complex Event Processor
Enterprise Mobility Manager (EMM)
Is there a more detailed description about how to setup the components?
I managed to run the rpi agent on raspberry and to run EMM on my server machine, but where to put the files in the folders "cep-resources" ?
Also I foud few information on how to enroll the raspberry in EMM, is this possible by default with the user token in EMM or do I have to make any adjustments?
You can use WSO2 IoT Server 1.0.0 Alpha which was released recently which has the necessary components packed OOB. You can download the pack from [1]. This release has a Raspberry pi sample [2] which uses DHT11 temperature sensor and a LED bulb which you can tryout. Also you can write your own device plugin by referring [3].
[1] https://github.com/wso2/product-iots/releases/tag/v1.0.0-alpha
[2] https://docs.wso2.com/display/IoTS100/Raspberry+Pi
[3] https://docs.wso2.com/display/IoTS100/Creating+a+New+Device+Type
Related
Can https://volttron.org/ be used as a 'protocol translator gateway' software which can take data from PLC over BACnet/Modbus and can forward it to Azure IoT hub?
Where can I get demo for Volttron? I am new to python and unable to understand the code present related to Volttron. Office hours videos present on Volttron sites are not indicating if Volttron is a choice for my scenario shown in the image.
Please guide/help. Thank you.
Yes, VOLTTRON can be configured to retrieve bacnet traffic. The picture you have drawn can be accomplished.
See
https://github.com/VOLTTRON/volttron
And
https://volttron.readthedocs.io/en/main/
For instructions on how to use the platform.
In the picture volttron could actually be in either the PLC Controller (assuming it has enough capabilities) or the protocol translator gateway or both. There is an mqtt facility in VOLTTRON to do the last step to the Azure IOT Hub as well, though it has not been tested with that interface.
We are currently trying to communicate with Edge devices using MQTT. We use the config topic for defining the algorithms to use, the version of software and so on.
We would like to use commands for sending "calculation results" back to the devices. We have to send it from the cloud towards the devices since multiple devices are working together on this.
This state is important for the device to visualise the correct state and therefor we would like to have QOS1 for these commands.
According to the documentation this should be possible but I can't find out how to do this.
We are using the API's for managing these config and commands.
I have two type of devices one support IoT JSON agent and another Ultralight Iot Agent. What approach is best should i used both IoT agent separately or there is something like IoT manager. What in future i have another device which support another IoT Agent like LoRaWan .
I have tried IoT manager but could not understand it is only for device provisioning or actual device data transfer also.
IoT Manager acts as a proxy for actual IOTAs, so depending on some parameters in the request (I don't remember exactly which ones, but they should be described in the IOTAs documentation) redirects the request to one or another IOTA agent.
But of course, you can implement this proxy using another piece of software (e.g. ngix with some king of URL-based or port-based redirection) if you want.
Is there a way to enable Raspberry Pi's internal pull-up resistors using Android Things?
EDIT: I filed a feature request -> https://code.google.com/p/android/issues/detail?id=233630
As of current release (DP2), there is no Peripheral I/O API to dynamically configure pull/down resistor on Android Things.
However has pointed in the release notes and the BCM2835 documentation, the Raspberry Pi 3 has internal pull-up (3.3V) resistor configured by default on the following pins, when configured as input with Gpio.setDirection:
BCM4
BCM5
BCM6
This is now available through the android things console:
First you should read this link for base knowlege.Pull-up resistors is hardware, it make uncertain voltage to 1 or 0 for pin!
I want to connect the PiCAN with my raspberry pi3 running windows IoT Core. I think I need a universal driver for the mcp2515 to work with the windows in Pi. I already tried using the instructions given in https://developer.microsoft.com/en-us/windows/iot/docs/driverdeployment to deploy the driver given in https://github.com/AustinWise/Mcp2515Can . But I got stuck in the instructions. I hope someone has already done this and maybe can help me with it? Did anyone successfully use this CAN board with Raspberry Pi (windows iot core)?
Thank you :)
Is a driver required in the first place?
Short answer is No.
Although a device driver is preferred, such work is not officially or community done yet.
The benefit you get from developing a device driver might include:
Native OS support for PiCAN board.
Create your create the custom IoT image, and deploy it to Microsoft store.
Possible performance improvements
others…
However, in order to develop an device driver, you need to follow the WDK framework. If you are comfortable with picking up new stuff, go ahead and try it out. You might need to refer to the linux source driver code for WDK driver developing.
If your purpose is to get the board working, you don’t need to get yourself into all these troubles.
In fact, you only need to get the SPI controller and GPIO controller, open the SPI device and initialize GPIO interrupt pin like Mcp2515Can does.
But, even after enabling the SPI, I couldn't receive anything on the
Raspberry Pi.
First, you can use Raspbian and turn on the CAN driver support to verify that you got all the wirings right. Here is the user guide you can reference.
If you can rule out the possibility of hardware failures, step into your C# code to troubleshoot the software.
Good luck.