[Frank A]

Hello Darrik,

Thank you for your quick response!

I followed the steps you suggested and it worked. In fact, I did start by upgrading from 1.3.2 to 1.3.3 before upgrading to 1.4.3, because the upgrade notes from 1.4.3 suggested that I could lose my LoRa configurations if I didn’t (it wouldn’t have been a big deal though).

Again, thank you for your support. It is much appreciated. A+

Frank

• This reply was modified 4 years, 6 months ago by Frank A. Reason: typo

[Frank A]

Hello Colin,

I asked a similar question a few weeks ago, about using the US915 mDot with the EU868 band. I my case, I needed to flash the mDot with the appropriate firmware: I couldn’t simply issue at+freq=EU868 (the same appears to be true for at+freq=AU915).

I didn’t actually try it (i.e. change US to AU), but my impression is that you need to flash your mDot with one of the firmware versions that can be found here.

I hope this helps. A+

Frank

• This reply was modified 6 years, 8 months ago by Frank A.

[Frank A]

Thank you for the information Jason!

[Frank A]

Hello Jason,

I had not seen your answer before posting a second time. 🙂 But thank you for your quick response!

at+pn=1 might indeed have been what was causing my problem. I was using at+pn=0, but my packet forwarder configuration file had "lorawan_public": true. I don’t why it didn’t work last night using the Conduit network however, but it is very likely that I was too tired to work on that and I simply missed something(s). 🙂

Once again, thank you very much for your time and support. Have a great day. A+

Frank

[Frank A]

Hello again,

I would like to withdraw my question, if possible.

I tried it again this morning and everything works fine. The only logical explanation here is that I was working too late last night. 🙂

I apologize for waisting your time.

Thank you very much for your time and support. A+ 🙂

Frank

[Frank A]

Hi Steve,

Thank you very much for the quick reply!

I will definitely have a look at what you are recommending.

Thank you for the information. A+ 🙂

Frank

[Frank A]

Thank you for confirming this Peter. A+ 🙂

[Frank A]

Hi,

I just stumbled upon this thread on this forum, in which it is mentioned that the mDot’s reference voltage for analog inputs is indeed 3V. So I guess this does answer part of my original question, but could this please be confirmed with a quick reply?

That being said, the last part of my initial question is: Is pin 24 of the mDot intended to be used (among other things), for instance, to help power analog sensors (e.g. pin 20 in analog input mode; AnalogIn(A0))?

Thank you for your time and support.

Frank

[Frank A]

Hey Jason,

Understood. Thank you for clarifying.

Thank you for your time and support. A+ 🙂

Frank

[Frank A]

Hey Mike,

Thank you for confirming this!

I did not think to ask in my original question, but now I think that it is a relevant request: I wonder if you could point me to some official documentation on how one would go about configuring the basic packet forwarder for different frequency sub-bands.

There is an example here (https://github.com/Lora-net/packet_forwarder/blob/master/lora_pkt_fwd/cfg/global_conf.json.US902.basic) from Semtech for frequency sub-band 1, and here is another one by The Things Network for frequency sub-band 2 (https://github.com/TheThingsNetwork/gateway-conf/blob/master/US-global_conf.json). Looking at these files, I realize that there is likely at lot of tuning that can be performed, for a wide array of configuration options. So it would be nice to have official guidelines about custom configurations.

Thank you for your time and support. A+

Frank

[Frank A]

Hello again Mike,

Thank you very much for confirming that the mDot can be operated without an antenna, as well as for the useful information about cases in which one might prefer to actually use it (i.e. mDot) without one (i.e. antenna).

Obviously, I think it is a must that a module like the mDot can be used without an antenna, because, for some IoT use cases (e.g. for very small sensor devices), the antenna won’t be an option.

Thanks for your time and support. A+ 🙂

Frank

[Frank A]

Hello Mike,

Thank you for your quick response!

Thanks for the link to the pressure/temperature sensor’s datasheet. I’ll have a look at it.

You are confirming what I suspected about the heat generated by the LoRa radio, etc., and this was this topic’s main purpose.

In fact, to be honest, this is not really a big deal for me. I think that it is fair to say that most people using this product (i.e. the mDot Box) are not using it to get precise temperature readings. It is a great experimentation tool, and, as far as I am concerned, I am glad I have it.

Once again, thank you very much for your time and support. A+ 🙂

Frank

[Frank A]

I further inspected the configuration file for the basic packet forwarder (e.g. http://www.multitech.net/developer/wp-content/uploads/2017/05/US-915-example-config.txt) and I finally figured out that the frequency sub-band was set using the fields radio0 and radio1.

The example configuration file above uses values that represent frequency sub-band 1, and since these are the exact same configurations I was using, that explains why my mDot needed to be compiled for FSB 1. So, if I want to use a different sub-band, I need to modify those values accordingly.

[Frank A]

Mike,

Thank you for your quick response!

I tried with v4.9 of the GCC ARM compiler as you suggested and it worked.

Thank you very much for your time and support. A+ 🙂

Frank

[Frank A]

Jason,

Thank you for the quick response!

I guess I’ll do as you suggest and go for the AEP model then. I think that it will be nice to be able to try both (i.e. AEP and mLinux).

Thanks again for your time and support. It is very much appreciated. A+

Frank

[Author]

Posts