[Robert]

Hi Renzo,

Thanks for your reply. I will assume it’s a terminating byte (although it’s not mentioned in the data sheet) and I will simply ignore it.

[Robert]

Hi Renzo,

The problem is that the module seems to send 12 bytes instead of 11 in reply to the request for configuration request. That command comprises 3 bytes : C1 followed by the start address and the number of parameters. For example sending C1 00 08 should result in returning the 3 command bytes followed by the bytes contained in all registers (8 in total : 00H … 07H).
That means 11 bytes in total (i.e. 3 + 8) but it returns 12 bytes, the 12th being 0x00 or the ASCII code for NULL.
The attached screen capture shows the code for reading the returned bytes and displaying them in the serial monitor.

Attachments:

You must be logged in to view attached files.

[Robert]

Hi Renzo,

I came across a discrepancy in the comments in the the E220 example file 01_setConfiguration.ino
The pin assignments for an Arduino Nano in the top of the comments do not match the pin assignments in the lines below that can be uncommented. See attached screen capture.

I presume that for an Arduino Nano I/O pins 6, 2 & 4 are used for AUX, M0 & M1 respectively in your library, right?

By the way, I presume I can use other I/O pins if it simplifies the PCB routing and change my source file accordingly, right?

Best regards and thanks for your help.

Robert

Attachments:

You must be logged in to view attached files.

[Robert]

Hi Renzo,

Thanks you for the link. I wasn’t aware that you already released the E220 library.

Bye,
Robert

[Robert]

Hi Renzo,

Thank you very much. It’s clear now.

I am aware that the library is for the E22 series but I think it can be used with the E220 in my case as I only need a simple point-to-point fixed TX/RX link.

Maximum packet size of 200 is OK for me and I don’t need a network ID.

One major difference is that M1 & M0 both need to be “1” for configuring the device instead of “1” and “0” respectively for the E22 series.

I still need to check if there are other differences in the various registers bit settings.

Bye,
Robert

[Robert]

Hi Renzo,

Thanks for your fast reply!

In fact I got the complete library and examples from github and I already looked at the setConfiguration file. You did a great job! It will surely simplify my work. Thanks a lot.

However, what I don’t understand is that in the fixed transmission file (Arduino_e22_04_SendFixedTransmission.ino) there is a comment saying that the the other device (i.e. the receiver of the fixed transmission) should be set as a FIXED SENDER and this device (i.e. the fixed sender) should be set as FIXED RECEIVER.

I would expect it to be just the other way around.

Same comment for the receive message file (Arduino_e22_08_receiveMessage.ino) where the configurations are reversed and saying that this device (i.e. the receiver) should be configured as a FIXED SENDER.

Am I missing something?

Best regards,
Robert

[Author]

Posts