Thankyou very much Elijah.

So defining those at the beginning of the program once is enough right and the microcontroller automatically does the rest every time. Cant i like use the pins of the arduino since they are already defined in the sx1276.cpp and the library is build basing on that. what i was speaking is on line 46 of the below provided link.

https://developer.mbed.org/compiler/#nav:/SX1276PingPong/SX1276Lib/sx1276/sx1276.cpp;

Regards

Nandan,

Not sure what they are doing in the main.cpp file with calling the Radio() constructor with type defined as SX1276MB1xAS [at line 67], but I would think they are creating a Radio object defined using the callback function pointers passed to Radio and returning an object of type SX1276MB1xAS from the constructor as the "Radio".

So, based on what their code is doing, no. You don't have to use the pins since they are already being declared in the sx1276.cpp file. All you have to do to initialize your radio is to pass the callback functions you want the radio to call on events to the Radio() constructor in the main.cpp file at line 67.

Example: Here's what my main.cpp code might have: SX1276MB1xAS Radio( OnTxDone, OnTxTimeout, OnRxDone, OnRxTimeout, OnRxError, OnFhssChangeChannel, NULL ); Bunch of main code here...... Function declarations for the callback functions passed to Radio: void OnTxDone( void ){} void OnRxDone( uint8_t *payload, uint16_t size, int16_t rssi, int8_t snr){} void OnTxTimeout( void ){} void OnRxTimeout( void ){} void OnRxError( void ){} void OnFhssChangeChannel( uint8_t channelIndex ){}

The digital pins shown on the LoRa module as DIO0,DIO1, etc. are all in use by the module for transmission, and should not be used (afaik). The pins defined in line 46 of https://developer.mbed.org/compiler/#nav:/SX1276PingPong/SX1276Lib/sx1276/sx1276.cpp are used internally for the libraries. Are you asking about using just the pingpong program as it is defined? Or using the unused pins on the LoRa module? Or just using the arduino pins for the NUCLEO-L152RE board? You shouldn't need to define the arduino pins, as they are already defined. You can call them as D12, D11, etc. to use them, but trying to define them would not work. The line 46 you referred to is used internally in the library to interface the LoRa module to the MBED arduino socket, with the pins predefined by the library itself, only requiring the user to write the callback functions and the main.cpp file.

Elijah Thankyou again,

I was speaking about the arduino pins only. The main doubt i have is are those pins defined for transmitter or the nucleo board. But as you were also telling that they are defined for the nucleo board itself I am confident enough. So can i directly connect them to the transmitter's MISO, MOSI ports?

Just for reference did you work on this inair9B module before?

Regards

Nope, havn't worked with that module. Yes, I would assume you just plug the MOSI on your board to the MOSI arduino pin, the MISO on your board to the MISO arduino pin, etc.

The NUCLEO board socket is designed to be arduino (compatible/similar) to allow easy development.

The program code defines the pins for the processor on the board to use when running all of the software. The software is assuming you have the same (MOSI,MISO,SCK,etc.) connection between the two hardware boards, so as long as your inair9B module is operating as the module that the code was written as an example for, it should be plug-n-play.

Just a quick question. NUCLEO board is a master and LoRa module is a slave? Can I connect 3rd device as a slave to NUCLEO?