HI
I am new to Lora etc and have managed to get a Conduit (MTCDT-LEU1-EU-GB). I have root access to the unit and would like to know if I can use the AEP or mPower Firmware?
If so does anyone know where I can find the files and instructions needed?
2 Likes
AEP is fine for running the Gateway Bridge on. I prefer it for the connection manager.
1 Like
Thanks, i don’t suppose you have any links to all the files etc?
1 Like
hmmm, I’ll try that also. I was using the “plain” mLinux image, but the LTE just keeps giving me IPv6 on the newest models they got out.
PS: I know IPv6 is the way to go…dual-stacking is another whole undertaking.
1 Like
To expand a bit further, since I’ve recommended this a few times in opposition of the ChirpStack docs:
In a previous engagement where I was more frequently in contact with the folks at MultiTech, they strongly recommended not using mLinux unless you were planning on building an entire distribution around it. AEP has a lot of nice features (connection manager, DeviceHQ, etc), none of which precludes you from installing any software you want on it, Gateway Bridge or otherwise.
@eugeneb We always used the latest 5.x release from the MultiTech site.
@brocaar Thoughts on modifying the docs?
3 Likes
Hi
Thanks, I have managed to convert to AEP. Now to finish setting up the GW.
1 Like
Hi
I am using the web interface on the conduit and trying to setup the packet forwarder. Can I leave this in auto and select the Chirpstack bridge? or do I need in the manual config?
I have tried a few variations using the multitech example and also the bits listed on the Chripstack pages…
I am just looking to setup a simple test system with a device, GW and the Network and application server on an Unbuntu PC…
My GW has a MTAC-LORA-H (v1.5)’ card installed in AP2. I am in New Zealand and I think I can use EU868.
The GW IP is 192.168.10.208
The Unbuntu PC is 192.168.10.209
What else do I need?
Cheers
I usually start the packet forwarder and point it at where the Gateway Bridge is running on localhost 1700.
Hi
I have managed to get to get all the SW installed as as far as I can tell
1 Multitech GW - bridge is running
2 Network Server - running on my laptop
3 Application Server - running on my laptop
I am now trying to setup the Application server to add the gateway etc.
Where do I find the Gateway ID on the Multitech? so I can finish creating it in the application server?
On firmware 5.1.6, I see it in the web UI under LoRaWAN → LoRa Card Information → Gateway EUI.
Great thanks, I was wondering about that one
Hi I think I have everything running on my test system, but how can I test that the end node is connecting to the Multitech GW and how can I tell if the network server is connecting to the GW etc?
Been doing some more digging and I think the lora node is trying to connect to the GW, the lora-pkt-fwd-1.log file seems to show the device sending data.
However I don’t get anything on the Application server, infact I cannot see the GW on there.
I have setup the Multitech Conduit using AEP, and using the installation instructions installed all the software and setup the config files.
I am using EU868
the MQTT section in the chirpstack config file only has the MQTT IP addressed chnged to point to my laptop, which is running MQTT broker, network and application servers, I see the mosquitto logs tell me that the GW has connected…
The Lora packet forwarder config consists of the radio stuff.
Chat am I doing wrong?
{
“SX1301_conf”: {
“antenna_gain”: 0,
“chan_FSK”: {
“bandwidth”: 125000,
“datarate”: 50000,
“enable”: true,
“if”: 300000,
“radio”: 1
},
“chan_Lora_std”: {
“bandwidth”: 250000,
“enable”: true,
“if”: -200000,
“radio”: 1,
“spread_factor”: 7
},
“chan_multiSF_0”: {
“enable”: true,
“if”: -400000,
“radio”: 1
},
“chan_multiSF_1”: {
“enable”: true,
“if”: -200000,
“radio”: 1
},
“chan_multiSF_2”: {
“enable”: true,
“if”: 0,
“radio”: 1
},
“chan_multiSF_3”: {
“enable”: true,
“if”: -400000,
“radio”: 0
},
“chan_multiSF_4”: {
“enable”: true,
“if”: -200000,
“radio”: 0
},
“chan_multiSF_5”: {
“enable”: true,
“if”: 0,
“radio”: 0
},
“chan_multiSF_6”: {
“enable”: true,
“if”: 200000,
“radio”: 0
},
“chan_multiSF_7”: {
“enable”: true,
“if”: 400000,
“radio”: 0
},
“clksrc”: 0,
“lbt_cfg”: {
“enable”: false,
“rssi_target”: 160
},
“lorawan_public”: true,
“radio_0”: {
“enable”: true,
“freq”: 867500000,
“rssi_offset”: -162,
“tx_enable”: true,
“tx_freq_max”: 870000000,
“tx_freq_min”: 863000000,
“type”: “SX1257”
},
“radio_1”: {
“enable”: true,
“freq”: 868500000,
“rssi_offset”: -162,
“tx_enable”: false,
“type”: “SX1257”
},
“tx_lut_0”: {
“dig_gain”: 0,
“mix_gain”: 11,
“pa_gain”: 0,
“rf_power”: -6
},
“tx_lut_1”: {
“dig_gain”: 0,
“mix_gain”: 13,
“pa_gain”: 0,
“rf_power”: -3
},
“tx_lut_2”: {
“dig_gain”: 0,
“mix_gain”: 9,
“pa_gain”: 1,
“rf_power”: 0
},
“tx_lut_3”: {
“dig_gain”: 0,
“mix_gain”: 10,
“pa_gain”: 1,
“rf_power”: 3
},
“tx_lut_4”: {
“dig_gain”: 0,
“mix_gain”: 12,
“pa_gain”: 1,
“rf_power”: 6
},
“tx_lut_5”: {
“dig_gain”: 0,
“mix_gain”: 10,
“pa_gain”: 2,
“rf_power”: 10
},
“tx_lut_6”: {
“dig_gain”: 0,
“mix_gain”: 11,
“pa_gain”: 2,
“rf_power”: 11
},
“tx_lut_7”: {
“dig_gain”: 0,
“mix_gain”: 11,
“pa_gain”: 2,
“rf_power”: 12
},
“tx_lut_8”: {
“dig_gain”: 2,
“mix_gain”: 12,
“pa_gain”: 2,
“rf_power”: 13
},
“tx_lut_9”: {
“dig_gain”: 0,
“mix_gain”: 13,
“pa_gain”: 2,
“rf_power”: 14
},
“tx_lut_10”: {
“dig_gain”: 0,
“mix_gain”: 15,
“pa_gain”: 2,
“rf_power”: 16
},
“tx_lut_11”: {
“dig_gain”: 0,
“mix_gain”: 10,
“pa_gain”: 3,
“rf_power”: 20
},
“tx_lut_12”: {
“dig_gain”: 0,
“mix_gain”: 12,
“pa_gain”: 3,
“rf_power”: 23
},
“tx_lut_13”: {
“dig_gain”: 0,
“mix_gain”: 13,
“pa_gain”: 3,
“rf_power”: 25
},
“tx_lut_14”: {
“dig_gain”: 0,
“mix_gain”: 15,
“pa_gain”: 3,
“rf_power”: 26
},
“tx_lut_15”: {
“dig_gain”: 0,
“mix_gain”: 15,
“pa_gain”: 3,
“rf_power”: 27
}
},
“gateway_conf”: {
“gateway”: { “spi_device”: “” },
“gateway_conf”: {
“spi_device” : “/dev/spidev32765.2”,
“server_address”: “localhost”,
“serv_port_up”: 1700,
“serv_port_down”: 1700,
“fake_gps”: true,
“ref_latitude”: -45.038913794592176,
“ref_longitude”: 169.15674471327938,
“ref_altitude”: 250
}
}
}
2 Likes