[Ryan Klaassen]

An external flash would need to be added to the xdot to store the firmware image coming down, or a host processor could use extended at+rxo to allow a host processor to reconstruct that binary and flash the xdot. The host processor would need somewhere to store the firmware image.

[Ryan Klaassen]

It can be done from LENS and AEP.

[Ryan Klaassen]

Yes, and fota is fully implemented on the mDot.

[Ryan Klaassen]

The xDot does not have external flash to store the firmware image. We are extending serial data mode so the xDot will send the packets to another processor. That processor will have to reconstruct the firmware image, and then flash it into the xDot using the xDot’s bootloader.

[Ryan Klaassen]

Any success with the port?

[Ryan Klaassen]

you can specify a port using MQTT ex:
snprintf(payload, sizeof(payload), "{\"data\":\"%s\",\"ack\":false,\"port\":%u}", buf, 1);

then publish

mq.publish(NULL, topic, (int)strlen(payload), (void*)payload, MQTT_QOS_1)

[Ryan Klaassen]

The mDot receives on all ports. Port 0 is reserved for mac cmds only. Other ports such as 224 is dedicated to LoRaWAN Mac layer test protocol.

There are ways on the conduit to set the downlink port. What are you using to send lora packets on the conduit?

[Ryan Klaassen]

The ON_SLEEP pin is describe here http://www.multitech.net/developer/software/mdot-software/at-command-firmware-user-guide/ under serial data mode.

The Serial Data mode is designed to work in conjunction with sleep where the mDot wakes up periodically, signals a host, reads data from the serial port, and then transmits it. The mDot can be configured to wake up on a fixed time interval or on an interrupt triggered by the DIO7 pin. When the mDot wakes up in serial data mode, it sets the XBEE_ON_SLEEP pin so the host processor knows when to start transmitting serial data.

[Ryan Klaassen]

I don’t see anything in the code that stands out as the issue.
https://github.com/ARMmbed/mbed-os/pull/4734/files It may have something to do with this pr. In 5.5.4 they eliminated some clears specifically this call __HAL_UART_CLEAR_IT(huart, UART_CLEAR_TCF); on uart_irq

[Ryan Klaassen]

I apologize, I meant what is the INT_USART1_TX_Handler code?

[Ryan Klaassen]

This is the only change I could find on interrupts from 5.5.3 to 5.5.4.
https://github.com/ARMmbed/mbed-os/pull/4676 . What is &INT_USART1_TX_Handler doing?

[Ryan Klaassen]

Does the interrupt go through the ISR without going to sleep?

• This reply was modified 6 years, 1 month ago by Ryan Klaassen.

[Ryan Klaassen]

try setting the mode to pullup or pulldown

[Ryan Klaassen]

Add a bool and set to true on rise of the pin on interrupt. Set to false before sleep. Check if true then the pin was the cause, else it was the rtc.

[Ryan Klaassen]

In AU915 peer to peer, the valid datarates are 8-13.

[Ryan Klaassen]

Was the dot box in configuration mode when trying these two ports? Try typing AT.

[Ryan Klaassen]

It will flash a new mbed program for the mdot.

Here is information:

https://www.multitech.com/documents/publications/manuals/s000612_DB9.pdf

[Ryan Klaassen]

There should be two serial ports enumerated, if only one is coming up which one is it?

[Ryan Klaassen]

Xdot tbd. Mdot will pushed up today.

[Ryan Klaassen]

It may be due to the time it takes to process a packet or when the packet was recv. The timer will keep running until the packet is verified for that device. Once the packet is verified the ack timer gets killed. It may be the device verifies the packet just after the timer expires, where the print happens but the callback doesn’t.

[Ryan Klaassen]

Does the join delay match on both ends? There are a lot of SPIFFS errors as well. Do you normally see this many SPIFFS errors? The flash may be corrupted on the dot.

[Ryan Klaassen]

Here is some example code https://os.mbed.com/teams/MultiTech/code/Dot-Examples/

[Ryan Klaassen]

You can edit the file located in /var/config/lora/lora-network-server.conf
Change the value for eui and key.

Then restart the network server using
$ /etc/init.d/lora-network-server restart

Here is a link for more information.

Conduit mLinux: Advanced LoRa Configuration

[Ryan Klaassen]

There is a key management tab under the LoRaWAN section

[Ryan Klaassen]

at+ni=0,(hex value)
at+nk=0,(hex value)

[Ryan Klaassen]

Do these settings match the conduit?

AT+PN=value (value = Network Setting from your Conduit)
AT+JD=value (value = Join Delay from your Conduit)
AT+FSB=value (915 NA only | value = frequencySubBand from your Conduit)
AT+NI=1,value (value = Network Name for your Conduit)
AT+NK=1,value (value = Network Passphrase for your Conduit)

[Ryan Klaassen]

The dot lib is compiled using a certain version of mbed-os. Make sure the version of mbed-os you are using matches the mbed-os version that the dot lib was complied against.

[Ryan Klaassen]

Configuration can be done using at commands.
Activation mode is at+njm=2 for auto ota
Device class is at+dc=c for class c
Network mode is at+pn=2 for private

[Ryan Klaassen]

The code works on my end. Can you confirm you are using mbed-os-5.4.7 and GCC 4.9?
cmd for GCC arm version: mbed config GCC_ARM_PATH
cmd for mbed-os version: git describe –match mbed-os*

[Ryan Klaassen]

For AT cmds: AT&K Hardware Flow Control AT&K0: disable, AT&K3: enable
For xDot library: int32_t setFlowControl(const bool& on);

[Author]

Posts