@gizmox

Needed to regulate the input voltage for the radio.

It was mentioned that the radio should NOT be powered through the on-board Regulator.

At the bottom of the linked article it says...

Edit: [CNLohr] points out there’s a more preferred toolchain that most people have switched to.
https://github.com/esp8266/esp8266-wiki/wiki/Toolchain

And be aware of this thread where the ENC module is hanging after a while..

http://forum.mysensors.org/topic/536/problems-with-enc28j60-losing-connection-freezing-using-uipethernet-or-ethershield-read-this

They both use SPI interfaces.

Did you wire it up like the Ethernet Gateway?
http://www.mysensors.org/build/ethernet_gateway

Hi,

Did you check the voltage of the output of the power supply?
I bet it's over 12V

LE33 seems to allow up to 20V
Arduino Mini Input Voltage range is 7-9 V
http://arduino.cc/en/Main/ArduinoBoardMini

I would check voltages at all the points to make sure it is in range.
Double check at the plugs (if you are using them) to make sure it's not shorted

Edward

@hek thanks for the clarification...

OK, that's interesting...

So you are utilizing the Hardware Ack mechanisms - RC represents the hardware successfully received HW Ack to the message.

• Understand the st=fail now. The hardware Ack was not received.
• Even if the Ack was received, No guarantee that the sketch got the message

The Software Ack is then handles the full path - validates that the message made it all the way up to the clients' sketch.

• The HW may have successfully received the message but for some reason did not make it to the sketch to be processed
• or the sketch failed to process the message.

Now, only if we can "fix" the debug output to identify which are Acks

• I know I can use the isAck() in the sketches......
• This was just in the debug messages so when we look at the output, it's clear that its an Ack message.
• That's what debug mode is for, so we can simply trace the messages

@dzairo thanks.

I'm not asking how to use the Ack flag.

I'm asking how to recognize the Ack messages from the debug messages.
This is the debug with Ack enabled. can you tell me which one is the Ack message?

send: 0-0-200-0 s=0,c=1,t=0,pt=5,l=4,st=fail:328336
rf24.send() RC=0
read: 0-200-0 s=0,c=1,t=0,pt=5,l=4:328336
send: 0-0-200-0 s=0,c=1,t=0,pt=5,l=4,st=fail:328336
read: 0-200-0 s=0,c=1,t=0,pt=5,l=4:328336

Second, why is the send status = fail but seems like the message actually was successful in being received by the receiver (as I received a reply to the message sent).

Hard to tell in the breadboard. Make sure the V12 is going to the RAW pin and not the GND pin.

The breadboard also does not show a connection from the Arduino to GND. So add a connection from the Arduino GND pins to the minus terminal of the power supply. (This missing piece in the breadboard diagram is probably the source of the question)

GND and the minus terminal of the power supply should always be connected.

The FET is being used to control the current trough the LED to GND
As long as it's not running the current through the Arduino, it's fine.
Practically,

• if you connect it to the Arduino GND ipin
• and the Arduino GND pin is connected to the minus terminal of the power supply
• Then the current is NOT going to go into the Arduino, it will go to the power supply's minus terminal (path of east resistance)
• So, anywhere there is a direct path to the minus terminal of the power supply is good.

Edward

I guess then it's a feature request..

1. Add Ack Flag
2. Add indicator when the library sends the message vs. the sketch.

Any idea why the status is returning fail (st=fail) when it looks like the message send was actually successful?

send: 0-0-200-0 s=0,c=1,t=0,pt=5,l=4,st=fail:328336
rf24.send() RC=0
read: 0-200-0 s=0,c=1,t=0,pt=5,l=4:328336

I have a very simple sketch, Controller sends a message every 500 ms to a sensor node. with the millis() as is it's payload.
The sensor node just echos the payload back...

void loop() 
{
    int iRC;
    
    rf24.process();
    if ((millis() - lastrun) > 500)
    {
        Serial.println("---------------------------------------------------");
        iRC = rf24.send(myMsgPingReply.set(millis()), RF24_RECEIVE_ACK_FALSE);
        Serial.print("rf24.send() RC=");
        Serial.println(iRC);
        lastrun = millis();
    }
}```


Here is a question to what is in the serial output..

Q1:  The first send():  Why is the RC = 0  when the remote node got the message and replied.    
---
Am I understanding the RC of the send() incorrectly?  1 = Successful, 0 = failed?
Especially since the "st=fail" in the debug corresponds to the RC from the send() 

---

send: 0-0-200-0 s=0,c=1,t=0,pt=5,l=4,st=fail:27546
rf24.send() RC=0
read: 0-200-0 s=0,c=1,t=0,pt=5,l=4:27546

send: 0-0-200-0 s=0,c=1,t=0,pt=5,l=4,st=ok:28072
rf24.send() RC=1
read: 0-200-0 s=0,c=1,t=0,pt=5,l=4:28072

send: 0-0-200-0 s=0,c=1,t=0,pt=5,l=4,st=ok:28582
rf24.send() RC=1
read: 0-200-0 s=0,c=1,t=0,pt=5,l=4:28582

send: 0-0-200-0 s=0,c=1,t=0,pt=5,l=4,st=fail:29092
rf24.send() RC=0
read: 0-200-0 s=0,c=1,t=0,pt=5,l=4:29092

send: 0-0-200-0 s=0,c=1,t=0,pt=5,l=4,st=ok:29618
rf24.send() RC=1
read: 0-200-0 s=0,c=1,t=0,pt=5,l=4:29618

send: 0-0-200-0 s=0,c=1,t=0,pt=5,l=4,st=ok:30127
rf24.send() RC=1
read: 0-200-0 s=0,c=1,t=0,pt=5,l=4:30127

send: 0-0-200-0 s=0,c=1,t=0,pt=5,l=4,st=fail:30637
rf24.send() RC=0

send: 0-0-200-0 s=0,c=1,t=0,pt=5,l=4,st=fail:31162
rf24.send() RC=0
read: 0-200-0 s=0,c=1,t=0,pt=5,l=4:31162

Q2:  Set the ACK flag to TRUE:  How do I know from the serial output which is the Ack Message?
----
My sketch sends the first send: 0-0-200-0 ....
I'm done after displaying the RC
The first read: 0-200-0 ... must be the Echo back from the sensor node
the second send 0-0-200-0  must be the Ack to the Sensor node
the second read 0-200-0 must be the Ack from the Sensor node to the initial Send?

Send Msg -->
<--  Echo of the Msg
Ack of the Echo -->
<--  Ack to the Msg"
Is this correct?  


* Only way I could assume the above is  because there is only one message involved.  In a more complicated case when trying to debug how would someone know what is a message I sent and one automatically sent by the Library?  What is an Ack message?

* st=ok and st=fail still concerns me that is does not make sense.  :-(

---

send: 0-0-200-0 s=0,c=1,t=0,pt=5,l=4,st=fail:327302
rf24.send() RC=0
read: 0-200-0 s=0,c=1,t=0,pt=5,l=4:327302
send: 0-0-200-0 s=0,c=1,t=0,pt=5,l=4,st=ok:327302

send: 0-0-200-0 s=0,c=1,t=0,pt=5,l=4,st=ok:327827
rf24.send() RC=1
read: 0-200-0 s=0,c=1,t=0,pt=5,l=4:327827
send: 0-0-200-0 s=0,c=1,t=0,pt=5,l=4,st=ok:327827
read: 0-200-0 s=0,c=1,t=0,pt=5,l=4:327827

send: 0-0-200-0 s=0,c=1,t=0,pt=5,l=4,st=fail:328336
rf24.send() RC=0
read: 0-200-0 s=0,c=1,t=0,pt=5,l=4:328336
send: 0-0-200-0 s=0,c=1,t=0,pt=5,l=4,st=fail:328336
read: 0-200-0 s=0,c=1,t=0,pt=5,l=4:328336

---

Hi,

I assume that you have an MySensor with an radio attached.
What sketch are you running to interface with the program?

Thanks
Edward

Try sudo cat /etc/groups

This will print the contents of the file "groups" in the /etc directory.
addgroup modifies this file.

The board tested good.

I have some small changes I would make for the next version but this board is good enough to start building...

The files are attached in the first post.
You you make enhancements, please share your enhancements so everyone else can benefit.

Thanks
Edward

It would be cool if this could be adapted to MySensors

Touch-less Gesture Controller + Home Automation
http://hackaday.io/project/1173-touch-less-gesture-controller-home-automation

Changelog:
12/3/2014

• Msys 1..1 - Gerber files are now available.

11/24/2104

• Source files are available for MeanPenguin MySensors PCB

11/15/2014:

• Added nRFIoT - Easy IoT Sensors thanks to @lasso for the referral
• Changed cm to mm thanks to @lasso for the correction
• Added Stockie- item centric shopping list

---

We're now using OpenHardware.io for our community PCBs

Hi,

As requested by @hek in one of the threads.. I'll attempt to maintain a list of Custom PCB you can build for MySensors.

Reference: Post focusing on all MySensor Supported boards

####Key
Schematic: A Picture of the Schematic is available
Build Files: Files need to build the board are available
Able to Modify: Files needed to modify the Schematic and Board are available

###Arduino Nano Gateway for Vera
Schematic: No
Build Files: Yes, Link to OSHPark
Able to Modify: Looks like the .brd file is available. I don't see the .sch file.
Description: Nano Gateway V2. Arduino Nano Gateway for MCV Vera 3 and Vera Lite systems.

###Minimal design thoughts
Schematic: Yes
Build Files: Yes (https://github.com/mysensors/SensebenderMicro)
Able to Modify: Yes
Description: Same size as a standard nrf24 module but includes atmega 328 and the nrf24 radio, official MySensor board, sold as "Sensebender Micro" from itead studio

###Battery Sensor v 1.0 PCB
Schematic: No
Build Files: Yes, (board is shared on OSHPark under UserName "ClipperMiami')
Able to Modify: No
Description: 50mm x 50mm board includes atmega 328 and the nrf24 radio.

###Official? MySensors battey board revision 1.0
http://www.mysensors.org/hardware/battery_sensor
Schematic: Yes
Build Files: No
Able to Modify: No
Description: 50mm x 50mm board includes atmega 328 and the nrf24 radio.

###Arduino UNO Shield
Schematic: No
Build Files: Yes
Able to Modify: .brd file is available
Description: A shield with headers for the radio to fit on an Arduino UNO

###MeanPenguin MySensors PCB
Schematic: Yes
Build Files: Yes
Able to Modify: Yes
Description: 50mm x 50mm board to hold a Arduino Mini Pro and the radio

###My sensorboard MYS 1..1
Schematic: Yes
Build Files: Yes
Able to Modify: No
Description: 50mm x 50mm boards with arduino pro mini and radio

###Schematic to MySensor Board
Schematic: Yes
Build Files: No
Able to Modify: No
Description: Schematic for a board using atmega 328 and the nrf24 radio.

###nRFIoT - Easy IoT Sensors
Schematic: No
Build Files: Yes (The .brd file is available) (https://www.dropbox.com/sh/vg0re4qo1ic6q91/AADA00TXXfzyIMQ8QLQ2xTPTa)
Able to Modify: No
Description: A Pro Mini Shield. A PCB, size of the Pro Mini, which can be stacked. "The finished product measures in at the size of the pro mini, and about 3 times thicker. "

###Stockie - item centric shopping list
Schematic: Yes
Build Files: Yes
Able to Modify: No
Description: An ATTiny PCB (so may not work with MySensors) with an NRF24. "Throughout the house there are tags (1) and panels (2) that allow you to mark one item as running low with a simple push of a button."

Misc Links related to Custom PCB

Etching My Own Boards

Try this...

#include <SoftSPI.h>
#include <MySensor.h>  
MySensor gw;


#define NUMBER_OF_VALVES  4
MyMessage *msg1valve[ NUMBER_OF_VALVES + 1 ] ; 
MyMessage *var1valve[ NUMBER_OF_VALVES + 1 ] ;
MyMessage *var2valve[ NUMBER_OF_VALVES + 1 ] ;


void setup() 
{ 
  for (int i = 0; i <= NUMBER_OF_VALVES; i++)
  {
    msg1valve[i] = new MyMessage (i,V_LIGHT);
    var1valve[i] = new MyMessage (i,V_VAR1);
    var2valve[i] = new MyMessage (i,V_VAR2);
  }
}

void loop() {
  // put your main code here, to run repeatedly:
}

Edward

@kalle

V1 of the board had problems. V2 boards just shipped out of HK and should be here within a week or two...
I'll start updating info with the changes in the mean time as it has changed a little bit.

Happy to provide you with the files needed to get them ordered.
Just want to wait to test the boards before I post them...
If you rather not wait, I can give you the Eagle files so you can verify and send the order in to get them produced.
I can send a couple of boards for you to test before getting a lot of them produced as well..

Edward

@bjornhallberg just got the boards yesterday... A few cuts using the stanley knife and .. snap - I have two boards.. Hope to fire it up this weekend... Open to any and all suggestions..

I guess the goal of this board is really for non-battery usage. There are lots of boards focusing on the battery version.. But we can see if this board can be utilized to support the battery as well....

I have a question out to @Bandra to see how his board with the radio installed over the Arduio is functioning. If there are no negative effects, I may change mine to that layout...

So this board can be Fed Unregulated V+, or 5V regulated, or 3v3 regulated.

If supplying unregulated, install a regulator (5v or 3v3)
If supplying 5v regulated or installed a 5v regulatore, install a 3v3 regulator for the radio
If supplying 3v3 regulated use the board without any regulators

The AMS1117 is to use when the supply voltage is 5V or a 5v Regulator is installed - the AMS1117 is used to generate the 3v3 needed for the Radio. Can check if the LE33A in the store is pin compatible and use it instead on the board. Is this what you are suggesting?

The EEPROM is interesting - At this point, haven't thought of it. Is the big need so it can be used in OTA programming?

The Protoarea are not SMD pads, they are holes. But, it's possible to change them (Option 2 board if there is a lot of interest)

@Bandra how are the boards working out?

Any issues with the Radio over the Arduino in terms of the RF capabilities?
I'm thinking I would like to change my board layout to have the radio like yours to save some real estate on the board if there are no negative consequences..

Thanks,
Edward