Jason Reiss
Forum Replies Created
-
AuthorPosts
-
Jason Reiss
KeymasterWhat has changed?
What xDot firmware version are you using?
Change the network server logging to forward to file with TRACE level and look at the log for more info.KeymasterThe hardware can output up to 100mW. EU868 regulations limit most frequencies to +14 dBm ERP with the exception of 869.525 MHz.
March 21, 2020 at 11:44 am in reply to: Conduit unable to recover from loss of cellular connection until restart. #30472KeymasterNot sure where the old doc went.
https://www.multitech.com/brands/multiconnect-conduit
Normally I look the the calls made by the UI in a browser debug window to see json examples of API calls.
March 20, 2020 at 5:09 pm in reply to: Conduit unable to recover from loss of cellular connection until restart. #30470KeymasterAPI doc is here.
You may want to open a ticket to share logs, config, model and firmware info.
https://support.multitech.comKeymaster“ftime” and “etime” fields carry the nS timestamp info for TDOA
March 19, 2020 at 5:05 pm in reply to: Unable to winscp into the new gateway using SFTP protocol. #30465KeymasterThe ssh configuration is on the Administration > Access Configuration page.
Options include allowing access over LAN or WAN. Depending on your network configuration WAN may need to be enabled.I was able to use WinSCP to mPower 5.1.5 with SSH enabled.
The built-in UI help has configuration descriptions and a search feature.
https://192.168.2.1/help/index.htmKeymaster– What is the reproduce steps for this issue ?
Configure the Conduit in lora packet forwarder mode.
After /var/log/lora-pkt-fwd-1.log file grows to 512K logrotate will try to copy the file, create a compressed version and HUP the processes.
The logrotate script fails as the lora-network-server is not running. This leaves a lora-pkt-fwd-1.log.1 file left uncompressed. The next time logrotate runs it will quit because this file exists. The original lora-pkt-fwd-1.log file will continue to grow taking up RAM as the log directory is in a RAM disk.– What is the reproduce rate ?
100% of MTCDT/MTCAP configured in packet forwarder mode– Is there any workaround like restarting the gateway once every day ?
Yes restarting the gateway will clear all log files– Does this issue happen when the pkt_fwd process is restarted every day ?
Restarting the pkt_fwd will not clear the log files.– Can we disable pkt fwd log to avoid this issue (Remove “-l $pkt_fwd_log” from lora-network-server)
Yes this would avoid the issue. Otherwise an IPK can be installed to correct the logrotate scripts a link is provided on the changelog downloads page.March 18, 2020 at 4:33 pm in reply to: Unable to winscp into the new gateway using SFTP protocol. #30448KeymasterI tested with an ssh/sftp client on my phone and it works with ssh server enabled.
March 18, 2020 at 4:28 pm in reply to: Unable to winscp into the new gateway using SFTP protocol. #30447KeymasterDid this work on previous firmware versions?
admin@mtcdt:~$ opkg list | grep ftp
inetutils-ftp – 1.9.4-r0.0
kernel-module-nf-conntrack-ftp – 4.9.87-r11.1
kernel-module-nf-nat-ftp – 4.9.87-r11.1
openssh-sftp-server – 7.5p1-r0.mts5.0admin@mtcdt:~$ ps aux | grep ftp
admin 18527 0.0 0.4 3092 1120 pts/0 S+ 17:22 0:00 grep ftpKeymasterP.S. The unit is being used with Actility, which I’m unsure if this causes issues.
Actility units have custom firmware built on mLinux. They will not have a webui or respond to factory reset.
If you need to change the gateway and still access the Actility network, please contact Actility for assistance.
If you want to replace the firmware to re-purpose the device please contact support.multitech.com.
KeymasterPackets can be rxd and txd during the scan.
It is not resource intensive.We have occasionally seen the scan get into a stuck state in the hardware. If the scan does not exit cleanly it will be due to this.
The normal packet forwarder still functions but further scanning is not possible until reset of the gateway card / packet forwarder.
KeymasterThe EUI is stored in external flash on mDot. The libmdot-mbed5 library has getDeviceEUI to get the EUI from the flash.
Are you wanting to use another lorawan stack?
This project uses the mbed-os stack with the EUI from flash.
https://github.com/MultiTechSystems/mbed-os-lorawan-tinyshell-
This reply was modified 5 years, 2 months ago by
Jason Reiss.
KeymasterPort forwarding should be preferred. It will survive a firmware update. Your conf change will be reset if/when you update the device.
Keymaster3.3.5 is released
KeymasterThe MQTT broker on Conduit is setup on the localhost interface only.
You could setup a VPN tunnel or use port forwarding to access the broker from outside.
Be sure to address any security ramifications of opening ports to the Internet.An other option is to put a custom application to push messages to a remote server using python.
Here is sample lora echo client, the code to push to an outside broker would need to be added.
https://github.com/trong63/python_mqtt_sampleKeymaster$ sudo
Or
$ sudo -sKeymasterI suggest opening a ticket at support.multitech.com to share screenshots and gateway log files.
KeymasterIn the Packets table you should see the UpUnc packet and a DnUnc packet.
Do you see only UpUnc packets?KeymasterIs the device sending periodic uplinks? A class A device will only receive after sending an uplink.
Does the downlink disappear from the queue?
Do you see a downlink packet on the Packets page after queuing the downlink?I am not familiar with that module and its operation to comment on ports to use or format of payloads.
KeymasterPlease open a ticket as support.multitech.com for more assistance.
KeymasterUse the downlink queue to send unicast messages.
This can be done programmatically through MQTT.The operations page is for devices supporting lorawan multicast and fuota applications. Details can be found in the technical documents here. Not all devices will have support this.
KeymasterGood to hear. Let us know if you run into any other issues.
KeymasterWhat firmware version are you using?
Does the one JnReq match the DEV-EUI of your device?
Did you restart the network server after adding the device credentials?
Did you try a Save and Restart of the gateway?Do not set the channel mask if you are unsure, the default is blank and the network server will choose the correct mask. The setting is only needed if you are networking multiple gateways to cover additional channels.
KeymasterWhat is the output of help and at&v?
Sounds like a bad connection if commands are missing.
Is it custom at firmware?Keymaster5.0.0 api may not return all results because of a bug.
These 3 end points should return different results. The first lists up and down packetshttps://myip/api/lora/packets
https://myip/api/lora/packets/up
https://myip/api/lora/packets/downKeymasterWhat firmware version is running?
KeymasterI am able to compile this package in mLinux. The avahi depends are also built.
MACHINE=mtcdt bitbake -c compile libnss-mdnsKeymasterIf there were missing records there would be a null as the last item in the array if I remember correctly.
KeymasterWhat version of AEP are you running?
There was an issue with returning large arrays of data from the network server through the API in a previous version, should have been addressed in 5.1.2.Best would be to push the data from the gateway to a remote server.
KeymasterHow often is the API being queried?
How many packets are returned?
How many packets are missing? -
This reply was modified 5 years, 2 months ago by
-
AuthorPosts