How do I get multiple different mock barometers?
-
This wait() can also help to avoid packet losses due to insufficient power supply when using nRF24.
@rejoe2 said in How do I get multiple different mock barometers?:
This wait() can also help to avoid packet losses due to insufficient power supply when using nRF24.
You mean it needs extra time for the auxiliary cap to recharge? If so, surely we can find a better way to power the radio module that doesn't require taking a breather between packets....
I don't remember how it works with the nRF24L01, but on the RFM69, there's only one buffer for both sending and receiving, so you have to empty the receive buffer before you either send or receive another packet.
-
@rejoe2 said in How do I get multiple different mock barometers?:
This wait() can also help to avoid packet losses due to insufficient power supply when using nRF24.
You mean it needs extra time for the auxiliary cap to recharge? If so, surely we can find a better way to power the radio module that doesn't require taking a breather between packets....
I don't remember how it works with the nRF24L01, but on the RFM69, there's only one buffer for both sending and receiving, so you have to empty the receive buffer before you either send or receive another packet.
-
@NeverDie a discussion on that topic is underway in https://github.com/mysensors/MySensors/issues/892
@mfalkvidd
In that case the nRF52832 should be faster at emptying the buffer, since it doesn't have to rely on the slower SPI bus. And from what I gather, it can also do DMA's, which could speed things up even further. -
@mfalkvidd
In that case the nRF52832 should be faster at emptying the buffer, since it doesn't have to rely on the slower SPI bus. And from what I gather, it can also do DMA's, which could speed things up even further. -
@NeverDie for a node I think the bottleneck is the speed of the air transfer. Sending a message takes about 1ms at the default setting of 250kbps. But a busy gateway might benefit from the higher processing speeds on nRF52832.
@mfalkvidd said in How do I get multiple different mock barometers?:
@NeverDie for a node I think the bottleneck is the speed of the air transfer. Sending a message takes about 1ms at the default setting of 250kbps. But a busy gateway might benefit from the higher processing speeds on nRF52832.
Does it default to 250kbps to compensate for the range problems that the nRF24L01 has? I'm planning to bump mine up to 2mbps if at all possible. That might save appreciably on battery life.
-
I suppose the
wait(long_wait)isn't so bad a power drain if it's actually sleeping rather than busy-waiting for 500ms.
-
Here is a little sketch that compiles on the NRF5.
// Enable debug prints to serial monitor //#define MY_DEBUG // Enable and select radio type attached #define MY_RADIO_NRF5_ESB /** @def MY_NRF5_ESB_PA_LEVEL @brief Default nRF5 PA level. Override in sketch if needed. - NRF5_PA_MIN = -40dBm - NRF5_PA_LOW = -16dBm - NRF5_PA_HIGH = 0dBm - NRF5_PA_MAX = 4dBm */ #define MY_NRF5_ESB_PA_LEVEL (NRF5_PA_MAX) #define MY_NRF5_ESB_CHANNEL (76) #define MY_NRF5_ESB_MODE (NRF5_250KBPS) #define MY_NODE_ID 10 #define VOLTAGE 0 #include <MySensors.h> float vcc = (hwCPUVoltage() / 1000.0); MyMessage VoltageMsg(VOLTAGE, V_VOLTAGE); void presentation() { sendSketchInfo("General sensor", "1.0"); present(VOLTAGE, S_MULTIMETER); } void setup() { // Serial.begin(115200); // while (!Serial) ; // wait for Arduino Serial Monitor } void loop() { send(VoltageMsg.set(vcc, 3)); // Serial.print(F("Voltage = ")); // Serial.print(vcc, 3); // Serial.println(F("v")); sleep(60000); }@rmtucker said in How do I get multiple different mock barometers?:
#define MY_NRF5_ESB_PA_LEVEL (NRF5_PA_MAX)
#define MY_NRF5_ESB_CHANNEL (76)
#define MY_NRF5_ESB_MODE (NRF5_250KBPS)
Just now noticing that your definitions:
#define MY_NRF5_ESB_PA_LEVEL (NRF5_PA_MAX) #define MY_NRF5_ESB_CHANNEL (76) #define MY_NRF5_ESB_MODE (NRF5_250KBPS)can also be set in myconfig.h.
Strangely, myconfig.h defaults to max Tx power on the nrf52, but not max Tx power on the nrf24. Not sure why, especially since, if anything, the nRF24 needs it more.
So, I just now changed myconfig.h to put everything at max Tx power and 2mbps ota datarate. A lot of the nrf24 fake chips don't even run at 250kbps.
-
@rmtucker said in How do I get multiple different mock barometers?:
#define MY_NRF5_ESB_PA_LEVEL (NRF5_PA_MAX)
#define MY_NRF5_ESB_CHANNEL (76)
#define MY_NRF5_ESB_MODE (NRF5_250KBPS)
Just now noticing that your definitions:
#define MY_NRF5_ESB_PA_LEVEL (NRF5_PA_MAX) #define MY_NRF5_ESB_CHANNEL (76) #define MY_NRF5_ESB_MODE (NRF5_250KBPS)can also be set in myconfig.h.
Strangely, myconfig.h defaults to max Tx power on the nrf52, but not max Tx power on the nrf24. Not sure why, especially since, if anything, the nRF24 needs it more.
So, I just now changed myconfig.h to put everything at max Tx power and 2mbps ota datarate. A lot of the nrf24 fake chips don't even run at 250kbps.
-
@gohan said in How do I get multiple different mock barometers?:
Do mean the fake chips need to run at higher datarate?
All the fakes I've encountered can handle 1mbps and 2mbps.
-
Not sure why, but by upgrading to 2mbps datarate from the previous default of just 250kbps, I'm able to reduce LONG_WAIT to 0 without incurring packet losses. Go figure.
-
For the SHORT_WAIT, 10ms seems adequate on an nRF52832. Not sure where it hangs if the SHORT_WAIT is reduced too much lower than that though.
-
@NeverDie my question was if thay handle higher speeds better than the lowest since you said "A lot of the nrf24 fake chips don't even run at 250kbps"
@gohan said in How do I get multiple different mock barometers?:
@NeverDie my question was if thay handle higher speeds better than the lowest since you said "A lot of the nrf24 fake chips don't even run at 250kbps"
I'm not understanding your question.
-
What does it mean when the Domoticz log looks like this?
2017-08-11 08:11:20.670 MySensors: Node: 1, Sketch Version: v0.5
2017-08-11 08:11:24.053 MySensors: Node: 1, Sketch Name: MockMySensors
2017-08-11 08:11:24.068 MySensors: Node: 1, Sketch Version: v0.5
2017-08-11 08:11:27.454 MySensors: Node: 1, Sketch Name: MockMySensors
2017-08-11 08:11:27.470 MySensors: Node: 1, Sketch Version: v0.5
2017-08-11 08:11:30.870 MySensors: Node: 1, Sketch Name: MockMySensors
2017-08-11 08:11:30.887 MySensors: Node: 1, Sketch Version: v0.5
2017-08-11 08:11:34.245 MySensors: Node: 1, Sketch Name: MockMySensors
2017-08-11 08:11:34.260 MySensors: Node: 1, Sketch Version: v0.5
2017-08-11 08:11:37.650 MySensors: Node: 1, Sketch Name: MockMySensors
2017-08-11 08:11:37.666 MySensors: Node: 1, Sketch Version: v0.5
2017-08-11 08:11:41.036 MySensors: Node: 1, Sketch Name: MockMySensors
2017-08-11 08:11:41.051 MySensors: Node: 1, Sketch Version: v0.5
2017-08-11 08:11:44.375 MySensors: Node: 1, Sketch Name: MockMySensors
2017-08-11 08:11:44.391 MySensors: Node: 1, Sketch Version: v0.5
2017-08-11 08:11:47.800 MySensors: Node: 1, Sketch Name: MockMySensors
2017-08-11 08:11:47.816 MySensors: Node: 1, Sketch Version: v0.5
2017-08-11 08:11:51.185 MySensors: Node: 1, Sketch Name: MockMySensors
2017-08-11 08:11:51.200 MySensors: Node: 1, Sketch Version: v0.5
2017-08-11 08:11:54.583 MySensors: Node: 1, Sketch Name: MockMySensors
2017-08-11 08:11:54.599 MySensors: Node: 1, Sketch Version: v0.5
2017-08-11 08:11:58.005 MySensors: Node: 1, Sketch Name: MockMySensors
2017-08-11 08:11:58.021 MySensors: Node: 1, Sketch Version: v0.5
2017-08-11 08:12:01.384 MySensors: Node: 1, Sketch Name: MockMySensors
2017-08-11 08:12:01.401 MySensors: Node: 1, Sketch Version: v0.5Plainly, it's caught in a loop of some kind and never receives the sensor values.
-
For some reason, downgrading from 2mbps back down to 250kbps solved the above problem.
-
Fortunately, 1mbps seems to work, even if 2mbps doesn't.
