[Jason Reiss]

Look for Semtech LoRa modulation.

[Jason Reiss]

You can try to access the device through the USB Device port on the back of the unit. Connect with a terminal emulator at 115200. Login with the same creds as ssh.

[Jason Reiss]

If you have an internet connection and run
> opkg update
> opkg install openvpn

It will install that package for you to try.
I don’t know if anyone has.

[Jason Reiss]

Tom,

Could you open a support case on support.multitech.com regarding the lora server crash and share your mote configuration to try to reproduce the error.
Network Address and keys used for ABP and commands used to enter mote into database?

Thanks,

Jason

[Jason Reiss]

Did you remove power from the UDK?

[Jason Reiss]

Jose,

For RF level testing you may need to make custom firmware using SxRadio libraries.

Through AT commands and the mDot library only LoRaWAN supported functionality will be available.

Here are some examples and libraries.

https://developer.mbed.org/users/dudmuck/

Also checkout the datasheets at Semtech.com for radio information.
http://www.semtech.com/apps/product.php?pn=SX1272

[Jason Reiss]

Are you trying to communicate with a LoRaWAN gateway? The AT-Command firmware and libmDot library are setup to use the LoRaWAN 1.0 communcation protocol which uses only LoRa and FSK modulations. The bandwidth is determined by datarate which must match the receiving entity.

If you want to use the Sx1272 radio on the mDot for communcations other than defined in LoRaWAN it will be better suited for you to use mbed and a SxRadio driver. All SxRadio drivers I have used employ settings for only LoRa and FSK modulations. GMSK would have to be added into them.

The following link has examples of an SxRadio tx and rx for mDot.
https://developer.mbed.org/users/dudmuck/

[Jason Reiss]

You could issue AT until OK is received.

[Jason Reiss]

What frequencies are used by the gateway.

Try AT+FSB=1 to use only the first 8 channels of US915

With AT+FSB=0 the mDot will use 64 channels and choose randomly between them.

The AT+RXDR command is not needed. The lora mac layer will choose the correct datarate depending on AT+TXDR setting and Rx window.

[Jason Reiss]

Just swap the pins.

Serial debug(XBEE_DOUT, XBEE_DIN);
mts::MTSSerial serial(USBTX, USBRX, 512, 512);

[Jason Reiss]

lora-query will be run on the command line. It will open UDP session and issue command and give result. It makes it easier than using the “nc -u localhost 6677”.

# lora-query -t 5000 -s -n

[Jason Reiss]

Also lora-query

Usage: lora-query [-t timeout] [-s] [-n]
Simple UDP client utility to pull info from LoRa Network server
–timeout (t) : UDP recv timeout, default: 100 (msecs)
–stats (s) : get LoRa Network server statistics
–stats-reset (r) : reset LoRa Network server statistics
–node-list (n) : get Node List
–json (j) : data in json format
–help (?) : returns this message
–version (v) : print version

[Jason Reiss]

node list

[Jason Reiss]

I found the issue with the config.
Backup interval must be a number, not a string.

“backupInterval”: 21600,

[Jason Reiss]

OK, things are running?

[Jason Reiss]

When I copy and paste from the above post there are some bad quote characters. Are these in the file on the Conduit?

Here they are replaced with ‘?’ characters:

{                                                   
    "db": "/var/config/lora/lora-network-server.db",
    "backupInterval": "21600?,                      
    "lora": {                                     
        "netID": "010203?,                        
        "frequencyBand": "915?,                   
        "frequencySubBand": 7,                    
        "rx1DatarateOffset": 0,                   
        "rx2Datarate": 12,                        
        "maxTxPower": 14,                         
        "frequencyEU": 867500000                  
    },                                            
    "udp": {                                      
        "appPortUp": 1784,                        
        "appPortDown": 1786                       
    },                                            
    "addressRange": {                             
        "start": "00:00:00:01?,                   
        "end": "FF:FF:FF:FE"                      
    },                                            
    "network": {                                  
        "public": true,              
        "leasetime": 1440,           
        "name": "BGLORANETWORK",     
        "passphrase": "BGLORANETWORK"
    },                               
    "mqtt": {                                     
        "enabled": true,                          
        "host": "127.0.0.1?,                      
        "port": 1883                              
    },                                            
    "log": {                                      
        "console": true,                          
        "syslog": false,                          
        "level": 30,                              
        "path": "/var/log/lora-network-server.log"
    }                                             
}

[Jason Reiss]

Another thing to do is check that the lora-network-server.conf file is in proper form. You can copy and paste the contents to jsonlint.com to verify it is still in json format. Fix any errors and copy/paste the file back.

• This reply was modified 8 years, 6 months ago by Jason Reiss.

[Jason Reiss]

Did you change passphrase?

[Jason Reiss]

Try stop and then start instead of restart.

[Jason Reiss]

What does the log show?

[Jason Reiss]

You can check /var/log/lora-network-server.log.

It will mention the short name and passphrase.

Have you modified lmic for 8 channel operation?

[Jason Reiss]

Network name and passphrase need to be at least 8 characters.

[Jason Reiss]

Check
# ps -A | grep lora

Make sure lora-network-server is running.

[Jason Reiss]

Command should be
nc -u localhost 6677

[Jason Reiss]

Can you post an example of the node add command you issued?

Also post the command you use to connect to command port.

[Jason Reiss]

What settings do you have on conduit?

[Jason Reiss]

You could also try to create a simple mbed program that just echos the serial input and try each interface in the program to trouble shoot without the AT firmware.

Serial Port pins: XBEE_DOUT, XBEE_DIN
USB Port pins: USBTX, USBRX

#include "mbed.h"

Serial pc(USBTX, USBRX); // tx, rx
// Serial pc(XBEE_DOUT, XBEE_DIN); // tx, rx

int main()
{
    pc.baud(115200);
    
    pc.printf("hello\r\n");
    
    while(1) {
        if(pc.readable()) {
            pc.putc(pc.getc());
        }
    }
}

[Jason Reiss]

At commands issued to the serial port.

USB is debug output only.

There is a bootloader on the USB that is accessible if you press enter key right after reset.

[Jason Reiss]

AT-Commands will be accessible on the serial port of a UDK board.

On the usb port of the UDK board debug output can be seen if enabled.
Use AT+LOG=6 for the highest level of output.

Be sure flow control is off.

I use minicom on mac. I did try CoolTerm and was able to access at command port.

The light on the UDK will be red until firmware is flashed, that is OK.

[Jason Reiss]

When the network server is shutdown all the database is saved to flash and reloaded on boot with all node session keys still intact. Nodes should not have to rejoin the network after a reboot.

Let us know if it is actually the case and we will address that.

Under what scenario would a Node-RED app that has been installed and running need to be rebooted? There may be an issue with other systems of the device not functioning properly. Perhaps the full reboot would be the appropriate action.

[Author]

Posts