Jason Reiss
Forum Replies Created
-
AuthorPosts
-
Jason Reiss
Keymastermsg.payload = "31";This will send two bytes, 3 and 1 in ascii as 0x33 and 0x31 shown below.
The downlink format is [TYPE][DEVADDR][FCNT][PORT][PAYLOAD]at+send hello
018856a20005000000013331OK
End of packet is
Port: 01 Payload: 3331To send only one byte.
msg.payload = new Buffer("31", "hex");at+send hello
018856a2000a0000000131OK
End of packet is
Port: 01 Payload: 31Port is an int and ack is a bool.
msg.port = 1 ; msg.ack = true;KeymasterSabri,
The current hardware still does not support hw float point operations required for newer versions of node-red.
We are working on updated hardware platforms that should be available later this year.
KeymasterThere is an id associated for each message to correlate the ACK.
lora/11-22-33-44-55-66-77-88/1/down_queued {
…,
“id” : 752,
…
}lora/11-22-33-44-55-66-77-88/1/packet_sent {
…,
“id” : 752,
…
}lora/11-22-33-44-55-66-77-88/packet_ack {“seqn”:2, “id”: 752}
KeymasterCould you explain more on what “some sort of my own correlation id” could mean?
There are MQTT topics available from the network server.
down_queued – occurs when a downlink packet is successfully queued by an application.
packet_ack – occurs when the network server receives an uplink with acknowledgement of successful receipt of a downlink packet.
KeymasterHave a look at the mPower 6.0.0 release
https://www.multitech.com/documents/publications/sales-flyers/mPower%20Software%206.x.x%20Conduit%20Gateways.pdf
https://www.multitech.com/documents/publications/software-guides/s000727–mPower-Edge-Intelligence-Conduit-AEP-software-guide.pdfThere is the Administration > MQTT Broker > MQTT Bridge Configuration with authentication using the device certificates or imported certificates.
There is also LoRaWAN > Network Settings > Default App that can be configured to connect to a remote broker.
https://multitechsystems.github.io/lorawan-app-connectKeymasterCheckout this command to see how to create a device profile.
$ lora-query -x helpThen assign to an existing device record or whitelist entry.
KeymasterThe LoRaWAN > Network Settings > Payload Broker should be left as default 127.0.0.1 and 1883 to use the local broker that the node-red application can also subscribe to.
Then in node-red you will connect to a remote broker to send to.
KeymasterWhat is the mPower version you are using?
Do you receive the ACK in Rx2?
The example shows a packet with FCNT 2. Can you provide later packets around 6 or 7?
What is the rssi/lsnr values received by the gateway?11:37:17:296|DEBUG| ED:31-30-34-37-5d-38-86-08|PACKET-TX|ADDR: 0149e6a7 PORT: 0 ACK: 0 FCNT: 00000002
This shows ADR is enabled and the average SNR is 7.2 and DR5 should be assigned eventually.
11:37:15:782|DEBUG| ADR|SNR: 72 AVG: 72 DR: 5 SEQ: 2
11:37:15:782|INFO| ED:31-30-34-37-5d-38-86-08|FCTRL|ADR:1 ADRACK:0 ACK:0 CLASS:A OPTS:0 LAST-PKT: 120009 msKeymasterI suggest creating a ticket at support.multitech.com for further help.
See section 3.4.4 Register the Device
https://www.multitech.com/documents/publications/marketing-guides/MultiTech_Getting_Started_Guide_for_AWS_LoRaWAN.pdfKeymasterWhat frequencies did you see in server mode?
What Frequency Sub Band was configured for server mode?The frequencies are sent to the gateway from the AWS network server when basic station mode is used. Is there configuration available for the gateway in AWS?
I did not see a device manual on the linked page. You may need to contact the device manufacturer.
KeymasterDo you see uplinks from the device?
Did it work when you configured the local network server?KeymasterWhat region are have you configured the gateway for?
8 channel configuration would only help a US915 or AU915 device.Do you have a manual for the device?
KeymasterIf gateway is connected and uplinks are received, there should be no further gateway configuration needed.
An end-device may need to be limited to only 8 channels to help join.
Default may have 64 channels enabled.What end-device are you trying to connect?
What firmware or library is being used?
Have you added the device to the AWS network server?KeymasterThe device DevEUI and AppKeys would need to be added to AWS LoRaWAN services.
Is there a gateway status in the AWS cloud that shows the gateway is connected?
I suggest creating a ticket at support.multitech.com for further help.
KeymasterWhat LoRaWAN network service have you configured basic station to connect to?
| I was able to connect the gateway, but not the devices
You may want to create a support case to share your configuration and logs with our team, support.multitech.com.
KeymasterBasic Station does no use local keys, they only work with network server mode.
All packets are sent to the remote network server configured with basic station.
The end-devices need to be provisioned with the remote network service.There is an updated firmware that will hide the rest of the LoRaWAN menu items when packet forwarder or basic station is selected.
Sorry for any inconvenience.
KeymasterNormally packets scheduled and sent by the network server will be target at the end-devices. These packets are transmitted with reversed polarity so that other gateways do not see them and they do not interfere with end-device uplinks. The network server schedules transmission and regulates the duty-cycle of the gateway transmitter where required by law.
The MQTT message to the network server can only be used to queue packets to end-devices. RAW lora messages cannot be queued or transmitted.
One possibility is to use an MTAC-XDOT card as a secondary transmitter configured as an end-device connecting to the central Conduit via LoRaWAN.
KeymasterAT Firmware has the AT+TM!=1 command to enable the test mode.
A custom firmware would need to implement the test mode to support certification. It is not built into the library.
KeymasterIf it is configured correctly is should work, otherwise it will not.
If you configure the Network Interfaces > br0 to be a DHCP client
Also turn off the DHCP server.When you plug into the home router is should get an address and DNS entry to reach the internet. You could then log into the home router to find the IP address that was assigned. Or you could scan the network from your PC to find the mac address on the label of the MTCAP.
If you need more help with the settings feel free to open a ticket at support.multitech.com
January 27, 2022 at 3:00 pm in reply to: Programming Channel Plan at runtime as opposed to compile time #32326KeymasterThey should both work the same and create the same channel plan.
The new ones are better to use, the old ones should not be used for new stuff.The new ID’s have a bit field to specify that the plan is a dynamic vs fixed channel plan. US and AU are the only fixed plans, all the channels are provided by the plan, no channels can be added. Dynamic plans are EU,IN,AS, etc.. where new channel are sent in a join accept.
KeymasterShow loaded plan
AT+FREQChange to EU868
AT+DFREQ=EU868
AT&WP
ATZChange to US915
AT+DFREQ=US915
AT&WP
ATZKeymasterhttps://github.com/MultiTechSystems/Dot-AT-Firmware
For xDot the global plan provided with 4.1.2 would be needed to change the channel plan through commands only.
Other wise the channel plan specific firmware must be used, i.e. load US915 for use in NA.
KeymasterWhat channel plan are you using?
Do you have ADR enabled?In LoRaWAN 1.0.4 the network controls the number of retries when ADR is enabled.
Perhaps the settings is being overridden by an ADR MAC Command?You could try to call setACK before each send.
What LoRaWAN network are you communicating with?
KeymasterMissedAck retries should be the current number of retries attempted.
If you miss the first ACK is should be 0
If you miss the second ACK is should be 1
…KeymasterSee getAck in the header file to retrieve the value that is set.
https://github.com/MultiTechSystems/libxDot-dev/blob/master/mDot.hThere are events for missed ACK that shows number of retries, and PacketRx gives the number of total retries when ACK is received.
https://github.com/MultiTechSystems/libxDot-dev/blob/master/mDotEvent.hJanuary 12, 2022 at 9:06 am in reply to: Programming Channel Plan at runtime as opposed to compile time #32301KeymasterThe latest commit to the dev libraries will skip this check.
[WARNING] New ChannelPlan detected…A changed channel plan will need to perform a join if the session does not match. The application has a better chance of detecting and fixing this once the dot instance is configured.
January 11, 2022 at 1:21 pm in reply to: Programming Channel Plan at runtime as opposed to compile time #32300KeymasterDid you enable setPreserveSession? normally the session is reset unless this is enabled.
In the ALL-PLANS AT Firmware we use these settings for saving the channel plan.
https://github.com/MultiTechSystems/Dot-AT-FirmwaresetDefaultFrequencyBand
getDefaultFrequencyBand
saveProtectedConfigKeymasterhttps://github.com/srned/baselib/blob/master/crc64.c
const std::string name = "NETWORKID"; uint64_t crc = 0; crc = crc64(crc, (const uint8_t*) name.c_str(), name.size());https://github.com/nullptr0807/aes128_cmac
const std::string passphrase = "NETWORKPASSPHRASE"; uint8_t key[KEY_LENGTH]; AES_CMAC_CTX ctx; AES_CMAC_Init(&ctx); // default session key is 2b.7e.15.16.28.ae.d2.a6.ab.f7.15.88.09.cf.4f.3c AES_CMAC_SetKey(&ctx, LoRaConfig::defaultNetworkSessionKey); AES_CMAC_Update(&ctx, (uint8_t*) passphrase.c_str(), passphrase.size() & 0xFF); AES_CMAC_Final(key, &ctx);KeymasterWhy would the generated values be better than using the appeui and appkey generated by chirpstack?
January 10, 2022 at 12:36 pm in reply to: After FOTA Firmware Upgrade, MDOT User Register values are lost #32293KeymasterWe will need some time to analyze the issue.
https://os.mbed.com/questions/62192/What-might-cause-RTC-Backup-Domain-Reset/
https://github.com/ARMmbed/mbed-os/blob/master/targets/TARGET_STM/rtc_api.c
-
AuthorPosts