[Renzo Mischianti]

Hi,
If you correctly set the M0 and M1, the configuration for fixed transmission with relative addresses for the sender and receiver is okay. If you send the correct packet to address the message to the other device, it must work.
If It does not work, you do something wrong in one of these steps:
– connection schema
– configuration of receiver and sender
– code of the transmitter
– code of the receiver
Bye Renzo

• This reply was modified 1 year, 5 months ago by Renzo Mischianti.

[Renzo Mischianti]

And you use this library???
Bye RM

[Renzo Mischianti]

Hi ERicci,
To start a fixed-point communication, you need to configure the device properly.

Please post your configuration sketch and the sender/receiver one.

First of all, I advise you to try a simple get configuration and post an image of the connection to the board.
Bye Renzo

[Renzo Mischianti]

Thanks for the feedback 🙂

[Renzo Mischianti]

Hi,
A critical configuration parameter is WOR Cycle. For the sender, it is essential because it adds a long preamble to the message (long as wake time). The receiver uses wake time as a pull interval time check.
So, if the receiver checks every 2000ms (polling time) if there is a message, the sender adds a 2000ms preamble. The receiver intercepts the message preamble, waits for the actual message to read It, and returns to power-saving mode.

So, if you want to maximize the power savings, you must put the maximum WOR Cycle on the receiver. If you want more efficiency, you must do the inverse and add a long preamble to the sender.
Even if the EByte advises to use the same WOR cycle.
Bye Renzo

[Renzo Mischianti]

Hi Willian,
the code is quite complex, and I need time to check It in depth, but what is the scope of the Ticker library?
Bye Renzo

[Renzo Mischianti]

Hi Baftu,
I think you set the pointer for the structure, not the structure of single elements.
You must create a fixed structure with fixed-size elements.
Bye Renzo

[Renzo Mischianti]

Hi Elkez,
I normally describe a device module thinking of a real scenario (I don’t write to have a visit), and I select the e70 because it has RSSI and a very good Sleep mode management to manage the battery. You probably never raise a distance if a device is declared for 1.5km but has high sensitivity.
All to say, this can be considered a good solution.
There are alternatives, but the efficiency can’t be the same.

But in your case (low number of messages per second), I think it can be a good solution for a LoRa device like the e220.

Bye Renzo

[Renzo Mischianti]

Hi phnahes,
I think you can’t decode because the EByte uses a proprietary cryptography system to obfuscate the message.
Even if some people decode it for e32 (it doesn’t have a key to change the algorithm), here is the thread where you can find some information.
EByte LoRa Communication encode/decode, crypt/decrypt
I don’t know if @Sahar-2 go ahead with Its idea, but I think you can ask.
Bye Renzo

[Renzo Mischianti]

Hi,
yes, it’s quite impressive, and I start some penetration test and I notice that 4/5 wall (with meet iron) can’t block the signal.
Bye Renzo

[Renzo Mischianti]

If you want to try, I also pushed a new version that adds a lot of features and the possibility to specify the INPUT_PULLUP mode.
Bye Renzo

[Renzo Mischianti]

Hi,
I tested now this sketch

/*
 KeyPressed on PIN1
 by Mischianti Renzo <http://www.mischianti.org>

 https://www.mischianti.org/2019/01/02/pcf8575-i2c-digital-i-o-expander-fast-easy-usage/
 */

#include "Arduino.h"
#include "PCF8575.h"

// Set i2c address
PCF8575 pcf8575(0x20);
unsigned long timeElapsed;
void setup() {
	Serial.begin(115200);
	// pcf8575.pinMode(P0, OUTPUT);

	pcf8575.pinMode(P1, INPUT);

	pcf8575.begin();

  timeElapsed = millis();
}

void loop() {
	// if (millis() - timeElapsed > 2000) {
	// 	if (pcf8575.digitalRead(P0) == HIGH) {
	// 		pcf8575.digitalWrite(P0, LOW);
	// 	} else {
	// 		pcf8575.digitalWrite(P0, HIGH);
	// 	}
  //   timeElapsed = millis();
	// }
	uint8_t val = pcf8575.digitalRead(P1);
	if (val == HIGH) {
		Serial.println("KEY PRESSED");

	}
	delay(100);

}

And this sketch

/*
 KeyPressed on PIN1
 by Mischianti Renzo <http://www.mischianti.org>

 https://www.mischianti.org/2019/01/02/pcf8575-i2c-digital-i-o-expander-fast-easy-usage/
 */

#include "Arduino.h"
#include "PCF8575.h"

// Set i2c address
PCF8575 pcf8575(0x20);
unsigned long timeElapsed;
void setup() {
	Serial.begin(115200);
	pcf8575.pinMode(P0, OUTPUT);

	pcf8575.pinMode(P1, INPUT);

	pcf8575.begin();

  timeElapsed = millis();
}

void loop() {
	if (millis() - timeElapsed > 2000) {
		if (pcf8575.digitalRead(P0) == HIGH) {
			pcf8575.digitalWrite(P0, LOW);
		} else {
			pcf8575.digitalWrite(P0, HIGH);
		}
    timeElapsed = millis();
	}
	uint8_t val = pcf8575.digitalRead(P1);
	if (val == HIGH) {
		Serial.println("KEY PRESSED");

	}
	delay(100);

}

and work properly.

Can you also insert the wiring diagram?

Bye Renzo

Attachments:

You must be logged in to view attached files.

[Renzo Mischianti]

Hi Amaia,
I test the library, and it works correctly.
Rewrite the code as usual and retry.
Bye Renzo

[Renzo Mischianti]

Hi,
thanks for your feedback, I think your information can be very useful.
Bye Renzo

[Renzo Mischianti]

Hi,
It’s very strange; It’s more likely that there are some problems with the power supply and the pull-up resistor.
Bye Renzo

[Author]

Posts