Anyone tried Laird RM1XX modules?

@BoRRoZ
thanks for the update procedure, any new features on this version or just bug fixes ?

Itā€™s a big and worthy update. BLE pairing actually works now :slight_smile:

also LoRa stack updates

You should also be able to update via the JTAG (SWD/Segger) if you donā€™t have Windows.

2 Likes

The following changes have been made for 18.4.1.0 release:

  • Updated LoRa Stack to 4.3.0
  • As part of stack update, if JoinRequest fails, the module automatically resends the JoinRequest.
  • Changed the ids for DevEui, AppEui, AppKey, NwkSKey, AppSKey, and DevAddr. AppKey, NwkSKey and
    AppSKey are now write only. This is to close a potential security problem. All existing modules must be
    reconfigured with the new ids.
  • Added in new LoramacSetOption() parameter to allow the user to modify the datarate for the 2
    Rx window. This avoids a problem with the iot.semetech.com website where they still use the old value of
    DR_3 for this window.
  • Bug fix - BLE bonding now works.
  • Bug fix ā€“ LoramacGetOption() now outputs the correct values for AppEui and DevEui.
  • ChannelsMask value can now be obtained in the RM191.
  • Added new events for the TxDone signal, ADR command from the gateway, and when a receive window times out.

thanks guys, youā€™re so prompt;-)

  • dingdong ā€¦ the AM2305 NOT ! I2C temp sensor ready for outdoor use

looks niceā€¦ more RM186 driver work :sunglasses: PDF specs

  • I thought it was equal to this which has a real I2C interface
    So I can use it with an arduino one wire lib, but it will be more difficult to use with RM186
1 Like

I need the same (size and price) with I2C sensors (BME280, SI7021 or HTU21D), this one controlled by only one wire are just so complicated in term of strict timing/measure time when coding on multitasking os such as linux :wink:

1 Like

How are you guys programming this module. Using the docs from Laird?
Never used smartBASIC beforeā€¦

I use docs from the Laird site to learn and also study example programs.

Oh thanks @BoRRoZ :slight_smile:

We are designing a small board with gps and accelerometer using this module.

Is anyone else working on something similar? would be good to compare notes :slight_smile:

diy evolution :sunglasses:

2 Likes

Nice! Iā€™m actually using a similar case for my RN2483+Teensy nodes :blush: . Which and how many batteries do you use?

1 or 2 lipo 750 mA


found the cheap enclosures here

* thereā€™s not much 'height !

What is the battery life of these?

that depends on your circuit :wink:

Why Li-Ion? Do you intend to make the nodes rechargeable?

I use NiMh because itā€™s cheaper and lasts longer. Li-Ion looses its charge quite fast imo. I want to make my nodes run for years without servicing :smile: .

in this particular application.

I donā€™t agree

I am preparing a longer post with some data ā€¦ next week :wink:

ā€™ I want to make my nodes run for years without servicing ā€™
o thatā€¦ yes, thats the 'dream of many people :innocent:

I never had more than a couple a couple of weeks with LiPo batteries, now use LTC which give me many months of operation. Should be years but these sensors havenā€™t been around long enough to test that. And with LTC, they are much easier to purchase in large quantities than LiPo.

Iā€™ve tested batteries from 100 to 12000 mA/H, all depends on the use, indoors or outdoors, just a door/window contact or a movement sensor in a crowded place.

If you use sensors which donā€™t use a lot of energy, you can feed them direct from the GPIO and let them sleep when the circuit sleeps, only to wake up by an RTC signal.
The RM186 GPIO pins for example have 2 modes, 0.5 mA and 5 mA drive current you can set.