Leon Lindenfelser
Forum Replies Created
-
AuthorPosts
-
December 29, 2016 at 3:56 pm in reply to: MDot as SPI master and introducing delays between writes. #16168
Leon Lindenfelser
ModeratorHi Ajay,
Have you put a scope on the SPI lines to see what is happening? Does the master drive the MOSI line as expected? Does the slave drive the MISO line as expected?
Kind regards,
LeonModeratorHi Laurent,
Have you tested with it near a window or even outside? I know inside our building it can be difficult to obtain lock unless the antenna is near a window.
Kind regards,
LeonModeratorHi Yogesh,
I suppose it could but not necessarily. Are you using our AT command code or your own application? When and how often do you see this error message?
Leon
ModeratorHi Sudhir,
Have you tried the library version with the recommended mbed-os version according to the commit messages…
https://developer.mbed.org/teams/MultiTech/code/libmDot-mbed5/shortlog
https://developer.mbed.org/teams/MultiTech/code/libmDot-dev-mbed5/shortlog
As stated above, when using the I2C, 5.1.4 not 5.1.5 should be used where the commit message indicates 5.1.5.Kind regards,
LeonModeratorHi Yusuf,
As far as I know, only mbed-os version 5.1.5 has the I2C problem. If you are using libmDot-mbed5, then roll back to 5.1.4. In the commit messages of the following page, you will see that we built against mbed-os version 5.1.5 but 5.1.4 will work too.
https://developer.mbed.org/teams/MultiTech/code/libmDot-mbed5/shortlog
If you are using libmDot-dev-mbed5, it is recommended that you coordinate the mbed-os version as shown in the commit message but you can try mbed-os version 5.3 if you want.
https://developer.mbed.org/teams/MultiTech/code/libmDot-dev-mbed5/shortlogWhen you create a project using mbed-cli, for instance
, mbed-os will be a sub-directory of . You will also want libmDot-mbed5 or libmDot-dev-mbed5 as a sub-directory of . Your application should be inside in whatever structure you organize it into.
https://github.com/ARMmbed/mbed-cli#introductionKind regards,
LeonModeratorHi Fabian,
On your PC you’d need to configure some sort of server or even a serial port to receive the sensor data. If you bring up Node-RED on your conduit, on the left you’ll see it has several output nodes that provide methods for output. Maybe look at these links to gain some familiarity.
https://nodered.org/docs/getting-started/first-flow
The MQTT output in Node RED may work with a mosquitto server. You could look at:
https://mosquitto.org/download/Kind regards,
LeonModeratorHi Danny,
I don’t know why there is a difference in the packet failure rate between frequencies. However, I know that placing the mDot too close to the gateway can be a problem as the signal can be too high and may get clipped. Do you have antennas attached? When I do close proximity testing, I remove the antennas. Please see how it performs with no antennas or move them away from each other.
Kind regards
LeonModeratorHi Ajay,
That’s what I would expect. Other than what it does with the external IO, it will work the same as sleep mode. The processor goes into stop mode not standby mode.
Kind regards,
LeonModeratoryes
ModeratorHi Danny,
Take a look at this.
http://nodered.org/docs/getting-started/second-flow.html
You can modify it to trigger with a lora input node and send the output to a lora output node. Assuming you are using class A, sending down to an endpoint can only happen after an up link packet.Leon
ModeratorHi Danny,
The AT commands AT+RSSI and AT+SNR will display RSSI and SNR of downlink packets. Call getRssiStats() and getSnrStats() from the library to get the same information.
If you are interested, AT+PING or ping() get you the RSSI and SNR of uplink packets.Kind regards,
LeonModeratorHi Robin,
I’m told we do not have a library import available for the 40 pin part.
Leon
ModeratorHi Robin,
With or without the developer board… Some pins are 5v tolerant but the analog reference voltage is 3v. So if you to connect voltages that range beyond 3v, a voltage divider is recommended.
I’ll check with out CAD group on the connector.
Leon
ModeratorHi Micheal,
Assuming you are using class A mode, call recv() after send(). See the mDot.h api.
Leon
ModeratorHi Micheal,
Assuming you are using our AT command code, the payload of the down link packet will be output on the main serial port… not the debug port.
I’m not sure if this might work for you but in our AT command code, the +PING command displays the RSSI and SNR that the gateway sees from the mDot in up link packets. The +RSSI and +SNR commands display the RSSI and SNR as seen in down link packets.
Leon
ModeratorHi Andrew,
There is a problem in mbed-os version 5.1.5. If you roll back to 5.1.4, everything should work.
Leon
ModeratorHi Micheal,
With what I gave you, the data is probably ASCII formatted. I believe you can change the formatting of the data in the function node before sending it. Like set it to hex if that’s what you are looking for.
Leon
ModeratorMicheal,
I think you are expecting this to be more complicated than it is. In the Conduit node red screen, there is a list of input, output, function etc nodes in the left panel. From the input list, grab lora. From the function list, grab function. From the output list, grab lora. Connect as follows.
lora input———–function———-lora output
Double click the function node to insert code. Deploy it with the Deploy button in the upper right. Join the Conduit from the dot and do an AT+SEND=. See what you get back. Leon
ModeratorHi Micheal,
In the flow on this page
you see a LoRa input node and LoRa ouput node. The function node should be placed in between them.Leon
ModeratorHi Micheal,
The nature of LoRa communication is such that there is no guarantee that a down link or up link packet will be received on the other side. You can enable acknowledgements and link checks improve odds of delivery but at a cost. Reading the following link may help shed light on the matter.
The receive window I am talking about is the window that is used by the mDot to receive down link packets from the network server following an up link.
Kind regards,
LeonModeratorHi Micheal,
Are you asking how to receive the packet or how to parse the data? If received, the packet will arrive in the first or second receive window… assuming you are using class A.
Kind regards,
LeonModeratorHi Micheal,
In Node RED on the Conduit AEP, you can add a function node between the LoRa input and output node with the following code.
msg.payload=msg.lsnr + msg.rssi;
return msg;See this link.
Kind regards,
LeonModeratorHi Yogesh,
Its not completely accurate to say there is no deep sleep. You can still invoke both sleep and deep sleep. All the internal IO are taken care of in both sleep modes. Deep sleep additionally handles external IO. For a more detailed explanation, see the ‘Deepsleep functionality change’ explanation found at the following link:
https://developer.mbed.org/platforms/MTS-mDot-F411/Kind regards,
LeonModeratorHi Alejandro,
I’m guessing you have looked at the mbed Serial page but I’ll include it in case you haven’t.
https://developer.mbed.org/handbook/SerialYou may also find our example code helpful.
https://developer.mbed.org/teams/MultiTech/code/Dot-Examples/
This page should provide all the information you need to get the examples running.Kind regards,
LeonModeratorHi Sindre,
Yes, if you need to alter the dot box demo mode data for TTN, you can do that in node red.
Leon
November 30, 2016 at 10:09 am in reply to: What version of libmdot, mbed rtos, mbed should be used. #15728ModeratorHi Yogesh,
There’s not much that has changed between the dev library and stable release.
https://developer.mbed.org/teams/MultiTech/wiki/Dot-library-change-logIf you use version 70:c45c5f1e348d, you get the PVD change on top of the stable release.
https://developer.mbed.org/teams/MultiTech/code/libmDot-dev-mbed5/shortlog
Make sure you use the proper mbed-os version as indicated in the commit message.Given your timeline and assuming you need the PVD protection, I wouldn’t suggest you wait for a new stable release. I’d use version 70:c45c5f1e348d libmDot-dev-mbed5 and stick with it during your testing. If you see no problems, got with it for production. If we produce a new stable release, while you still have test time available, you could switch to it.
Kind regards,
LeonModeratorNovember 29, 2016 at 9:44 am in reply to: What version of libmdot, mbed rtos, mbed should be used. #15693ModeratorHi Yogesh,
Do you need a production release of the mDot library with PVD support by a particular date? We have not set a timeline yet but I expect we’ll have a release in Q1 of 2017.
Kind regards,
LeonNovember 22, 2016 at 9:09 am in reply to: What version of libmdot, mbed rtos, mbed should be used. #15605ModeratorHi Yogesh,
The STM32F411RE processor we use on the MDOT has a programmable voltage detector(PVD) built into it. Any time a file system transaction is requested, the PVD output is read to see if the voltage is above or below the programmed voltage. If it is below, the file system access is blocked. You can go to the ST Micro web site to download the STM32F411RE data sheet and reference guide for additional details.
This feature is currently supported in the libmDot-dev-mbed5 version not the libmDot-mbed5 version.
The PVD code is implemented in the mDot library. It does not rely on anything in mbed-os5.
Kind regards,
LeonNovember 21, 2016 at 10:24 am in reply to: What version of libmdot, mbed rtos, mbed should be used. #15581ModeratorHi Yogesh,
Building on line works. I think working off line is more of a work flow issue and allows you to use your preferred IDE for editing code. Of course you could edit off line and move your source code into the on line compiler for compilation.
Your SPI interface will work in mbed-os 5.1.5. It is only the I2C interface that is broken in that revision of mbed-os.
DR0 is not an issue with ADR.
You can use the latest stable build if you like…
https://developer.mbed.org/teams/MultiTech/code/libmDot-mbed5/
This should be build against mbed-os version 5.1.5. As long as you are not using I2C, this will work. Moving to the latest libmDot-dev-mbed5 version with the newer mbed-os, you get the PVD enhancement. If you are running off batteries, I’d recommend this. If your power source is stable at 3.3-5v, then this is of no value for you.Kind regards,
Leon -
AuthorPosts