Jason Reiss
Forum Replies Created
-
AuthorPosts
-
Jason Reiss
KeymasterThe examples are for mDot and xDot. On xDot they will be true.
On mDot the current hardware does not support a deepsleep mode as per the message in the debug console. Therefore only sleep mode will be used with RAM maintained, execution resumes after sleep instead of a device reset.
For low power applications xDot is recommended.
February 20, 2020 at 6:42 am in reply to: seekUserFile MDot API fails, when fetching last byte in the file. #30306KeymasterIt should be signed, that will be an issue for using SEEK_END. I will have to change that in the future.
Can you use the size to seek from the beginning?
KeymasterAT+WM=1 will use the interrupt as the source to wake-up.
Do you use deepsleep AT+SLEEP or stop mode AT+SLEEP=1?
Both should wake only on the configured AT+WP setting.
Is the WAKE pin floating?February 19, 2020 at 8:40 am in reply to: seekUserFile MDot API fails, when fetching last byte in the file. #30293KeymasterDid you try to seek using offset -1 from the end to get the last byte.
KeymasterPlease see the “Deepsleep functionality change” section.
https://os.mbed.com/platforms/MTS-mDot-F411/KeymasterWhat version of firmware are you running?
KeymasterPlease have a look at these documents.
February 15, 2020 at 7:55 am in reply to: lora-packet-forwarder cannot find valid configuration #30281KeymasterDid you follow this?
The -HL- is unexpected in the product-id, what does the hw-version field list?
Perhaps this was a sample LBT cardHere is the production version.
https://www.multitech.com/models/94557303LFKeymasterIssue the following API calls and then do the firmware upgrade using the 1.7.4 upgrade.
https://192.168.2.1/api/system?method=PUT&data={"signedFirmwareValidation":false}
https://192.168.2.1/api/command/save?method=POSTAfter the downgrade perform reset to defaults.
KeymasterYes, the CFList will be used if 1.0.3 is specified and there will be no ADR commands in the first downlink.
KeymasterIt is defined in LoRaWAN and explained precisely in the Regional Parameters specification. The downlink channel is correlated to the uplink frequency by using modulus 8 on the uplink channel index.
Downstream – 8 channels numbered 0 to 7 utilizing LoRa 500 kHz BW at DR8 to 845DR13) starting at 923.3 MHz and incrementing linearly by 600 kHz to 927.5 MHz
Both US915 and AU915 have eight downlink channels. They are 500 KHz width with 600 KHz spacing.
See pages 21 and 25 of LW1.0.3
https://lora-alliance.org/sites/default/files/2018-07/lorawan_regional_parameters_v1.0.3reva_0.pdfKeymasterI do not see a Rev B for 1.0.3 on the lora-alliance.org resource hub.
The supported values for MAC Version are “1.0.2”, “1.0.3” and “1.0.4”
The region version does not change LNS behavior.1.0.2 Rev B (“1.0.2”) is the default behavior.
Class B is implemented with “1.0.3” definitions regardless of MAC setting.KeymasterYou will need to do the firmware upgrade with 5.1.2 to restore the suders file. Factory reset only affects the config partition.
KeymasterThe user created through commissioning mode should be able to elevate to sudo.
Try after login through ssh.
$ sudo -sKeymasterThanks for the topic and follow-up.
KeymasterThe ARMCC compiler appears to optimize memory better and reduce image sizes.
We use the ARMCC compiler for production builds.Keymaster________$$$$
_______$$__$
_______$___$$
_______$___$$
_______$$___$$
________$____$$
________$$____$$$
_________$$_____$$
_________$$______$$
__________$_______$$
____$$$$$$$________$$
__$$$_______________$$$$$$
_$$____$$$$____________$$$
_$___$$$__$$$____________$$
_$$________$$$____________$
__$$____$$$$$$____________$
__$$$$$$$____$$___________$
__$$_______$$$$___________$
___$$$$$$$$$__$$_________$$
____$________$$$$_____$$$$
____$$____$$$$$$____$$$$$$
_____$$$$$$____$$__$$
_______$_____$$$_$$$
________$$$$$$$$$$KeymasterLoRaWAN > Network Settings > Queue Size
The setting is per device.
Max number possible to be queued depends on the number of devices and size of packets.There is 8MB of space for config, LNS DB and custom apps to share.
The size of each packet and meta-data in the queue id less than 500 bytes so 2000 would take up less than 1MB of NVM.
If more packets need to be stored the application could store them in the file system outside of /var/config/ they would be lost on firmware upgrade.
/var/oem/ could be used by the app to survive reboot and upgrade. It is another 8MB partition used for custom defaults.
Or an SD card can be installed and the LNS DB moved to it.January 23, 2020 at 7:52 am in reply to: how can i resend message until receive ack? (when channel is busy)) #30189KeymasterWhat Channel Plan is being used?
The “channel is busy” would only be expected if LBT is enabled.retransmit an unacknowledged packet
This is correct, if the packet was acknowledged there would be no retransmission. Perhaps you are confusing with Confirmed/Unconfirmed Uplinks.
KeymasterWhat is your at+txdr setting?
DR6 and DR7 will need additional channels to be used.
KeymasterThis has been discussed many times before.
The hardware does not support hw floating point operations, sw floating point was last supported in node.js in the installed version v0.10.48, node-red v0.15.3 is the last version available.An updated gateway will be available this year.
KeymasterWe do not have an mDot specific library at this time to support LoRaWAN 1.1
ARM mbed has a LoRaWAN 1.1 stack that can run on mDot.
https://os.mbed.com/blog/entry/Introducing-LoRaWAN-11-support/January 20, 2020 at 7:44 am in reply to: RTC Synchronization error in MDOT after a successful flash of firmware. #30174KeymasterDoes it still occur after a power cycle (pulling power)?
KeymasterThe mosquitto.conf file would configure the local broker settings.
The local broker delivers packets from the network server to node-red.The connection from node-red to the cloud will not be affected by the local broker settings.
What QoS setting does the MQTT out node use?
KeymasterIt still does not match.
Try changing “filename” to “fileName” and “size” to “fileSize”.KeymasterThe json provided to the curl command did not match the UI call.
{“info” : { “fileName” : “MTCAP_5.1.2_upgrade-signed.bin”, “fileSize” : 106219520 }}KeymasterAny difference in the api.log between using API and GUI?
You could also look at the API calls being made by the Web GUI for differences.KeymasterBe sure you have the latest firmware version.
MTDOT-BOX-EVB-3.1.2.bin is available here.
https://github.com/MultiTechSystems/Dot-AT-Firmware
If LoRaWAN Public is selected on Conduit.
AT+PN=1
AT+JD=5
AT&WKeymasterThe xDot and mDot are LoRaWAN certified end-devices. They can connect with any LoRaWAN Network. By default the latest firmwares should be able to join a public network after setting the AppEUI/JoinEUI (AT+NI) and AppKey (AT+NK).
Can you share any of the multiple sources so we can work to correct this?
There is a private LoRaWAN MTS specific network mode with different default join delay of 1s for all plans and differing downlink channels for US/AU channel plans. This would only work with Conduits, but it is no longer the default.
KeymasterIn a REST API POST is used to create a resource, i.e. add an item to an array.
To change an existing resource, such as the network collection, PUT should be used.
curl 127.0.0.1/api/loraNetwork/network -X PUT -H "Content-Type: application/json" -d '{"public":1}' -
AuthorPosts