Jason Reiss
Forum Replies Created
-
AuthorPosts
-
July 13, 2020 at 11:26 am in reply to: Lora network server option status is "Stopped" and "Disabled" #30928
Jason Reiss
KeymasterAfter downgrading the firmware a reset to default should be applied.
July 13, 2020 at 10:56 am in reply to: Lora network server option status is "Stopped" and "Disabled" #30926KeymasterInstalling 3rd party tools is usually not compatible with the system UI.
Status would be seen on the connected Network Server.> I am trying to use the installer.sh form ResIot and run the sh file in mlinux mode
ResIot may need to provide support for the 3rd party software.
Otherwise perform a firmware update to remove the 3rd party tools and use the default software to check that the hardware is OK before attempting the 3rd party install.
Keymasterhttps://os.mbed.com/docs/mbed-os/v6.0/apis/spi-flash-block-device.html
This API is a block device for NOR-based SPI flash devices that support SFDP.
The Flash part on Dragonfly does support SFDP.
[EDITED FOR CORRECTNESS]
-
This reply was modified 4 years, 11 months ago by
Jason Reiss.
KeymasterWhat type of external flash are you using?
This example uses a block device as storage. This can be one of:
A built-in SPI flash, such as on the FRDM-K82F.
An external block device (one of SPI flash, DataFlash or an SD card).
Simulated on a heap block device on boards with enough RAM.KeymasterUART1 PA9/10 is the at command port.
Thr deveui is at the beginning of the flash eeprom section. An xdot eeprom api can be used to restore.
https://github.com/ARMmbed/mbed-os/blob/master/targets/TARGET_STM/TARGET_STM32L1/TARGET_XDOT_L151CC/xdot_eeprom.hThe 3.3.5 version of library will allow setting and saving deveui to the “protected” config.
Or contact support.multitech.net for an at cmd firmware working on the debug port.
KeymasterIs this on an mPower firmware?
Inbound connections are not allowed by default.
Check the firewall settings and open a port.KeymasterUsing Default DR as 4
Are you sure default is not DR0 (SF10BW125)? This is limited to 11 bytes payload minus any MAC commands that need to be sent.
When the network sends commands to the end-device it will expect answers in the header of the next packet. This can impact the number of payload bytes that can be sent in the packet.
I expect the issue to be with the end-device and not the gateway. I would not expect the payload to be truncated by the device, unless there is a built in protocol to fragment the payload into multiple packets.
Packets exceeding the LoRaWAN regional payload limits may not be reported by the network server.
KeymasterOK, the ST-Link tool will erase the entire flash which contains the application and the eeprom configuration data. That explains the deveui of 00’s.
It looks like you have the debug serial port connected.
There is another serial port for entering commands, do you only have access to the other serial ports or only the debug pins?
KeymasterIf it is an MTCDT-H5-210 it does not have GPS needed for Class B and it cannot be added with an mCard.
An MTCDT-X-24X model will be needed.
https://www.multitech.com/brands/multiconnect-conduitJune 15, 2020 at 4:14 pm in reply to: Flashing MDot firmware compiled using MBED Online compiler causes CRC Errors. #30742KeymasterThe online compiler has updated tooling with mbed-os-6
The mdot bootloader is not being built into the application as was the case before the update to the online tools.This may be causing your issues.
Is it possible for you to build offline?
KeymasterThe library is built with GNU Tools ARM Embedded\6 2017-q2-update
I expect v9 is not compatible in some way.We will look to update the library to v9 in a future release, we have been testing with v9 during development.
KeymasterDo you have an example Join Request received by the chirpstack server?
KeymasterDid you happen to erase the flash with a ST-LINK tool?
https://github.com/MultiTechSystems/Dot-AT-Firmware
The xDot debug firmware can be used to set the devEUI
AT+DI=0011223344556677
AT&WPKeymasterDid you verify the JoinEUI in the JoinRequest received at the server matches?
KeymasterDid you change the config setup to use the ID/KEY instead of NAME/PASSPHRASE?
// in OTA and AUTO_OTA join modes, the credentials can be passed to the library as a name and passphrase or an ID and KEY // only one method or the other should be used! // network ID = crc64(network name) // network KEY = cmac(network passphrase) update_ota_config_name_phrase(network_name, network_passphrase, frequency_sub_band, network_type, ack); //update_ota_config_id_key(network_id, network_key, frequency_sub_band, network_type, ack);KeymasterSry. See mlinux doc.
Commissioning mode is coming to mLinux BTW.
-
This reply was modified 4 years, 11 months ago by
KeymasterThis looks like an issue with mbed-os-6.0.0-rc1
When I rolled back to mbed-os-5.15.3 both GCC and ARMC6 work.KeymasterLooks like that readme needs some work.
The latest tag for mbed-os is mbed-os-6.0.0-beta-1
The released library was built against mbed-os-5.15.1
I suggest rolling back mbed-os to use mbed-os-5.15.1https://os.mbed.com/teams/MultiTech/code/libxDot-mbed5/
The Dot library version and the version of mbed-os it was compiled against can both be found in the commit message for that revision of the Dot library. Building your application with the same version of mbed-os as what was used to build the Dot library is highly recommended!
KeymasterThere should not be a libxDot-ARMCC.ar file in the plans directory of the libxDot-mbed5 library.
The ARMCC archive is replaced in the latest releases with an ARMC6 compiled version.
KeymasterThe online compiler now uses ARMC6, there may be some logic to detect a library built with the previous version of ARM CC and compile with the previous version.
Are you using an earlier version of libxDot_mbed5? Which version?
What mbed-os version are you compiling with?Could you publish an example project showing the issue?
I was able to compile this example with mbed-os-5.13.14 and libxDot 3.3.5
ostringstream s1; int i = 22; s1 << "Hello " << i << endl; string s2 = s1.str(); printf("%s\r\n", s2.c_str());KeymasterPins put to analog are shown in the AT Firmware
https://os.mbed.com/teams/MultiTech/code/Dot-AT-Firmware//file/35c201bc5205/CommandTerminal/CommandTerminal.cpp/Also in the dot examples
https://os.mbed.com/teams/MultiTech/code/Dot-Examples//file/76f8a75ed3ec/examples/src/dot_util.cpp/Does this answer your questions?
KeymasterYes and no. Disabling DHCP does not prevent access.
However it does disable the automatic settings your PC was using to connect.
The Ethernet settings will need to be set manually on your PC.https://en.wikipedia.org/wiki/Dynamic_Host_Configuration_Protocol
KeymasterAjay,
You would need to PUT the entire “dhcps” or “dhcp6s” object with “enabled” changed as false to each of these URLS.
PUT https://10.17.100.138/api/dhcp/dhcp6s/0
PUT https://10.17.100.138/api/dhcp/dhcps/0Or delete them
DELETE https://10.17.100.138/api/dhcp/dhcp6s/0
DELETE https://10.17.100.138/api/dhcp/dhcps/0April 22, 2020 at 2:54 pm in reply to: Unable to invoke Conduit API, with firmware version 5.1.6 #30557KeymasterI was able to get a login token if I passed the data in the body rather than the query string. Does this help?
curl -k https://172.16.33.152/api/login --data '{"username":"admin","password":"somepwd"}'April 20, 2020 at 5:58 pm in reply to: Missing Link for the latest conduit firmware version 5.1.6. #30545KeymasterIt was removed by accident. It is back now, thanks for the heads up.
KeymasterYes I have modified the init script to create PKF logs.
How did you implement this?
Redirecting the stdout/stderr to a file with the > or >> does not work with logrotate. The original log file continues to grow as the file cursor does not return to 0 after the truncation. The start of the file is filled with nulls.
In 5.1.2 we added logging capability to the PKF to handle the rotation correctly.
KeymasterThe fix applies to mPower 5.1.2 only.
On mPower 1.7.4 the HUP will restart the packet forwarder.By default there is no PKF logs in mPower 1.7.4
Have you installed packages or modified the init scripts to create PKF logs?KeymasterMichelle,
Could you please provide more details?
What fix did you implement?
What version are you running? $ cat /etc/issue
When is the packet forwarder restarted?KeymasterThere is no support in the gateway for lora mesh.
From what I see it is a device to device protocol.
Do you have a reference to a specific project? -
This reply was modified 4 years, 11 months ago by
-
AuthorPosts