@OldSurferDude I have since looked at various modules that are sold on the internet. My conclusion is that they are not all the same. Some seem to be much better than others. The price also shows that.
I use this shield for the radio comms NANO V3 Wireless Shield. It has the caps already built in as well as some level shifting for the signal pins.
@mfalkvidd said in Absolute location of system config in EEProm:
https://github.com/mysensors/MySensors/blob/253109d3ff00ec524c5d1e1dfcd8e197c96e54c2/core/MyEepromAddresses.h might be useful
Wow thanks. That is exactly what I needed.
Thanks for the help, you are a champion.
Aah ok that makes sense. My application is for rural use and I need the max distance possible. The slow response will not be a problem as the sensors don't send a lot of data at all. So maybe I will stay with the SF4096 for now but I will do some experimenting with the settings. Just to understand them a bit better.
@mfalkvidd said in Absolute location of system config in EEProm:
https://github.com/mysensors/MySensors/blob/253109d3ff00ec524c5d1e1dfcd8e197c96e54c2/core/MyEepromAddresses.h might be useful
Wow thanks. That is exactly what I needed.
Thanks for the help, you are a champion.
@mfalkvidd said in Absolute location of system config in EEProm:
@mariusl I am not sure I understand the question, but saveState will add EEPROM_LOCAL_CONFIG_ADDRESS to the position you use in the call.
That is what I asked thanks.
@mfalkvidd said in Absolute location of system config in EEProm:
You can use EEPROM_LOCAL_CONFIG_ADDRESS as start address.
I take it this will be allocated after the system config block? Does this include the locations for saveState()? I noticed that you can give an address for the saveState() to locate the data. If that is not included in the system config block it will make sense to just add a couple of bytes to the EEPROM_LOCAL_CONFIG_ADDRESS and make sure that the saveState() locations are below that.
@electrik said in Absolute location of system config in EEProm:
If you use saveState() and loadState() the library will handle this for you
Will this be true for a situation before the mySensors library has been initialized? I want to save my data before the system is loaded.
Hi
I want to store some custom config variables in EEprom prior to the hardware init of the system.
The question is where is the system config located in the EEprom and where can I go write without doing damage?
Thanks for the reply. If use defined variables then I am sure it should be possible to do.
As far as the dynamic setting is concerned, I want to connect the sensor serial port to a terminal and then set the variables that I need through text messages. There is an Arduino library called sCmd that has a very basic protocol that allows this kind of thing. There will be a button to put it into setup loop before hardware init and then I need to write the variables to the Eeprom. They will be retrieved at the next boot. Hence my need to know where the system puts it's config variables so that I don't go mess that up.
Hi
I want to set some of my parameters prior to the mySensors code loading. I want to set the NodeId on my sensors and things like the WiFi credentials on the gateway. The gateway can be ESP8266 or ESP32.
I noticed that was a preHwInit() function available. Will this allow me to set things like that before the code loads and if so where will I store or effect those parameters?
Aah ok that makes sense. My application is for rural use and I need the max distance possible. The slow response will not be a problem as the sensors don't send a lot of data at all. So maybe I will stay with the SF4096 for now but I will do some experimenting with the settings. Just to understand them a bit better.
@yury said in Gateway sends NACK to node:
any reason for the Spread factor SF4096 ?
Not at all. It is from example code that I found online. I don't really know what it does to be honest.
@yury said in Gateway sends NACK to node:
These lines can affect. the TRANSPORT_STATE_TIMEOUT may be less than a actual message sending time. you will get constant NACK's.
I have it working fine now but I would like to make it as robust as possible. What would you suggest as a good value for the timeout?