[API] To develop specific commands for Talking Fiber configuration

ralcaide commented 5 years ago

To develop the specific commands for Talking Fiber configuration showed here: Sinapse API.

EXPLANATION

Config Listen State

Question Topic: INST_ID/TF/ACT/ID where ID are the last 6 digits of the IMEI Message: L3_TF_CONF_LISTEN_STATE;ENABLED;TL_START;TL_LISTEN;TL_N; where:

ENABLED is 0 or 1. Enable / Disable the listen state
TL_START is an hour with format HH:MM. If Listen State is enabled will start listen at this hour each day
TL_LISTEN is a number representing minutes from 1 to 60. It is the time the listen state will be active during each day
TL_N is a number representing number of tries to connect and the value could go from 1 to 10. Number of times the Quectel will try to connect. If not connect in these number of tries then continue with its normal behaviour

All these data should be saved in NVM and the FW will work following these values

Response Topic: INST_ID/TF/CONFIG Message: L3_TF_CONF_LISTEN_STATE_R;ID;RESULT; where result is 1 if OK or 0 of was a problem

Config Send Status State

Question Topic: INST_ID/TF/ACT/ID where ID are the last 6 digits of the IMEI Message: L3_TF_CONF_SEND_STATUS_STATE;PERIOD_SEND_STATUS;TS_LISTEN;TS_N; where:

PERIOD_SEND_STATUS: Number of minutes the status will be published
TS_LISTEN is a number representing minutes from 0 to 60 that the device will be in listen mode after publish the status
TS_N is a number representing number of tries to connect and the value could go from 1 to 10. Number of times the Quectel will try to connect. If not connect in these number of tries then continue with its normal behaviour

All these data should be saved in NVM and the FW will work following these values

Response Topic: INST_ID/TF/CONFIG Message: L3_TF_CONF_SEND_STATUS_STATE_R;ID;RESULT; where result is 1 if OK or 0 of was a problem

Config Sampling State (ALERT)

Question Topic: INST_ID/TF/ACT/ID where ID are the last 6 digits of the IMEI Message: L3_TF_CONF_SAMPLING_STATE;PERIOD_SAMPLING;TH_MIN;TH_MAX; where:

PERIOD_SAMPLING: Number of minutes the status will be published
TH_MIN: Low Threshold to generate alerts, if the measurement is under TH_MIN, then an alert should be published
TH_MAX: High Threshold to generate alerts, if the measurement is obove TH_MAX, then an alert should be published

All these data should be saved in NVM and the FW will work following these values

Response Topic: INST_ID/TF/CONFIG Message: L3_TF_CONF_SAMPLING_STATE_R;ID;RESULT; where result is 1 if OK or 0 of was a problem

ralcaide commented 5 years ago

L3_TF_CONF_LISTEN_STATE;ENABLED;TL_START;TL_LISTEN;TL_N; TESTED KO

Sent L3_TF_CONF_LISTEN_STATE;1;21:35;30;5; at 21:30. The message is processed correctly but then at 21:35 is not connected. It is not possible to act over the device as expected.

@vAnArhist : How is that working? Could you test and fix it?

L3_TF_CONF_SEND_STATUS_STATE;PERIOD_SEND_STATUS;TS_LISTEN;TS_N; TESTED KO

Sent L3_TF_CONF_SEND_STATUS_STATE;5;3;5; when the device was publishing its status each 30 minutes. The message is processed correctly but the device is not publishing each 5 minutes. It is still publishing each 30 minutes.

@vAnArhist : How is that working? Could you test and fix it?

We are not tested the alerts configuration but we suppose it will not work as expected. It seems the messages are processed and returns with 1 (OK) but the configuration is not applied.

We need these features working as expected.

ralcaide commented 5 years ago

@vAnArhist , could you provide an estimation about that? We should be able to reconfigure the device in runtime as soon as possible in order to cover the features requirements.

Sinapse-Energia / talking-fiber