Develop LoRa program

[Thomas Nguyen-Van]

Hi,

I’m trying to use lora_gateway (http://git.multitech.net/cgi-bin/cgit.cgi/lora_gateway.git) library to develop my own LoRa program on MultiConnect Conduit with LoRa mCard but I couldn’t reach concentrator. With debug from the library activated I get a ERROR: MPSSE OPEN FUNCTION FAILED on mpsse = OpenIndex(VID,PID,SPI0, SIX_MHZ, MSB, IFACE_A, NULL, NULL, 0); line. VID and PID are set respectively to 403 and 6010.

The basic_pkg_fwd is running without a problem with information as :
*** Basic Packet Forwarder for Lora Gateway ***
Version: 1.4.1
*** Lora concentrator HAL library version info ***
Version: 1.7.0; Options: ftdi sx1301 sx1257 full mtac-lora private;
***

Naively, I’ve focus on ftdi mode but I’ve seen two spidev3276x.2 in /dev which can refer to a native mode if I’m correct. So for now I don’t really know what parameters to use to access the concentrator with the library lora_gateway. Should I use Native or FTDI mode? Which parameters should I have to take in account to access concentrator?

Hope some of you could give me some response.

Thanks.

[gildas gaudin]

Hi,

I have the same problem.
How do we get a lora_gateway source code up to date for a MultiConnect Conduit (mLinux Model) ?

Thanks.

[Jason Reiss]

This branch is built for mLinux:
http://git.multitech.net/cgi-bin/cgit.cgi/lora_gateway.git/log/?h=1.7.0-mts

It has the changes needed for MTAC-LORA support.

[gildas gaudin]

With this version I also have problems:

1/ cross compilation issue (toochain from http://www.multitech.net/mlinux/sdk/3.1.0/) => ftdi.h include not found from mpsse.h when compiling loragw_spi.ftdi.c
It works when LIBFTDI1=1 (=> libftdi1/ftdi.h)
Could you confirm that is the right way to fix it ?

2/ ERROR: MPSSE OPEN FUNCTION FAILED when running util_pkt_logger on MTCDT-210L
Any information for the debug is welcome.

Thanks.

• This reply was modified 8 years, 11 months ago by gildas gaudin.

[gildas gaudin]

In dmesg I see :
usb 1-2.1: new high-speed USB device number 3 using atmel-ehci
usb 1-2.1: New USB device found, idVendor=0403, idProduct=6014
usb 1-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-2.1: Product: Single RS232-HS
usb 1-2.1: Manufacturer: FTDI

and in loragw_spi.ftdi.c :
/* parameters for a FT2232H */
#define VID 0x0403
#define PID 0x6010

(edit wrong file)

• This reply was modified 8 years, 11 months ago by gildas gaudin.
• This reply was modified 8 years, 11 months ago by gildas gaudin.
• This reply was modified 8 years, 11 months ago by gildas gaudin.
• This reply was modified 8 years, 11 months ago by gildas gaudin.

[gildas gaudin]

problem was in library.cfg

I change configurations:
CFG_BRD= ref_1301_868 mtaclora
CFG_BAND= eu868 full (else compilation issue)

[gildas gaudin]

It seems that http://git.multitech.net/cgi-bin/cgit.cgi/lora_gateway.git/log/?h=1.7.0-mts does not match with https://github.com/Lora-net/packet_forwarder

Example: struct lgw_conf_board_s no more defined)

Do we have an other branch for packet_forwarder source code ?

[Jason Reiss]

The packet forwarder recipe and patches for mLinux are found here:
http://git.multitech.net/cgi-bin/cgit.cgi/meta-mlinux.git/tree/recipes-connectivity/lora

We are using the 1.4.1 version of the Semtech packet forwarder as a base.

[gildas gaudin]

Thank you for support.

Does MultiTech plan to make new versions from Lora-net 3.x.y releases ?

Regards.

[Jason Reiss]

The things network is open source and has the latest releases of lora-net lora_gateway and packet forwarder with support for multitech hardware.
https://github.com/TheThingsNetwork/

We may update when we have an new version of MTAC-LORA gateway card.

[Christophe Lecomte]

Hi Jason,
I’am working with Gildas.
The last things network lora_gateway version is 3.1.0.
This version gives this error (spi=native):
ERROR: NOT EXPECTED FPGA VERSION
ERROR: FAIL TO CONNECT BOARD

or this error (spi=ftdi)
ERROR: Version of calibration firmware not expected, actual:3 expected:2

Does it work only with older multitech hardware (version 2)?

And MTAC-LORA is version 3 ?

Which SPI configuration should we used : native or ftdi ?

Thanks for your help.

[Jason Reiss]

Are you compiling the Semtech version of 3.1.0 or TTN version?

TTN has commits past Semtech 3.1.0 to add Multitech support:
https://github.com/TheThingsNetwork/lora_gateway/commit/4f77b387f9893cb49749cf4d61ac4f9221829fc9

[Christophe Lecomte]

I’m compiling the TTN version 3.10, and the TTN commit for multitech support is included.

The software is checking the calibration firmware version

/* Check firmware version */
lgw_reg_w(LGW_DBG_AGC_MCU_RAM_ADDR, FW_VERSION_ADDR);
lgw_reg_r(LGW_DBG_AGC_MCU_RAM_DATA, &read_val);
fw_version = (uint8_t)read_val;
if (fw_version != FW_VERSION_CAL) {
printf(“ERROR: Version of calibration firmware not expected, actual:%d expected:%d\n”, fw_vers$
//return -1;
}

The MTAC LORA card returns 3, and the software is waiting for the version 2 :
#define FW_VERSION_CAL 2 /* Expected version of calibration firmware */

Regards

[Jason Reiss]

Seems the cal_fw.var file and expected versions do not match.

The calibration firmware is loaded by the lora_gateway.

Either load the previous cal_fw.var from before Semtech release 2.0.0 or update the expected version to 3.

[Author]

Posts