My Sensor node "motherboard" (MySensorsNode)

[Cliff Karlsson]

I just got my boards from dirtyPCBs but are there any list of the required components? And can I use rfm69 with a 5v pro mini or do I have to use a 3.3v pro mini?

[Anticimex]

@Cliff-Karlsson you can find the BOM in GitHub under manufacturing. The board is designed for 3.3v pro mini. I have not taken 5v variant into consideration at all.

[Cliff Karlsson]

Are all components required? I know you can only use one radio / pcb and that the power sockets are optional. But I tried to find the cheapest components and after adding all the components from aliexpress the cost is almost 100 EUR and then I got probably atleast as many components from the more expensive shops left.

[Anticimex]

@Cliff-Karlsson well, I did not consider cost for my board. That said, 100EUR is definitely not required to spend for components on it. It depends on how you intend to use it and what flexibility you want. The ability to control certain aspects is optional as indicated by jumper configurations. I made it clear in my schematic what parts are optional to solder. You can of course cut more cost by skipping decoupling and such as well, but I can't vouch for board performance in that case.

[Pejo]

@Anticimex Do you know what screws are expected for the BOX-2252? Is it M2 or something else?

[Anticimex]

@Pejo I believe M2.

[Pejo]

@Anticimex Thanks!

[Cliff Karlsson]

Is it possible to only solder a mini pro 3.3v and an rfm69hw to your pcb and use it as a mysensors gateway? Or do I need to solder any more components?

[Anticimex]

@Cliff-Karlsson it was never design for that purpose, but I suppose you could. You'll need to see the schematics to determine what additional components are needed for power and regulation. Decoupling is also highly recommend. Remember that you need to expose a serial port for the GW.

[MiKa]

Hi,
Can You share also pcb for BOX-2252 please
Thanks,
MiKa

[Anticimex]

@MiKa https://www.openhardware.io/view/2/MySensors-node
It's all there. However, be adviced that the board has a hard time fitting BOX-2252.

[MiKa]

Hi,
Which one is problem to fit into the box? 2252 or LE-BOX-0028 ?
Here You wrote about 2252 and on the openhardware site is LE-BOX-0028...
Regards,
MiKa

[Anticimex]

@MiKa Hi, sorry, my bad. It is LE-BOX-0028 (the big one) that has problems fitting (at least the box I have).

[bilbolodz]

Could some please point me to right (working) Dualoptiboot bootloader for these board? I'm fighting with it for over two days but without success.

[Anticimex]

I have not used dualoptiboot. But there should not be need for a special variant of it. It is a board that takes a standard arduino pro mini so a bootloader designed for that arduino should work just fine. Just make sure to configure the proper JEDEC ID for the flash.

[bilbolodz]

I've took bootloader from: https://github.com/LowPowerLab/DualOptiboot
What JEDEC ID is correct for AT25DF512C?

[Anticimex]

@bilbolodz that is stated in the datasheet of the device. Table 12.2. Manufacturer ID is 1Fh and Device ID part 1 is 65h. So you need to define MY_OTA_FLASH_JDECID to 0x1F65 (which is default I believe).
I don't know if you need to reconfigure DualOptiboot if you took it from LowPowerLab. Perhaps.

[bilbolodz]

I've got it working BUT I've very strange "solution". I'll write it down maybe someone be able to explain me what's going on:

I've 3 versions of "test program" 1.0, 1.1, 1.2 (actually the only difference is sketch number).

1. I'm uploading manually with avrdude DualOptiboot from "Mysensors board package" (uploading using gui not working - gives strange error about fuses).
2. I'm uploading (using USBasp and Arduino GUI) program version 1.0: program is working but "Reboot" command send from MYSController gets arduin into endless loop during "boot"

0 MCO:BGN:INIT REPEATER,CP=RNORAA-,VER=2.1.1
4 TSM:INIT
4 TSF:WUR:MS=0
12 TSM:INIT:TSP OK
14 TSF:0 MCO:BGN:INIT REPEATER,CP=RNORAA-,VER=2.1.1
4 TSM:INIT
4 TSF:WUR:MS=0
12 TSM:INIT:TSP OK
14 TSF:0 MCO:BGN:INIT REPEATER,CP=RNORAA-,VER=2.1.1

3. Physical reset of board and OTA update to v 1.1 using MYSControler. OTA update is finished but at the end "endless loop"

133398 OTA:FWP:RECV B=0000
133400 OTA:FWP:FW END
136038 OTA:CRC:B=05A8,C=6506,F=6506
136040 OTA:FWP:CRC OK
0 MCO:BGN:INIT REPEATER,CP=RNORAA-,VER=2.1.1
4 TSM:INIT
4 TSF:WUR:MS=0
12 TSM:INIT:TSP OK
14 TSF:�0 MCO:BGN:INIT REPEATER,CP=RNORAA-,VER=2.1.1
4 TSM:INIT
4 TSF:WUR:MS=0
12 TSM:INIT:TSP OK
14 TSF:�0 MCO:BGN:INIT REPEATER,CP=RNORAA-,VER=2.1.1

4. Physical reset of board: still version 1.0 present and running, reboot NOT working
5. One again I program bootloader using command:

avrdude -c usbasp -p m328p -u -U flash:w:optiboot_atmega328_pro_8MHz.hex

6. Surprise, surprise: version 1.1 present and running, reboot command WORKING!
7. After these I can program freely (using OTA) other versions of program (e.x. 1.2 or even "start version" 1.0)

I'm making some STUPID mistake but I can't find it......

[Anticimex]

@bilbolodz hm, sorry. Can't really help there. The board should be SenseBender compatible so what ever flow is described for that board (and bootloader designed for that board) should work on this. But perhaps the fact that this one has a pro mini and not just a vanilla atmega cause it to behave differently in some way.

[rozpruwacz]

@bilbolodz I had also problems with DualOptiboot and OTA. It is very poorly documented. As I understand how it works, If you burn the bootloader first and then the program You actually erasing the bootloader that you burned before (thats why it is in "endless loop"). The bootloader must be burned after the program is already on the external flash, so it can load that program into the internal memory. To do that:

1. upload the program to the board
2. fire the ota update to write the same program to the external flash
3. program the bootloader

after that you will have the bootloader and OTA working.