Jason Reiss
Forum Replies Created
-
AuthorPosts
-
Jason Reiss
KeymasterEU868 joins on default channels so they should not be different unless you are in a different region.
Attempts at joining the network are limited by duty-cycle regulations in EU868. The device must wait after each attempt to maintain <1% time on air.
Do you know if the gateway is active?
How near is the gateway?
Is there any obstruction? Line-of-sight will give best chance of reaching.Keymaster125 khz channels may not be allowed by regulation without frequency hopping.
Since P2P uses a single frequency there is no hopping.
Check local regulations for ISM band.
AU borrows from FCC.
KeymasterAfter changing the settings through the API POST to /api/command/save or /api/command/save_restart for the changes to persist.
KeymasterManual ABP session can be installed in both Conduits.
OTA session cannot be shared between network servers as you have seen.Downlinks will be the next issue as the downlink counters will not be in-sync the end-device will reject downlinks with a lower frame cnt.
Better to have a central network server with conduits in packet forwarder mode.
KeymasterP2P uses a single channel specified with tx_frequency.
The call to setFrequencySubBand(0) will have no effect.October 9, 2018 at 11:22 am in reply to: Unable to set remote Management in Conduit AP (GPS Error) #26493KeymasterThe API can be used directly to by-pass the javascript.
https://192.168.2.1/api/remoteManagement?method=PUT&data={"accountKey":"<ACCOUNT-KEY>","enabled":true}Then Save and restart.
-
This reply was modified 6 years, 8 months ago by
Jason Reiss.
KeymasterIf the Join Accept is being received at the gateway but not the end-device I would suspect a timing issue.
Have you set the sync-word and join delay properly?
AT+PN=1
AT+JD=5October 9, 2018 at 7:29 am in reply to: Upgrade config from saved config gives conflict in LoRa #26490KeymasterThe packet forwarder configured in MANUAL mode can have a placeholder for the gatewayID.
Any text between the angled brackets will be replace with the hardware EUI.
“gateway_ID”: “<WILL-BE-REPLACED-WITH-LORA-EUI>”,We will look to include a similar option for the NORMAL config mode in a future release.
KeymasterThe machine type can be provided on the command line as follows with the image to build.
~/mlinux/build$ MACHINE=mtcap bitbake mlinux-mtcap-image
KeymasterWhat was the range used between the end-device and gateway?
What is the success ratio at +50m?
Perhaps the preamble sync-word detect gives some false positives when the signal power is very high.I have seen ~10% success with mismatched sync-word as well when testing at my desk at close range.
KeymasterLooks like /api/v2/test needs authentication although the doc says it shouldn’t.
KeymasterTry setting header “Content-Type” to either “application/vnd.api+json” or “application/json”.
October 3, 2018 at 7:32 am in reply to: Can't enable DeviceHQ on MTCDT-H5-210A: "Invalid GPS Data Interval" #26443KeymasterI concur there is a javascript issue. If the device does not have gps capabilities the interval was set to 0. The form validation does not allow the 0 setting. The gps interval validation was added in the last release.
Thank you for the report.
KeymasterDoc of AT+SENDB on page 79 shows possible data received from the network to be printed before the OK following an AT+SENDB command.
http://www.multitech.com/documents/publications/manuals/s000643.pdf
You can disable waiting for rx windows before AT+SENDx commands return if ACKs are not enabled.
AT+TXW=0Keymasterhttps://os.mbed.com/platforms/mts-mdot-f411/
Printf should not be used in ISR context. I assume you added these after it stopped working.
PA_0 is the default wake pin. Perhaps another pin.
September 28, 2018 at 9:27 am in reply to: How to configure LoRaWAN parameters programmatically in AEP environment #26424Keymaster
http://www.multitech.net/developer/software/aep/conduit-aep-api/requests/
http://www.multitech.net/developer/software/aep/conduit-aep-api/collection-endpoints-conduit/
http://www.multitech.net/developer/software/aep/conduit-aep-api/collection-endpoints-conduit/loranetwork/
http://www.multitech.net/developer/software/aep/conduit-aep-api/commands-conduit-aep/KeymasterNode-red lora-out node should have doc in the right pane when the UI is activated.
msg.payload and msg.eui can be set in the message to queue the downlink.
MQTT message lora/EUI/down can be sent
Command line options
# lora-query -x helpKeymasterMTAC-LORA-H-915 or MTAC-LORA-HL-915 is needed for KR920 with LBT
The v33 firmware will also need to be loaded.To install the v33 FPGA image on Accessory Port 1
# mts-fpga-loader -i /usr/lib/mts-flash-binaries/mtcdt-fpga-v33.hex -p1KeymasterThe AT+DLC command reports the FCNT from the last received packet. In the case of the first downlink the FCNT may be 0.
KeymasterStrings containing NULL or other special characters may have issues being printed to the terminal. This is why the HEX output is available.
AT+SD will provide the raw data correctly.
KeymasterThe first downlink from the network server may be network setup MAC commands for Channel Mask or Additional Channels.
KeymasterIf the power was pulled from the Conduit rather than a clean shutdown joins could be lost before they were able to be written to flash.
Our latest firmware AEP 1.6.2 as well as the last 1.4.17 has a setting to control the length of time between database backup.
If you need further assistance our support team is also available at https://support.multitech.com
KeymasterAn Ethernet connection is required. Packets are forwarded via UDP.
KeymasterHave a look at the troubleshooting guide to diagnosis any hardware issues.
KeymasterMark,
You will need to run the apache service bound to an external interface, eth0 address, and not localhost. The localhost address is not available to processes on other network devices.
KeymasterYes the network server conduit can also have a packet forwarder running.
KeymasterVerify that the hardware is running and connecting to the software stack.
Have look at the logs for more info for help in debugging.
Upgrading the firmware would not be a bad idea.KeymasterLooks like Yocto on ARM 32-bit is not supported
https://docs.microsoft.com/en-us/azure/iot-edge/supportKeymasterUse node-red lora-in node or MQTT in an application in node.js, python or c++.
-
This reply was modified 6 years, 8 months ago by
-
AuthorPosts