I intend to use the IoT Hub to update firmware of my Edison device utilising its bi-directional capability although I am not sure of where to look for detailed instructions on how to do it. The only information I have found on the subject is HERE but doesn't go into detail on how exactly to do it, more a high level overview. Does anyone have any knowledge on how this is to be done or know any links that will help?
Thanks
The link you provided returns 404 for me right now; maybe that's temporary...
I work for Microsoft, on the Device Management SDK team for IoT Hub. The new Device Management capabilities we announced at Build last week should give you exactly what you need, but there isn't much info because the features aren't available to the public just yet.
For a preview, take a look at this video from Build where we demo'd firmware update on the Intel Edison. The device management segment starts at about 35 min, demo at 40 min.
To do firmware update using only what's available publicly today in IoT Hub, you'd probably start by sending a cloud-to-device message to your Edison. Of course, exactly how you go about downloading and updating the firmware after that is specific to your device and scenario.
Here is the link to the repo which allows you to update firmware remotely using the IoT Hub. Thanks MS!
https://github.com/Azure/azure-iot-sdks/tree/dmpreview
Related
I am trying to port https://github.com/Azure/azure-iot-sdk-c to VxWorks. I have created 2 PRs:
https://github.com/Azure/azure-iot-sdk-c/pull/2022
https://github.com/Azure/azure-c-shared-utility/pull/538
I have signed the CLA but don't know how to proceed.
I have referred the contribution guide: https://github.com/Azure/azure-iot-sdk-c/blob/master/.github/CONTRIBUTING.md.
But the section "Contributing Ports" is TBD.
My PRs seem stuck there. All CI checks are pending.
Could you please let me know what I should do next?
thank you for your PR! Getting the VxWorks RTOS ported to work with Azure IoT services seems to be a great idea. The only caveat here is choosing the right SDK to get this done: in your case you used the C SDK which can be too big for constrained devices.
The best SDK for constrained devices and porting a RTOS would be the Embedded C SDK which is smaller, non-allocating, and very flexible as it allows you to use whichever MQTT, TLS and Socket your target platform needs.
I'm looking at prototyping a couple of solutions using the MXChip AZ3166 that require a number of external devices like GPS, Display and Comms hardware.
Does anyone know what connectors can be used with the "Pluggable" MXChip AZ3166 IOT Devkit, or if there are any breakout boards available for it?
In Mxchip AZ3166, there is a edge connector on the board that is compatible with BBC Micro:bit accessories. So you could easily extend it with external devices.
More information of Micro:Bit could be find here: https://www.kitronik.co.uk/microbit/bbc-micro-bit-accessories.html
And you could check this example https://github.com/jimbobbennett/InternetConnectedFan on how to use Micro:Bit to connect to external devices.
I currently have a video chat app working on web(Flash) and android via Adobe AIR, it uses Adobe Media Server (RTMP) as backend for video streaming and shared objects, my question is, if there is another server or solution that provides many to many live video broadcast maybe using H.264 codec from android and iOS, have some sort of user list and room list stored in a database or similar, I want to move away from Adobe as it has many limitations on mobile devices.
Live video is crucial in 1 to many broadcasts that will have hundreds of viewers at the same time.
Thanks for reading!
Ulex.fr created an RTMP connector for Asterisk (the free PBX platform).
Used with the Asterisk Vonference application, it allows you to create conference rooms for 1 to many configuration, with audio and video. The only one limitation is the power of your server. You can plan a scalable architecure in order to broadcast one video to many (many could be unlimited). We developp a specific protocol to connect and manage the connection based on the telephony events. I think we already done a direct RTMP connection that skip this protocol too.
All the project done by ulex.fr is free, OpenSource and GPL.
Get the full project here : https://github.com/voximal/asterisk-rtmp
(a live demo is available)
We already develop an RTMP stack for android with video (using the camera), this allows you to create your own application without using AIR.
You can check Adobe Cirrus, it's still in the beta stage (actually IMHO Adobe forgot about it), but it works on web, desktop and mobile too. Check this Video Phone example, it can handle chat applications without a problem.
http://labs.adobe.com/technologies/cirrus/samples/
You could take a look at Red5 Media Server, which is an open source solution. There are other options like the Wowza's solutions on AWS, but they come a higher cost...
Ok as today, we have decided that we can manage the users,rooms and messages via Google Firebase Real Time Database, and the live video stream using ANT Media Server
Now I am working on the IBM MQA (Mobile Quality Assurance). But I want to get some informations from MQA Service such as device's information , session, bugs, .... The IBM have the rest API to support it ? Can anyone give some suggestion about this problem ?
Thank you.
We are working to improve the MQA filtering features however at this time we don't have a way to filter crashes by devices. We recently announced that MQA in Bluemix now supports integration with the following bug tracking systems: Jira, TFS, HP Quality Center, GitHub, FogBugz.
If you use one of these BTS's, its possible to use their sorting or filtering process, if any however unfortunately at this time there are no MQA APIs available.
I have done this when running Debian using gpsd. But when running Windows IoT preview...what is a way to get the NMEA sentences off an attached GPS (on the USB port). Is that kind of support around yet?
Currently this support is not yet available but it is being actively developed. Furthermore the Geolocator API is broken. Unfortunately I don't have an ETA for this but its coming.
Mark Radbourne (MSFT)