[Renzo Mischianti]

Hi Ivan,
now we have sufficient information.
First of all here I add a table comparison of EByte devices

                       E32                       E22                       E220
Chip                   sx1276-sx1278             sx1262-sx1268             LLCC68
Range                  3Km - 8Km                 5km - 11km                5Km - 10Km
Repeater               No repeater               Repeater                  No repeater
Remote conf            No                        Yes                       No

Power consumption      Best                      Good                      Very Good
                       Sleep 4μA                 Sleep 496μA               Sleep 6μA
Transmission and receiving have similar power consumption.

Message size bytes     58                        240                       200
Buffer size bytes      512 (ok)                  1000 (good)               400

Max air data rate (bps) 19.2k                    62.5k                     62.5k

Encryption             One standard              Configurable              Configurable crypt
Price                  Less expensive            More expensive            Less expensive

1. Neither the master nor the slaves sleep as they will be powered all the time by the eletricity network

If you want we can add after the WOR.

2. Each time a slave has something to send to the master, the set of information does not exceed 8 bytes, but it can be divided into more than one transmission, if necessary, without a problem.

If you select e22 or e220 the packet size is sufficient to send all the data.

3. As soon as the master receives data from a slave, it stops pooling and will process the slave’s operation, only resuming pooling after this processing, which can take up to 1 minute or more.

For this problem, we can adopt various solutions.

• The master tells the various clients when it is available for reception, and polls all clients in rotation.
• IF the sending frequency is quite low the buffer of the device It’s sufficient.
  If you select an e220 you have available 400bytes of buffer and if you set the packet size at 32bytes the LoRa device can store 12 packet without the intervention of the microcontroller.
  An e22 can store about 31 packet of data in his buffer (1000bytes).
• If you have a high sending frequency you can build a gateway with a microcontroller and put all the packets to a push server and another (or more than one) microcontroller to process the packet.

4. For security reasons, it is mandatory to have CRC and encryption in each communication.

E22 and E220 have configurable and transparent encryption.
You can develop CRC but remember these devices monitor the ambient noise and with a reduction of air data rate, It’s improbably that they lost packet.

5. The network will always be formed by a master and up to 8 slaves, typically from 2 to 5.

These devices support hundreds of devices.

Tell me if these informations are sufficient.
Bye Renzo

[Renzo Mischianti]

Hi Ivan,
do you know what kind of data (and the quantity) you must manage?

LoRa has the possibility to send a structured packet or a simple string, so as needed we can create a reliable and efficient transmission protocol, better than modbus which is widely used but has physical limitations.

Bye Renzo

[Renzo Mischianti]

Hi Ivan,
I think you can use the fixed transmission like in the examples in this article.

Ebyte LoRa E220 device for Arduino, esp32 or esp8266: fixed transmission, broadcast, monitor, and RSSI – 4

If you give our some details we can try to be more specific.

And if you are Italian remember that the articles are also in Italian.

Bye Renzo

[Renzo Mischianti]

Hi Anton,
I check the link and the source, and all are correct.
Explain which step you make to do the build.
Bye Renzo

[Renzo Mischianti]

Hi Anton,
you can read all that information in the relative articles.
MKS WIFI for Makerbase Robin: boards and how to wiring esp12 & NodeMCU – 1
MKS WIFI for Makerbase Robin: PCB and how to compile & upload firmware – 2
MKS WIFI for Makerbase Robin: communication protocol and Cura plugin – 3
MKS WIFI for Makerbase Robin: firmware upgrade and new Web Socket features – 4
MKS WIFI for Makerbase Robin: BeePrint web interface with Camera on Flying Bear Ghost – 5

Bye Renzo

[Renzo Mischianti]

Hi Gzegorz,
you can find some examples and documentation here

PCF8574 i2c digital I/O expander: Arduino, esp8266 and esp32, basic I/O and interrupt – Part 1

Bye Renzo

[Renzo Mischianti]

In the SecurityRoom.ino.
Try to reduce the sending frequencies.
Bye Renzo

[Renzo Mischianti]

Hehehehhe… but I think the problem is the sending frequencies of the email, probably GMail block the multiple sending if the second email is too close to the previous.
Bye Renzo

[Renzo Mischianti]

Hi Fix,
SoftwareSerial for esp32 is not a standard library, esp32 can use HardwareSerial with custom pins.
You can find all in the official documentation.
Bye Renzo

[Renzo Mischianti]

Can you send me all the serial output (with debugging enabled)?
Bye Renzo

[Renzo Mischianti]

Hi ozzy,
probably GMail blocked the attempt to send an email too close to the previous email (prevent spam).
Try to add a delay(10000); or more before the second Email2();

Bye Renzo

[Renzo Mischianti]

Hi Anton,
to develop a web solution for that machine I need the hardware.
No response from Makerbase, you can try to write to him for that support (蔡钦栋 ).
Bye Renzo

[Renzo Mischianti]

Hi Jimh,
any news?

[Renzo Mischianti]

Hi deti,
I think isn’t possible, e220 have an embedded cryptography system, but overall It’s based on new llcc68.
You can try with the less recent e32 based on sx1276, but I’m not sure about result.
Bye Renzo

[Renzo Mischianti]

Yes Jimh,
you must uncomment this line

// #define FTP_SERVER_DEBUG

Bye Renzo

[Author]

Posts