|
Changing push time parameters on Java based Azure connection - Printable Version +- Ewon Technical Forum (https://techforum.ewon.biz) +-- Forum: Development (https://techforum.ewon.biz/forum-50.html) +--- Forum: Java (https://techforum.ewon.biz/forum-53.html) +--- Thread: Changing push time parameters on Java based Azure connection (/thread-1187.html) |
Changing push time parameters on Java based Azure connection - rnicola - 24-02-2020 Hello, Absolute new guy here again, I am using the Java MQTT to Azure program on an Ewon Flexy 205 and need to understand these parameters better. When adding these configurations: deviceid:Flexy205 iothubname:FlexthinkAzureIOTHub fullpushtime:10 changepushtime:2 taggroups:A certificatetoken:000000 mqttlog:1 What do the ""fullpushtime" and "changepushtime" parameters stand for? What are they controlling? If the customer states that they want "data collected every second but only sent to Azure every 15 minutes" can that be controlled with this? Thank you! RE: Changing push time parameters on Java based Azure connection - tedsch - 27-02-2020 What do the ""fullpushtime" and "changepushtime" parameters stand for? What are they controlling? If the customer states that they want "data collected every second but only sent to Azure every 15 minutes" can that be controlled with this? Fullpushtime refers to the time between when every tag value will be uploaded. Every 10 seconds the current value from all the tags will be uploaded. changepushtime refers to the time between and tag value change uploads. So in the example you posted every 2 seconds any tag that has changed a value in the last 2 seconds will be uploaded. RE: Changing push time parameters on Java based Azure connection - simon - 03-03-2020 Hi, Ted is fully right. If they want to collect (and record) data every sec and send these data every 15 min, then it means the Java app must send the Historical logging to azure, which is not the case. This Java app is only sending the Tag live values to Azure. Simon |