Jason Reiss
Forum Replies Created
-
AuthorPosts
-
Jason Reiss
KeymasterDid the card work before you tried to flash it?
Did you try the flash procedure again?I suppose the check will return 255
$ mts-fpga-loader -cPower down the Conduit, pull the card out and re-install carefully to ensure it is fully seated.
September 4, 2019 at 11:21 am in reply to: Multitech Conduit mLinux 5.0 cannot connect Thething #28581KeymasterIt is not necessary to install the TTN forwarder.
Check “I’m using the legacy packet forwarder” in TTN when registering the gateway.
August 29, 2019 at 2:04 pm in reply to: unable to redirect to https even if I enable redirection #28458KeymasterIn AEP Gui see Administration > X.509 Certificate pages
To get an official signed cert you will need a DNS addressable name for your server or permanent IP address.
https://duckduckgo.com/?q=purchase+signed+ssl+certsKeymasterFollow the flashing procedure with a images from the previous version.
KeymasterAEP configuration is controlled through the API.
Network Server Mode
$ curl 127.0.0.1/api/loraNetwork -X PUT --data '{"lora":{"antennaGain":8}}' -H "Content-Type: application/json"Packet Forwarder Mode
$ curl 127.0.0.1/api/packetForwarder -X PUT --data '{"lora":{"antennaGain":8}}' -H "Content-Type: application/json"Save and Restart
url 127.0.0.1/api/commands/save_restart -X POST –data ”`Or save and restart only Lora services
$ curl 127.0.0.1/api/commands/save -X POST --data ''
$ curl 127.0.0.1/api/lora/restart -X POST --data ''KeymasterIt does not appear that the TTN installer currently has support for mlinux 5.0.0. This would need to be provided by TTN.
Also the mlinux-factory-image should be used as it has support for nodejs.
installer.sh: line 822: node: command not found
The device should be downgraded to a version supported by TTN or the TTN installer not used until it is supported.
Otherwise you could install the mlinux-factory-image 5.0.0 or AEP 5.0.0 and use the already installed Semtech packet forwarder to connect to TTN.
AEP would be easiest to configure, there is a dropdown and region selector.
Replace the server information in the configurations above with the TTN info according to your region.
https://github.com/TheThingsNetwork/gateway-conf
“server_address”: “router.as1.thethings.network”,
“serv_port_up”: 1700,
“serv_port_down”: 1700,KeymasterWith xDot using AT firmware v3.2.1 the Multicast setup is performed by the xDot but the fragmentation packets are passed through to the connected MCU to receive the firmware. The MCU can then decide what to do with the file.
AT+RXO=2
AT+SD
<<< RECEIVE DATA and Parity >>><<< RESPOND WITH CRC >>>
August 16, 2019 at 10:15 am in reply to: OTAA Failed – Check Keys error for US915 Multitech Conduit AEP Model #28347KeymasterSee troubleshooting guide for info from the gateway.
The UI will show any tx’d or rx’d packets on the packets page. Also successful or unsuccessful joins.Some code stacks take keys or eui values in LSB rather than MSB seen in the GUI and logs of AEP.
-
This reply was modified 5 years, 9 months ago by
Jason Reiss.
KeymasterDo you get the full list if you use lora-query directly or is it truncated the same as the API?
The API will call lora-query in the background.
I wonder if there is a difference in the next session record that may cause the JSON to stop the list or if there is a timeout.
KeymasterThe network server manages the database in /var/run/lora/ directory in RAM. It is backed up periodically to flash in /var/config/lora/ directory.
To force a backup to flash
$ lora-query -x database backupNow the /var/config/lora/lora-network-server.db file will be in sync.
Move the file to another conduit.$ /etc/init.d/lora-network-server stop
$ cp lora-network-server.db /var/config/lora/lora-network-server.db
$ /etc/init.d/lora-network-server startList all session
$ lora-query -x sessions list jsonSee available options
$ lora-query -x helpKeymasterThere is a serial data mode where the dot will send bytes received on the serial port to the network.
Otherwise custom firmware can be developed to read and report sensor data.
https://os.mbed.com/platforms/MTS-mDot-F411/KeymasterOnly submitting the diasabled signed firmware validation is needed.
Save and restart is not needed before performing the upgrade.
The unit should be reset to default values after being downgraded.Keymaster3.0.0-rc7 looks suspicious.
Try the 3.0.0 firmware from downloads or update to 3.1.x or 3.2.1
KeymasterYou get nothing every time you try AT&V?
But AT+NA is always successful?How about ATI?
It sounds like a connection issue.
There are firmware updates available:
KeymasterWhat output do you get?
How is the module connected?July 24, 2019 at 11:35 am in reply to: update to lora-network-server – impact on classB emission? #28246KeymasterThe network server will add a beacon to the scheduling queue to block other packets from being scheduled in the beacon time. It will not send a beacon to the packet forwarder to be transmitted.
The forwarder could be modified to adjust the beacon.
See lines 1963-2053 for beacon format code and lines 2093-2192 for GPS time used for scheduling.
https://github.com/Lora-net/packet_forwarder/blob/master/lora_pkt_fwd/src/lora_pkt_fwd.cJuly 24, 2019 at 10:54 am in reply to: update to lora-network-server – impact on classB emission? #28244KeymasterPrior to LW 1.0.3 Class B specification and functionality was experimental and subject to change for official release.
Unfortunately the final specification is not compatible with the previous definitions and the experimental features were not maintained.
In the latest releases with official Class B support as defined in LW 1.0.3 the packet forwarder schedules the beacon frames.
The forwarder could be customized to adjust the beacon format and polarity. Also the scheduling would need to function without GPS in your case.
http://git.multitech.net/cgi-bin/cgit.cgi/meta-mlinux.git/tree/recipes-connectivity/loraKeymasterIf the same software works on another hardware without issue then it may be a hardware issue.
I suggest opening a ticket at support.multitech.com to report the issue.July 12, 2019 at 7:04 am in reply to: [ERROR] update_firmware: Failed to back up current firmware #28205KeymasterThe firmware controls the frequencies used. If an EU868 firmware is flashed on to the device then EU868 frequencies are used.
If the configuration in external flash was erased then the configuration output will show 915 as default. The DevEUI was also lost and a special firmware is needed to restore it.
Also if a device was originally a 915 device and EU868 firmware is flash the default frequency will continue to report 915.
KeymasterThe mlinux factory images should include the packet forwarder binaries for v1.0 USB, v1.5 SPI and v2.1 gateway cards.
If the minimal image was installed these packages can be added using opkg. With a connection to the Internet available to the device.
# opkg update
# opkg install lora-packet-forwarder-geolocationSee available packages for each version in the feeds directory http://www.multitech.net/mlinux/feeds/
The /etc/opkg/mlinux-feed.conf file on Conduit points the opkg utility to a specific folder within feeds.
KeymasterThe regional parameters page 23 shows a table of how the channel mask control field is used in US915.
https://lora-alliance.org/resource-hub/lorawan-regional-parameters-v103revaThe network server determines the commands to send depending on what channels need to be enabled.
In LoRaWAN 1.0.2 and before two commands are needed to set to a single FrequencySubBand. The first disables all 125 kHz channels and enables one 500 kHz channel. The second enables a block of 8 channels. Some sets of channels would need several commands to be enabled.
ChMaskCtrl 7 and 0-3 are used
FSB1: 0300010071 & 0300ff0001
FSB2: 0300020071 & 030000ff01
FSB3: 0300040071 & 0300ff0011
…
FSB8: 0300800071 & 030000ff31In LoRaWAN 1.0.3 the option (5) to set the block of 125 kHz channels and a single 500 kHz channel was added. This allows a set of channel blocks to be enabled/disabled with one command.
ChMaskCtrl 5 is used.
FSB1: 0300010051
FSB2: 0300020051
FSB3: 0300040051
FSB4: 0300080051
…
FSB8: 0300800051KeymasterIt is part of the LinkAdrReq MAC command. The ADR algorithm controls the ChMaskCtrl bits to enable the correct channel according to selected FrequencySubBand.
https://lora-alliance.org/resource-hub/lorawanr-specification-v103
KeymasterThe previous value of AT+PN=0 – Public Network: off can be set with these commands:
AT+PN=0
AT+JD=1The default Join Delay was changed to 5 seconds to be LoRaWAN compliant. In previous versions changing from AT+PN=0 to AT+PN=1 or vice-versa would adjust the Join Delay. This must be done explicitly now.
July 8, 2019 at 2:46 pm in reply to: Errors Installing Custom APP after upgrading Firmware to 5.0.0 #28165KeymasterTry to run with sudo.
Previously the ssh session was started with root permissions. This is no longer the case with 5.0
KeymasterMTDOT box firmware will load the plan at start-up using setChannelPlan. The selected plan is saved to flash.
https://os.mbed.com/teams/MultiTech/code/MTDOT-BOX-EVB-Factory-Firmware/file/e76cec0eec43/main.cpp
KeymasterFound MTAC-LORA-G16-868 with MTAC-LORA-2.1 hardware
Looks like the hardware is not a USB lora card.
The 2.1 geo-location hardware should use this forwarder binary./opt/lora/pkt_forwarder
Also use the 2.1 configuration files in /opt/lora/
global_conf.json.MTAC_LORA_2_1*KeymasterCan you create a support ticket at support.multitech.com and share the /var/config/lora/lora-network-server.db file and device configuration backup file?
KeymasterThe mbed-semtech-lora-rf-drivers would be used in a firmware deployed on xDot.
If you connected to the xDot via SPI to attempt to access the LoRa radio you would need SPI to SPI application on xDot.
This project implements a custom shell for use with mbed-os on xDot/mDot to command it via UART.
https://github.com/MultiTechSystems/mbed-os-lorawan-tinyshellThe LoRaWAN layer can be removed or customized.
KeymasterYes it is possible.
Radio drivers can be found here.
https://github.com/ARMmbed/mbed-semtech-lora-rf-driversThey are used in the mbed-os lorawan implementation which can be used as a reference for using the drivers.
https://github.com/ARMmbed/mbed-os-example-lorawanKeymasterThis example could be modified.
node.js, python or c++ could be used with mqtt and http libraries to create an application without node-red.
-
This reply was modified 5 years, 9 months ago by
-
AuthorPosts