NRF24 transport status not initialized

Reply to NRF24 transport status not initialized on Wed, 10 Jul 2019 15:07:21 GMT

Yveaux — Wed, 10 Jul 2019 15:07:21 GMT

@mfalkvidd said in NRF24 transport status not initialized:

I do not know what they were intended for

Tekka's chart says it all; preHwInit() has no serial output, so can be used to e.g. initialize serial devices (some hardware might require this). Then before() is called which starts logging to serial.

Reply to NRF24 transport status not initialized on Wed, 10 Jul 2019 12:40:35 GMT

skywatch — Wed, 10 Jul 2019 12:40:35 GMT

@tekka - Simply marvellous! - Thank you for that :)
A picture is worth a thousand words. ;) - I'll need to look at this in detail this evening and see what does and what doesn't make sense to me. But it is a great start to explaining these aspects.

@mfalkvidd It is great that you still have the passion and patience to help people even when you are as much in the dark as the rest of us. Please never leave! ;)

Reply to NRF24 transport status not initialized on Wed, 10 Jul 2019 12:05:27 GMT

mfalkvidd — Wed, 10 Jul 2019 12:05:27 GMT

@skywatch thanks for explaining

I do not know what they were intended for, but if someone knows, it would be great if the information could be added to https://www.mysensors.org/apidocs/group__MySensorsCoregrp.html#ga6892318cbd6aa933bd2d9e70104652b1

Reply to NRF24 transport status not initialized on Wed, 10 Jul 2019 15:29:50 GMT

tekka — Wed, 10 Jul 2019 15:29:50 GMT

@skywatch Here is a simplified flowchart that illustrates the two most common MySensors bootup scenarios (but as @mfalkvidd pointed out, there are many more possibilities depending on the transport configuration and/or defines):

Reply to NRF24 transport status not initialized on Wed, 10 Jul 2019 11:39:41 GMT

skywatch — Wed, 10 Jul 2019 11:39:41 GMT

@mfalkvidd But I didn't ask for 'documentation that covers all possible scenarios' - of course I know that would be a huge undetaking.

Just a guide that says......

PREHInt() This was developed because (reason here)...
Use this for xxxx type data so that (reasons here)....
Here is an example....

Done!
Then the same for before() as to me they are one and the same and I can't even begin to think of why you would need both.

Reply to NRF24 transport status not initialized on Wed, 10 Jul 2019 10:34:55 GMT

mfalkvidd — Wed, 10 Jul 2019 10:34:55 GMT

@skywatch What is "correct" depends on a lot of things. I don't think it would be possible to create documentation that covers all possible scenarios. In a way, it is like asking "what is the correct way to write a c program".

With that said, we have https://github.com/mysensors/MySensors/issues/927 that tries to document which order the functions are executed. But due to MySensors' flexibility, the execution order is different depending on which defines are set, how long time some things take, etc. So something "as simple" as documenting the order of execution is unfortunately overwhelming :-(

Reply to NRF24 transport status not initialized on Wed, 10 Jul 2019 09:42:06 GMT

skywatch — Wed, 10 Jul 2019 09:42:06 GMT

@tekka That is an interesting thing. Is there a document somewhere that explains the correct useage of pre-Hwint() and before() - As they both seem to be the same to me.

Reply to NRF24 transport status not initialized on Wed, 10 Jul 2019 12:52:27 GMT

tekka — Wed, 10 Jul 2019 12:52:27 GMT

@danielef alternatively, you can move the setup() code to preHwInit() - this function is called before the any other HW initializes.

Reply to NRF24 transport status not initialized on Wed, 10 Jul 2019 07:30:21 GMT

DanieleF — Wed, 10 Jul 2019 07:30:21 GMT

@tekka my setup is quite simple:


void setup() {

  wdt_disable();

  pinMode(RAIN_D_PIN, INPUT_PULLUP);
//  pinMode(REED_PIN, INPUT_PULLUP);

  pinMode(VELUX_UP_PIN, OUTPUT);
  pinMode(VELUX_DOWN_PIN, OUTPUT);

  digitalWrite(VELUX_UP_PIN, RELAY_OFF);
  digitalWrite(VELUX_DOWN_PIN, RELAY_OFF);

  sensors.begin();
  if (!sensors.getAddress(ds18Addr, 0)) 
    Serial.println("************** Unable to find address for Device 0"); 

  sensors.setResolution(ds18Addr, 11);

  wdt_enable(WDTO_8S);

}

the only driver I use is the one from DallasTemperature library, which I used also in other nodes without any issue.
This evening I'll try removong it to see if it has any effect.

Regarding radio issues, this node goes completely offline from that message on: it neither sends nor receive any message.

Reply to NRF24 transport status not initialized on Tue, 09 Jul 2019 20:50:24 GMT

tekka — Tue, 09 Jul 2019 20:50:24 GMT

@danielef A driver initialization in setup() interferes with the SPI and/or RF24 radio: TSP=0 hints to a failed transport sanity check. I presume you're having radio issues in loop()?

Reply to NRF24 transport status not initialized on Tue, 09 Jul 2019 20:18:30 GMT

mfalkvidd — Tue, 09 Jul 2019 20:18:30 GMT

@danielef would it be possible for you to post the log before 2093ms?