Hi,
I was wondering if there are any plans to update the host CPU in the Conduit? I have an application that would really benefit from a more powerful host processor with a more modern core architecture. Even a move to a 600MHz A5 CPU would be a big improvement, but ideally a dual A7 or better.
I am happy to discuss my application off line if required.
Thanks
Jonathan
A network server can send a packet to the end-device to enter a test mode of operation. Test Mode can enable/disable ACK and echo payloads back to the test server. ADR can be used to change the datarate of the end-device.
TestMode is implemented in the LoRaWAN stack, the reference Semtech stack shows the client side functionality starting at line 705.
Full test documentation is available for LoRa Alliance members at https://lora-alliance.org/
Okay, Jeff, will do – thanks.
I need to support RU864 channel plan on my MTCDTIP-LEU1-266A with “Lora Mode” set to PACKET FORWARDER.
Right now I’m running firmware 1.6.4 AEP.
If I try to change the SX1301 Channel Plan I cannot find RU864.
Should I wait new firmware? When will it be available?
Hello,
I’m using Conduit AEP model (MTCDT-LEU1-247A,Firmware 1.4.17) with LoRa Network Server. When I add a device in Device Configuration page or with lora-query, it is visible on the web page but not in the node-list of lora-query.
When I power on the device, its JoinRequest is rejected cause of UnknowDevEUI.
Any idea on what I’m missing ?
Thanks in advance,
BR
I forgot to mention that the device is using OTA joining mode so I only have it’s DevEUI.
BR,
Add the device eui and key into Key Management page.
Device Config and Session is for ABP provisioning.
Hello Jason,
thank you for your answer, but I only have the DevEUI. I have to choose for AppEUI but what about Appkey ?
Now I have a rejected JoinRequest cause of MICFailed.
Thank you for your time.
The AppKey is required to match the device.
Hello,
We have just started development on a new Conduit AP which was shipped with mLinux 3.3.13. We are keen to see if we can update to 4 although as the download is several GB and there’s no USB port on the device we’re looking for guidance as to how best to achieve this, as there’s only ~120MB of space in /var/volatile
Similarly, there appears only to be node.js 0.10.44 available as an opkg install, which is very, very old (even NPM doesn’t exist). Even remaining on 3.3.13 we need to be able to update the node.js version to something much more recent (version 6+). Wondering again what would be the best way to achieve this.
Thanks
Rob
ok, answer part of this myself (for others if needed).
Found the ~30MB upgrade image in http://multitech.net/mlinux/images/mtcap/4.0.1/
then it’s simply copy to /var/volatile, and /usr/sbin/mlinux-firmware-upgrade /var/volatile/mlinux-mtcap-image-mtcap-upgrade-withboot.bin
ok, answer my own second point (should go digging first me thinks).
V8 dropped support for ARMv5 aligned with node.js v0.10, so that’s why (later versions can’t be compiled to run on the Conduit hardware)
Hello,
We’ve upgraded our new Conduit AP to mLinux 4.0.1. Installed node.js 0.10.48 via opkg. It doesn’t appear to install the node package manager (npm) and we need it to install some third party (and our own) modules. Anyone point us in the right direction? Seems it’s installed with the AEP/node-red install but we don’t need/want that.
Thanks in advance
Rob
Hello,
I am trying to configure cellular connection on a Multitech IP67 Base Station -mLinux version.
I tried three different (different providers) sim cards (4G) while the gateway is indoors and none of them is even registered on a network. Checked with AT commands:
AT+CREG? and AT+CGREG?
Both response with 0,2 (not registered).
With the AT+CSQ? command I sometimes get good signal e.g. 23,99 and some other is 99,99 (undetectable). The second parameter (bit error rate) is always 99 (undetectable).
In the same location I have a Multitech Conduit AEP version 210-LEU1 which has one of this sim card, connected on cellular, stable and working properly.
Also, in the same location all three sim cards connect normally with good signal on a mobile phone.
I only managed to have one sim card to successfully register and connect to the internet while outdoors and holding really high the gateway!
With two LTE antennas shouldn’t the gateway have a better behavior? Am I missing something obvious? Do I have to be always outdoors to configure it?
Is there any default configuration that needs to be changed for the mLinux version?
I am located in Cyprus, Europe and the gateway is the EU version.
Thank you very much.
Christos,
Please file a support portal case at https://support.multitech.com. They will be able to help you.
Thank You,
Jeff
I have been using the call_home function where the device connects to device HQ on its first boot up connected to ethernet, and installs the config file to connect to lora and cellular. The only problem i am running into is the GWID, in the db.json from the config file. Each conduit should have its own GWID that it gets from the LORA card but it assigns them all the same one. What would be the best way to make the GWID defined correctly on the initial boot up?
Manual mode allows a placeholder.
Anything between the angled brackets will be replaced by the HW EUI.
“gateway_ID”: “<LORA-EUI>”,
The next release will have an option to fill the EUI from the hardware for the LoRa Packet Forwarder config.
Hello guys,
I have a system consisting of several xDot modules (xdot-firmware-3.0.0-US915-mbed-os-5.4.7.bin firmware).
The system is configured for peer-to-peer mode. The system functions well.
One device (A) sends data to another (B) and gets data from that device (B).
I suppose that the total time on air (TX Data Rate DR13, Time On Air 57 ms for 128 bytes of data) should be:
time on air from A to B (57 ms) plus time from B to A (57 ms). But I never get the total time on air less than 400 ms.
Any of your suggestions, thoughts.
Thanks for the support / help.
Hi Jonathan
MultiTech is currently working on the next generation Conduit Gateway that
will utilize a ARM Cortex A9. We anticipate availability towards the end of this year.
-Best Regards
Hi everyone,
I thought I’d share with you a little application I made for the Multitech MultiConnect Conduit. It is completely open source, written in pure C, based on some examples from Microsoft’s Azure IoT Hub C SDK and designed to be a minimal example of how you might use a Conduit to forward LoRaWAN packets to an Azure IoT Hub instance. You can find the source code along with simple instructions here:
https://github.com/ljmarks/multitech-conduit-lora-iot
Apologies if this is an inappropriate post – I’d be happy to move it to a different category or otherwise remove it altogether.
Thanks
