When I keep running omega for hours and when I want to send sensor data to cloud after some time from Omega ( Azure Device client), it's not working for 1 or 2 data packets saying issues with connectivity and later it start working.
I want to keep my IOT edge ( connected to IOT hub) for while.
@crispyoz Thank you for your support and help very much appreciated . I see some thing wrong with my installation , I tried on brand new omega 2S and I am able to run the Node JS code and send data from Omega to Azure cloud. I am good now.
@crispyoz I shared results. Still not able to proceed. It seems I need to upgrade node js version. ?
@crispyoz : I get following error. I
@crispyoz I tried to run it from root folder, please go through below error.
then I try to run npm install, it has created Package.jason in root folder. I tried to run Device.js had same issues
I am able to install node using Opkg Install Node,
when I create sample program , simple hello world, it is working fine.
'use strict';
console.log("Hello world");
however when I run following code in Js,
// Copyright (c) Microsoft. All rights reserved.
// Licensed under the MIT license. See LICENSE file in the project root for full license information.
'use strict';
// Choose a protocol by uncommenting one of these transports.
const Protocol = require('azure-iot-device-mqtt').Mqtt;
// const Protocol = require('azure-iot-device-amqp').Amqp;
// const Protocol = require('azure-iot-device-http').Http;
// const Protocol = require('azure-iot-device-mqtt').MqttWs;
// const Protocol = require('azure-iot-device-amqp').AmqpWs;
const Client = require('azure-iot-device').Client;
const Message = require('azure-iot-device').Message;
// String containing Hostname, Device Id & Device Key in the following formats:
// "HostName=<iothub_host_name>;DeviceId=<device_id>;SharedAccessKey=<device_key>"
const deviceConnectionString = process.env.IOTHUB_DEVICE_CONNECTION_STRING;
let sendInterval;
function disconnectHandler () {
clearInterval(sendInterval);
sendInterval = null;
client.open().catch((err) => {
console.error(err.message);
});
}
// The AMQP and HTTP transports have the notion of completing, rejecting or abandoning the message.
// For example, this is only functional in AMQP and HTTP:
// client.complete(msg, printResultFor('completed'));
// If using MQTT calls to complete, reject, or abandon are no-ops.
// When completing a message, the service that sent the C2D message is notified that the message has been processed.
// When rejecting a message, the service that sent the C2D message is notified that the message won't be processed by the device. the method to use is client.reject(msg, callback).
// When abandoning the message, IoT Hub will immediately try to resend it. The method to use is client.abandon(msg, callback).
// MQTT is simpler: it accepts the message by default, and doesn't support rejecting or abandoning a message.
function messageHandler (msg) {
console.log('Id: ' + msg.messageId + ' Body: ' + msg.data);
client.complete(msg, printResultFor('completed'));
}
function generateMessage () {
const windSpeed = 10 + (Math.random() * 4); // range: [10, 14]
const temperature = 20 + (Math.random() * 10); // range: [20, 30]
const humidity = 60 + (Math.random() * 20); // range: [60, 80]
const data = JSON.stringify({ deviceId: 'myFirstDevice', windSpeed: windSpeed, temperature: temperature, humidity: humidity });
const message = new Message(data);
message.properties.add('temperatureAlert', (temperature > 28) ? 'true' : 'false');
return message;
}
function errorHandler (err) {
console.error(err.message);
}
function connectHandler () {
console.log('Client connected');
// Create a message and send it to the IoT Hub every two seconds
if (!sendInterval) {
sendInterval = setInterval(() => {
const message = generateMessage();
console.log('Sending message: ' + message.getData());
client.sendEvent(message, printResultFor('send'));
}, 2000);
}
}
// fromConnectionString must specify a transport constructor, coming from any transport package.
let client = Client.fromConnectionString(deviceConnectionString, Protocol);
client.on('connect', connectHandler);
client.on('error', errorHandler);
client.on('disconnect', disconnectHandler);
client.on('message', messageHandler);
client.open()
.catch(err => {
console.error('Could not connect: ' + err.message);
});
// Helper function to print results in the console
function printResultFor(op) {
return function printResult(err, res) {
if (err) console.log(op + ' error: ' + err.toString());
if (res) console.log(op + ' status: ' + res.constructor.name);
};
}
I am getting following error, can some one help here to resolve this issue ?
@crispyoz Thank you for your reply. Memory usage is as below
Over all memory usage should not be more than 50 MB, its constant at 35.7 PM as of now.
My build size is 15 MB
In my application I am continuously reading sensor data and some time call to read the RFID's and then send data to Azure IOT. Sensor and RFID are connected to my Omega using USB ports.
I have purchased OMEGA 2S+ SDK with EMMC 8 GB , I don't have SD card on development KIT. When I am looking into physical storage only few MB's are available on Omega 2S+.
My questions is how can I extend storage and use EMMC 8 GB storage ? Also my application is developed in to .net core 3.1. I will be able to install .net core 3.1 run time on Omega 2S+ ? if yes, i tried to refer link https://community.onion.io/topic/1945/cross-compile-mono-from-source-for-the-omega2-and-omega2
Or creating docker image from visual studio and deploy on Omega 2 S+ and OpenWRT support Docker is yes, any one done this in past ?
Help will be really appreciated.
I have .net core application on Raspberry PI, it is working fine. I would like to go for Omega 2S+ processor now, Can I run my existing application on Omega processor ? If yes, can some one help with steps ?