Jason Reiss
Forum Replies Created
-
AuthorPosts
-
July 25, 2016 at 11:46 am in reply to: Public/Private messages coming through when they shouldn't… #14294
Jason Reiss
KeymasterWe have seen occasional messages get through with mismatched settings.
The sync word is a single byte. If there is interference and the sync word is corrupted to match the other sync word it will be forwarded.
That is the only possibility as the sync word is a filter at the radio front end.
July 22, 2016 at 11:17 am in reply to: AEP Max number of packets per MDot & Clearing packets. #14283KeymasterCombining packets is not a feature of the network server.
A clear message can be sent via MQTT to the network server.
July 19, 2016 at 12:56 pm in reply to: No output on Conduit packet forwarder to Conduit Network Server setup #14245KeymasterIt is not exposed because the network server downlink routing via multiple gateways is still experimental. Results may not be as expected but should mostly function.
KeymasterAfter Send the MacEvent will fire for TxDone and RxTimeout (not packet received) or RxDone (packet received).
recv() does not need to be called it is used to retrieve the data in blocking operations.
See libmDot headers for event info.
https://developer.mbed.org/teams/MultiTech/code/libmDot/file/121e4c454964/LoRaMac/LoRaMacEvent.hKeymasterJust one call to mdot->recv is needed.
The windows will be opened behind the scenes.Otherwise see lines 46 and 754 to handle receive asynchronously with a custom event class.
void CommandTerminal::RadioEvent::MacEvent(LoRaMacEventFlags* flags, LoRaMacEventInfo* info);
https://developer.mbed.org/teams/MultiTech/code/mDot_AT_firmware/file/6a12bf1f6723/CommandTerminal/CommandTerminal.cppKeymasterPlease open a ticket at support.multitech.com so we can exchange configuration and log files.
KeymasterIf you are using OTA join you should only need to define the default channels in order to initiate the join. The network server will pass the additional channels to the device.
The Conduit will be set to listen on the default channels and a user-defined set of additional channels. The default value for additional channels is 869.5 creating channels 869.1,869.3,869.5,869.7,869.9.
The “busy” or “no free channel” may be due to the duty cycle restrictions built into the software. You may need to contact Microchip for more explanation into the behavior.
July 18, 2016 at 7:35 am in reply to: M dot doesnot connect to the gateway and shows failed to join network #14197KeymasterWhat was the command to check the version that you issued?
The response is very strange, perhaps it is a copy paste issue with the command.Try to type this command with two dashes before version.
/opt/lora/lora-network-server --versionOtherwise, it appears that the upgrade was not successful.
Please open a ticket at support.multitech.comKeymasterJuly 16, 2016 at 9:25 am in reply to: No output on Conduit packet forwarder to Conduit Network Server setup #14188KeymasterThe network server is not exposed on the external interface to be connected to by default.
KeymasterThe “nodeQueueSize” is referring to the downlink queue in the lora network server. In this context “node” refers to a LoRaWAN end-point and not a Node-RED node.
KeymasterFirst create a backup and exercise caution as an invalid json format may result in default settings for entire AEP.
You can edit /var/config/db.json and add the “backupInterval” setting to the “loraNetwork” section.
Then in GUI select Commands > Revert Changes
This will load the changed file from flashNow the settings is in the API and will be written to /var/config/lora/lora-network-server.conf
/api/loraNetwork/backupInterval
KeymasterThe database is backed up on stop/restart of the network server and on a configurable interval. (Default: 6 hours, Minimum: 10 minutes)
This setting is not in the AEP gui/api so the default is used.
KeymasterConfiguration for ADR datarate range is not available in the 0.9.2 version of network server installed by default in AEP 1.1.2
Please upgrade AEP to 1.2.2 or the network server to 1.0.8
KeymasterThere is only one channel that the Conduit can receive at DR6:SF7BW250
868.3 is set for SF7BW250.
868.1 and 868.5 will always fail at DR6.
The max datarate for ADR can be configured through the API after logging into the Web GUI.
https://192.168.2.1/api/loraNetwork?method=PUT&data={"lora":{"maxDatarateEU":5}}&apply=now*** Quotes may need to be replace if copied from this web page.
KeymasterYes the led should stop blinking. Did you also borrow the while(true) from the HelloWorld?
Difference between sleep and deepsleep is ~400 uA. RAM is lost in deepsleep and execution resumes at start of main(), as you have noticed, when the program is reloaded from flash.
KeymasterSet “frequencyEU” to define the center of 5 additional channels with 200 kHz spacing.
Getting Started with LoRa Conduit mLinux (LoRa Configuration)
KeymasterDefault is 16 per node.
On AEP the settings can be queried through the API
https://<CONDUIT-IP>/api/loraNetwork/nodeQueueSizeAnd also set
https://192.168.2.1?method=PUT&data={"lora":{"nodeQueueSize":20}}&applyNow=trueIn mLinux it is also configurable in /var/config/lora/lora-network-server.conf
"lora": { ... "nodeQueueSize": 16, ... }KeymasterDo you think the issue is packets not being received by the gateway or the gateway being unable to respond to the packet?
The gateway must adhere to the same time-on-air restrictions as and end device if you are using EU868. Perhaps this is what seems to be inconsistent.
June 22, 2016 at 8:48 pm in reply to: How to register or delete devices in the gateway manually? #13617KeymasterKeymasterKeymasterUsing the network server on conduit it is always a private network.
That private network has two modes “private” and “public”. “private” can be used with mDots, “public” is available for compatibility with 3rd party motes.For a true Public network you would only use the packet forwarder to send lora packet to a cloud server.
KeymasterSee the intro to lora link for details
KeymasterThe public mode is a compatibility mode. The network server is running on the conduit in either case. If you don’t care about the sync word just running the default files in public mode. Nothing will be sent over the internet with default software on mLinux.
KeymasterRun the network server in private mode.
Then copy /var/run/lora/1/global_conf.json to /var/config/lora/ directory.
Then modify /etc/init.d/lora-network-server to start basic_pkt_fwd process with /var/config/lora directory
Run the server in public mode to get matching downlinking and frequencies.
The packet forwarder will keep the 0x12 sync word.
KeymasterThe public mode is compatible with 3rd party devices. The private mode differs in downlinks frequency and join delay.
KeymasterIf I said no, would you still try it?
It should work as long as it doesn’t require authentication. There is no config for username and password.
KeymasterPlease open a ticket at support.multitech.com and we will help you get it back in order.
-
This reply was modified 8 years, 10 months ago by
Jason Reiss.
KeymasterI haven’t run into that issue. Could you provide a code sample?
An example can be found in the mDot AT Firmware application on mbed
https://developer.mbed.org/teams/MultiTech/code/mDot_AT_firmware/file/6a12bf1f6723/CommandTerminal/CmdSnr.cpp -
This reply was modified 8 years, 10 months ago by
-
AuthorPosts