Jason Reiss
Forum Replies Created
-
AuthorPosts
-
Jason Reiss
KeymasterKeymasterA host processor is required to perform the fragmentation re-assembly.
It can also be used to flash the xDot over serial with the default bootloader.This open-hardware board uses xDot with an external flash.
It is used with mbed-os for lorawan FUOTA demos, the lorawan fuota example includes a bootloader to flash the xDot from flash, it does not have the serial transfer of firmware of MTS bootloader. The example is using the mbed-os lorawan stack with the full FUOTA application with multicast setup and packet fragmentation implemented in an xDot firmware with no AT commands.https://github.com/L-Tek/L-Tek-FF1705
https://os.mbed.com/platforms/L-TEK-FF1705/
https://github.com/ARMmbed/mbed-os-example-lorawan-fuotaKeymasterThe xDot bootloader does not support an external flash to self flash.
The bootloader would need to know the connection parameters of the flash and file-system type.KeymasterYes, version mbed-os v5.11.1 should be used with GCC ARM v6 toolchain.
https://os.mbed.com/docs/mbed-os/v5.11/tools/index.html
gcc-arm-none-eabi-6-2017-q2-update
KeymasterUS915 using DR0 can send a maximum of 11 bytes payload.
Occasionally MAC commands responses need to be sent to the network. This will reduce the number of payload bytes available to send.In Dot v3.2.1 AT+TXS will return the number of bytes available for the next uplink.
KeymasterAT commands over serial is the only option with AT firmware
https://stackoverflow.com/questions/23532038/read-response-at-command-with-pyserialThis c++ utility could be ported to python
https://github.com/ARMmbed/ATParser/blob/master/ATParser.cppKeymasterThe MTAC cards have filters specific to 915 or 868 to meet regional certifications. Tx and Rx outside of the filter frequency range is greatly reduced.
Keymaster
See “Using Auto-Flash During Reboot with image upgrade.bin”The upgrade can be performed with mLinux and AEP upgrade files obtained from the downloads page.
KeymasterThe /var/config and /var/oem partitions will remain intact during firmware upgrade. Any configuration or data you wish to maintain across upgrades will need to be stored there.
KeymasterThe Join Request contains the DevEUI to id the device.
https://lora-alliance.org/resource-hub/lorawanr-specification-v103Other packets would only contain the NetAddr. It would be difficult to map from DevEUI to DevAddr without the network server.
KeymasterKeymasterI thought this article has made the point clear.
What are yor questions regarding the contents of the article?KeymasterIt is both.
KeymasterI do not see the issue with using either term to describe the devices capabilities.
IOT uses M2M communication to provide a service.
Keymasterhttps://www.multitech.com/products/embedded-m2m-modems
Both units are able to communicate via serial AT commands. Any micro-controller with a serial peripheral could be used.
mDot datasheet
http://www.multitech.com/documents/publications/data-sheets/86002171.pdf
xDot datasheet
https://www.multitech.com/documents/publications/data-sheets/86002182.pdfBoth modules are programmable and could be connected directly to digital and analog sensors.
https://os.mbed.com/platforms/MTS-mdot-f411/
https://os.mbed.com/platforms/MTS-xDot-L151CC/Key differences.
mDot has a 100 MHz processor and external flash
xDot has a 32 MHz processor with no external flashBoth have SPI, I2C, digital, analog and serial interfaces.
KeymasterIt does not sound like the unit is operating correctly.
Please open a case at support.multitech.com to share device configuration and logs.KeymasterDid you restart the lora services after adding the second sensor?
Device credentials are stored at this API end-point.
https://192.168.2.1/api/loraNetwork/whitelistThe current configuration in use by the network server, including the whitelist of device credentials is accessed through this API.
https://192.168.2.1/api/lora/configIf a device is in the whitelist of /api/loraNetwork but not in api/lora/config a restart of the network server is needed.
KeymasterThe mdot is a single channel device. Packet forwarder software does not communicate with a dot over USB.
The packet forwarder uses the concentrator card to listen on 8 frequencies and 6 datarates creating 48 virtual 125 khz lora channels.
The gateway can also transmit lora packets.
An app on the gateway can also transmit packets.The ipol setting for pkt fwd json will need to be set to true for other gateways to hear.
https://github.com/Lora-net/packet_forwarder/blob/master/PROTOCOL.TXT-
This reply was modified 6 years, 1 month ago by
Jason Reiss.
KeymasterUsing 867.5 will create channels on 867.1-867.9
The default frequencies are at 868.1, 868.3, and 868.5
While supporting the default channels it is not possible to also support both 867 and 869 ranges.KeymasterUplink packets can be repeated, however this will break downlinks as the Rx windows are not longer in-sync with the network.
The gateways and network would need knowledge of a repeater protocol to be fully functional in a LoRaWAN network. There is no such functionality available in current firmware.
KeymasterWhen you say “restart” the Conduit are you doing a graceful shutdown and restart or pulling the power cord?
When the power is cut recent sessions may be lost as they have not been written to flash.
The database is held in RAM and backed up to flash periodically. The default period is hourly and can be reduced to ten minutes. This process reduces the flash wear. The trade-off is loss of session if power is cut. On normal restart or reboot the database is automatically backed to flash.
Backup command info
Backup interval info
http://www.multitech.net/developer/software/aep/lorawan-aep/lorawan-network-settings/April 12, 2019 at 7:11 am in reply to: lora-packet-forwarder not running at reboot with lora-network-server #27624KeymastermLinux does not have a supervisor process by default like AEP.
monit could be used to ensure the packet forwarder process is running and restarted if it exits.
The forwarder may have failed to start or quit during boot.
KeymasterThe application can send an ADRLinkReq to the end-device to set the datarate.
Using port 0 MAC commands can be sent, send 0330ff0001 to set to DR3 and first 8 channels enabled. The mask will need to match the configured channels.Or the device can be configured to use DR3.
The ADR algorithm may reduce the datarate if there are issues receiving downlinks. This may cause your device to be unable to transmit a larger payload. Your end-device may need to enforce a minimum datarate to avoid being stranded.KeymasterOthers have had success using monit.
KeymasterPlease see info here and complete the contact form.
https://www.multitech.com/bands/lensKeymasterThe lora-out node will accept a buffer or a UTF string.
var data = new Buffer("010203", "hex"); var msg = { "eui": "1122334455667788", "payload": data }; return msg;KeymasterIn the network section of the config the defaultProfile can be set for devices joining with NetworkID and NetworkKey. This setting is resetting the device back to A on re-join.
“defaultProfile” : “DEFAULT-CLASS-A”,
Change to class C for devices to join as class C.
“defaultProfile” : “DEFAULT-CLASS-C”,Otherwise using the whitelist local keys each device can be configured to a specific class when joining.
KeymasterIt is listed at the bottom of the post.
Default Key: 2b.7e.15.16.28.ae.d2.a6.ab.f7.15.88.09.cf.4f.3c -
This reply was modified 6 years, 1 month ago by
-
AuthorPosts