Error with Two Way Ranging Initiator and Responder and Help with TWR Example

[maeenk]

Hello Guys, I am having some trouble when running both the Two Ranging Codes (Initiator and Responder) and also with the 2-D Main Anchor and Tag Implementation codes. I am new to this and want to replicate this system but I've come across some difficulties. Currently, I am using a Node MCU 1.0 ESP 12-e chip that is wired with a DWM1000. I have around people recommending external power, but I a connected my Node MCU to a laptop port. The Basic Receiver and Basic Sender had also had issue as I got bunch of "Question Marks" in the Serial Monitor from the Basic Receiver's Serial Monitor while the Basic Sender is continuously transmitting the packet.

Basic Receiver

Basic Sender

For the Two Ranging Initiator and Responder. Once I implemented the changes for "Fix ISR #181", the Two Way Responder started to output the following although I believed the changes would help bypass this problem. The Two Way Initiator runs the same edited "Fix ISR #181" changes.

(Using the example code provided printed a bunch of hex values, and really implementing that changed reduced it. )

Could you shed some light on the matter?

Along with this, I am also having difficulty with implementing the Standard RTLS Project. Whenever these codes are uploaded, sometimes the Serial Monitor is blank or it outputs the basic setup string statements but never the ranging. The RTLS project utilizes the original src libraries and not the "Fix ISR #181" changes (that was used only in the Two Way Responder and Initiator).

Tag's Serial Monitor.

Anchor B and C

And Anchor Main is usually blank with no range values and once with the printed strings in the setup function.

Sometimes the output from the tag and anchors' serial monitors may not come out until several minutes or ever (nothing even after 10 minutes). Would you please shed some light to this matter as well. What fixes can I implement?

Thank you in advance!

[anacromaniac]

Can you try this version? https://github.com/F-Army/arduino-dw1000-ng/releases/tag/0.3

I suggest you proceed in steps, first try to make basic sender and receiver work. Let me know if the stable release works (a lot of code was merged in between and maybe something broke)

[maeenk]

So I went ahead and tried both the basic sender and receiver tests. These are the outputs I am getting on the Serial Monitor.

Basic Receiver

Basic Sender

I am not too sure if I am suppose to see these symbols...

[Sonic0]

Hi @maeenk,
we have been using the same MCU. Check out the wiki to find out pins connection with NodeMCU 1.0, this seems to be an SPI or alimentation problem. Our DWMs use 3.3V out voltage from NodeMCU.
In addition, I had have a problem like this when I make a mistake during the soldering of the DWM1000.

[maeenk]

You are maybe right. I will double check that.

I was wondering if you utilized an external power supply because I am simply using the connection from a usb to a computer. Or a voltage regulator; if so, any recommendations?

Thank you again for your response. It is helping a lot.

[Sonic0]

I was wondering if you utilized an external power supply because I am simply using the connection from a usb to a computer. Or a voltage regulator; if so, any recommendations?

We have used the internal voltage regulator of the NodeMCU 1.0 and the Main Anchor connected via computer USB.
Try keeping the WAKE pin to 3.3V. Otherwise, try another dwm1000 device.
Unfortunatetly, no other ideas.

[maeenk]

By any chance, were these the connections? These are the physical connections I made. Just want to make sure. Thank you again for your help!

[Sonic0]

Yes @maeenk, we have made the same connections but whitout pull-down resistor on IRQ.

[maeenk]

Hello again, it seemed as if I posted in the wrong post last time. Below includes the conversation from the recent post.

I wanted to make sure just how exactly do I actually get the same device mode. Does re-downloading the zip file do this? If so, which version should I download? I had switched to an Arduino Uno because I was having difficulty with the NodeMCU. With the Arduino, I was able to get the basic receiver and sender to work. But the two way ranging is still giving me issues. I made sure that I was utilizing 5 volts on the Arduino to use SPI and a bunch of resistors to drop down this voltage to 3.3 volts. However, it doesn't seem to work as I hoped.
By any chance could I see how the connections were set up or could you give any other advice on the matter? I appreciate all the help too.

[Sonic0]

Hi @maeenk , check the DEFAULT_CONFIG structs at the beginning of Arduino examples.

[maeenk]

I have made sure that the both serial monitors were printing out the device mode when not using the voltage divider method when testing the two way initiator and responder. Thank you again. I used the two way responder example code; but I do want to point out that in the arduino-dw1000-ng-0.3 version that both the irq and reset pins were commented out, so I uncommented them when running them. I have been following the setup with Arduino Uno below, but used resistors instead of a voltage regulator.

Once I used the method with voltage dividers, as Arduino's SPI operates then, I got this from the responder's serial monitor. And this is wrong as I should've seen some range. Maybe it is in something I did but can't seem to find out yet.

I decided to see what exactly was being sent and received, and this was the responder's serial monitor. This shows that nothing is being sent nor received by the responder because of the "0" at the end of each line.

Would you provide recommendations? Which zip file should I include instead?

[Bartvelp]

hey @maeenk
I have used the ESP8266 and I sort of recognize some of the errors. Please make sure that when the sketch does not print an incorrect Device ID like FFFF in many in your screenshots, or the weird characters printed. These kinds of errors always point to some kind of wiring issue, either I accidentally connected 2 pins together on the DWM (that damn pin spacing is small) or the connection just was not solid enough. Do not use a breadboard, always directly solder a copper wire to both the ESP8266 and to the DWM module, it will save you a lot of headaches.
Did you do this?
In my tests the dwm1000 isn't too picky about power, just add a 100uF capacitor and you should be fine.
IMO you should stick to the latest version of the library and if you use an ESP8266/ESP32 use the one in my pull request that fixes ISR. But sonic and 0nism know a lot more about this library than I do.
Stick to the basicReceiver and basicSender sketch, when you get that working, continue to ranging sketches.

[Sonic0]

Yes, when all F appears at the beginning during the reading of configuration committed to the DWM1000, there is a problem with SPI communication. I had the same problems a the beginning of this project due to the breadboards and soldering mistakes w(ﾟДﾟ)w.

[maeenk]

In my tests the dwm1000 isn't too picky about power, just add a 100uF capacitor and you should be fine.

Thank you for the response. I too believe that it has something to do with my wiring. I will move to soldering everything instead of breadboarding. I do want to make sure about the power to the dwm1000. Would I connect a 100 uF capacitor from the VCC to VDDAON, VDD3V3 (in the schematic above)? Just want to make sure the connections to delay this any further.

[Bartvelp]

Add an electrolytic capacitor across VCC (which is the net connected to VDDAON, VDD3V3) and ground. As you might know, the capacitor will act as a (very) small battery that can make sure there is no big voltage drop due to current spikes when transmitting and receiving. Since it buffers a small charge, you always need to connect 1 leg to a positive rail like VCC(/VDD3V3/VDDAON) and 1 leg to ground.
This is my schematic: (BU01 === DWM1000 equivalent)

The ceramic cap is not really necessary I think but it is common practice.
Hope this helps.

[maeenk]

Hi guys and thanks for the reply,

I am editing this post entirely. I realized that the library beginning of SPI actually sets up the SPI modes. The basic senders and receivers don't utilize SPI, but the Two Way Ranging does. I tried just trying to see waveforms when the dwm1000 is disconnected from the NodeMCU, so just probe the NodeMCU SPI parameter pins. I found from my oscilloscope that the MISO, MOSI was constant low or at 0 which I am assuming is problematic. However, once I connected the Dw1000 with the NodeMCU, I went ahead and probed four of the main pins for SPI: chip select, clock, MISO, and MOSI. Here are the following readings I saw from the oscilloscope. The codes used to run are the Two Way Initiator and Two Way Responder. Channel 1 is the Yellow Signal and Channel 2 is the Blue Signal.

Two Way Initiator:
Channel 1 is MOSI, and Channel 2 is Clk. It is hard to see, but they overlapped one another below

Channel 1 is MISO, Channel 2 is MOSI below

Channel 1 is Chip Select (CS) and Channel 2 is MOSI below

Two Way Responder:
Channel 1 is MISO, and Channel 2 is MOSI below.

Channel 1 is Clk and Channel 2 is MOSI

Channel 1 is CS and Channel 2 is MOSI

Comparing MISO (Channel 1) and MOSI (Channel 2) on both responder and initiator. Responder is the picture on the Left, and Initiator is picture on the Right.

When I was observing the MISO and MOSI waveforms from both the responder and the initiator, I was wondering why I am seeing two different waveforms especially in there difference in voltage peaks. The initiator is tiny in comparison to the responder. I kind of assumed that they were going to be similar especially in that they were initialized the same way. The responder seems to be looking fine, but the initiator is probably what is messing up my attempt on your two way ranging examples. The other signals seem to look correct as well. I was hoping what steps would you recommend I take? Is there a simple SPI program to send some bytes over? I am bit of a novice and am very fascinating in running this project as well.