Posts made by ikkeT

@nca78 You can't really add one more battery, or you fry the radio which can handle only 3 and some Volts, right? If doing so, one needs to add step down regulator, so again loosing voltage. Or am I wrong?

Just to give an update anyone building similar setup. I managed to find a day to fix the systems. I thought the step-up booster is causing noise, so I added a capasitor to step-up output. It stabilised it enough so PIR doesn't give false alarms any more. Pheeeew... Finally working properly.

Thanks a lot for sharing this! I already did the Arduino and MySensors stuff, and started thinking of writing program for it. I'm glad I found this, it fit exactly what I was doing. Here's your code a bit modified, and added some different kind of lamps for the next one looking for references: https://github.com/ikke-t/Arduino-RGB-leds-and-lightbulbs/blob/master/README.md

The additional piece here is how to command this from OpenHAB, as that's my controller. One needs to modify the RGB info via rules, it's there for reference:

https://github.com/ikke-t/Arduino-RGB-leds-and-lightbulbs/raw/master/src/rgb.rules

There are links within that file to references for how to create similar rules for RGB mangling.

@Ngwpower after 10 months experience, I've modified things a bit. I never got to smaller batteries, as my access to 3D printer is quite rare. I have run into some problems with this setup.

1. PIR sensor is picky about the voltage. It starts soon creating false alarms after batteries get a bit lower on voltage. It expects good 3.3V. To fix this I added voltage boster to suck out all the power from batteries to keep it in steady 3.3V. It worked (for a while).

2. The 2.4Ghz radio is not a good idea in concrete house, along with neighbors wifis. I have lost signal from 1/3 sensors. I don't know really why, I suspect the radio signal strength and interference.

3. I think batteries won't last now for so long after putting in the voltage pump. I really don't know why, I haven't investigated, but devices disappear after some weeks. The one without voltage pump stays there for months.

4. PIR sensors again give false alerts. I don't know if it's due the heating during the winter, or dirty voltage that the voltage pump outputs.

It could be that I should just change the batteries and reboot all of them, but I haven't got around to do it now. But if you add the voltage pump, make sure to add capacitor to steady the radio power.

Temperature and door open/closed circuit works well. I wish I get the motivation to fix all the above one day soon

Good luck, and report back the enhancements!

Excellent, thank you. It's too long since I've done serious coding, I didn't remember that. atoi -> atol fixed it.

The point in the above is, the Serial.print converts it correct, the atoi doesn't.

Thanks, now it looks different, doesn't still work though. Perhaps the atoi doesn't do longs properly?

Received something of type: 32
V_IR_SEND command received...
V_IR_SEND data invalid: 16236607, ircode: 4294950975

that turns out to be:

echo "obase=16;4294950975"|bc
FFFFC03F

How does it come up with that? Need to hurry to work now, later...

Hi,

I'm puzzled how message receive happens. I am building a infrared transmitter. I decoded the NEC signals from original remote, they look like this (hex): 0xF7C03F. This is power on command.

Now I want to send those signals over MQTT, which mysgw transfers over NRF24L01+ to arduino. But how to convert messages so that they look alike at both ends? is that number too big to send (3 bytes)?

As I send that exact command from arduino:

#define CMD_ON        0xF7C03F
...
send(msg_ir.set(CMD_ON));

it looks like this on MQTT looking from mosquitto_sub:
MySensorsGW/out/7/1/1/0/32 16236607

When I send that back:
mosquitto_pub -h droidcam.ikenet -p 1883 -t MySensorsGW/in/7/1/1/0/32 -m 16236607

the code:

uint32_t ircode;
ircode = atoi( message.data );
...
        Serial.print( "V_IR_SEND data invalid: " );
        Serial.print( message.data );
        Serial.print( ", ircode: " );
        Serial.println( ircode );

prints it out like this:
V_IR_SEND data invalid: 16236607, ircode: 4294950975

the numbers don't match. 16236607 is not the original CMD_ON code.

This is the receive function:

// IR remote command codes
#define CMD_BRIGHTER  0xF700FF
#define CMD_DIMMER    0xF7807F
#define CMD_OFF       0xF740BF
#define CMD_ON        0xF7C03F
#define CMD_FLASH     0xF7D02F
#define CMD_STROBE    0xF7F00F
#define CMD_FADE      0xF7C837
#define CMD_SMOOTH    0xF7E817
#define CMD_RED       0xF720DF
#define CMD_RED1      0xF710EF
#define CMD_RED2      0xF730CF
#define CMD_RED3      0xF708F7
#define CMD_RED4      0xF728D7
#define CMD_GREEN     0xF7A05F
#define CMD_GREEN1    0xF7906F
#define CMD_GREEN2    0xF7B04F
#define CMD_GREEN3    0xF78877
#define CMD_GREEN4    0xF7A857
#define CMD_BLUE1     0xF7609F
#define CMD_BLUE      0xF750AF
#define CMD_BLUE2     0xF7708F
#define CMD_BLUE3     0xF748B7
#define CMD_BLUE4     0xF76897

void receive(const MyMessage &message)
{
  uint32_t ircode;
  Serial.print( "Received something of type: " );
  Serial.println( message.type );

	if (message.type == V_IR_SEND) {
		Serial.println( "V_IR_SEND command received..." );

		ircode = atoi( message.data );
    //ircode = message.data;
    switch (ircode) {
      case CMD_BRIGHTER:
      case CMD_DIMMER:
      case CMD_OFF:
      case CMD_ON:
      case CMD_FLASH:
      case CMD_STROBE:
      case CMD_FADE:
      case CMD_SMOOTH:
      case CMD_RED:
      case CMD_RED1:
      case CMD_RED2:
      case CMD_RED3:
      case CMD_RED4:
      case CMD_GREEN:
      case CMD_GREEN1:
      case CMD_GREEN2:
      case CMD_GREEN3:
      case CMD_GREEN4:
      case CMD_BLUE1:
      case CMD_BLUE:
      case CMD_BLUE2:
      case CMD_BLUE3:
      case CMD_BLUE4:
      {
        Serial.print( "V_IR_SEND code received: ");
        Serial.println( message.data );
        send_ircode(ircode);
        ack_ir_to_controller(ircode);
        break;
      }
      default:
      {
        Serial.print( "V_IR_SEND data invalid: " );
        Serial.print( message.data );
        Serial.print( ", ircode: " );
        Serial.println( ircode );
			  return;
		   }
    }
  }
  for (int i=0; i<5; i++) {
    digitalWrite(LED_PIN, HIGH);
    wait(100);
    digitalWrite(LED_PIN, LOW);
    wait(100);
  }
}

I suppose it has to do with data length and auto conversion of variables. It perhaps worked if I use smaller numbers to set the IR code value. But however, I'd like to understand how this is supposed to work?

BR,
-ikke

PS, this is IR controlled LED light bulb from LIDL, and commands do work with the given codes.

I'm going to test how long such would work with button batteries (CR2032, 3V), and if it's long time, I could make smaller case. So far it's been on about half an year at least with two AA batteries.

One could actually stack e.g. three of those CR2032 batteries and wire them parallel in half of the size casing. Creating like "Shelves" for the batteries in the case, where they could slide in.

No I don't mind, I'm happy if someone finds it useful. Go ahead

Hi home automators,

I thought I share back my case here from thingiverse for those who do want to monitor home with sensebenders and alike. I draw and 3d printed this case for my sensebender and motion + door trap sensors. One of them is running with arduino pro mini, as I didn't have sensebender for that. It's a bit tight for that, but does it's job. Feel free to modify it, and please notify me if you enhance it, so I'll get the enhancements as well

http://www.thingiverse.com/thing:2144946

The angle on the motion sensor allows me to point the PIR range to certain parts where I want it, by placing the case in different ways. Turn to left, right or put it above the door to aim all over.

It's not state of art, but my first 3d drawing and my first arduino job. Code is pretty much copy paste from here. The device sleeps until sleep timer hits, or motion or door trap interrupts the sleep. To get the interrupt for both, you need to leave arduino pin 2 unused from the NRF24L01+ radio, as that reserves the edge interrupt pin from sensebender. There are only 2 edge interrupt pins on those arduinos.

The code is here for the devices, like said mostly copy paste (fork): https://github.com/ikke-t/sensebender

Mysensors GW on raspi forwards the traffic as MQTT forward to my node-red. That then sends gtalk messages of events if alarm is on. I recently also added openhab to listen to MQTT bus just out of curiosity.

My sample is here, unfortunately I didn't see this thread before starting it
It works for temp, humidity, door and motion, and interrupts for door and motion, otherwise sleeps the intervals:

https://github.com/ikke-t/sensebender

There is also pro-mini to code to monitor only door and motion.

This is also for 2.0 MySensors.

Hi,

please share your experience of setting MQTT to work with Domoticz and MS GW. Should the traffic be changed to json format or what's the deal?

I got the MySensors Raspi GW work ok, sending stuff to remote MQTT mosquitto server. The config is this:

./configure --my-gateway=mqtt --my-controller-ip-address=192,168,1,32 --my-port=1883 --my-mqtt-client-id=22 --my-mqtt-publish-topic-prefix=domoticz/in --my-mqtt-subscribe-topic-prefix=domoticz/out --my-rf24-pa-level=RF24_PA_LOW 

Unfortunately it won't show anything in Domoticz. I googled a bit and someone wrote Domoticz reads data in json format? Is that true? Sounds a bit weird in case of MQTT.

I'm rather close now getting things to work, please any tips welcome, too tired to google more tonight...

MQTT part is fine:

$ mosquitto_sub -t domoticz/in/# 
23.0
40

nevermind. now after all upgrades AND BATTERY CHANGE to sensebender it's all fine

after upgrading to above mentioned 3.1.1 version from wheezy, the mysensors start to print out it sends stuff. can't see it on subs yet though.

My mosquitto is mosquitto 3.1 - 0.15-2ubuntu1 (from ppa) and mysensors is up to date devel branch from github.

so this works:

MySensors $ mosquitto_pub -h 192.168.1.32 -t mysensors-from/0/1 -m "MySensors MQTT hello world from raspi to odroid"

mqtt-host $ mosquitto_sub -t mysensors-from/#
MySensors MQTT hello world from raspi to odroid

I'm also trying mqtt. somehow I can't see the messages:

MySensors $ ./configure --my-gateway=mqtt --my-controller-ip-address=192,168,1,32 --my-port=1883 --my-mqtt-client-id=22 --my-mqtt-publish-topic-prefix=mysensors-from --my-mqtt-subscribe-topic-prefix=mysensors-to --my-rf24-pa-level=RF24_PA_LOW 
MySensors $ sudo make install
...
MySensors $ sudo mysGateway -d
...
mysGateway: Attempting MQTT connection...
mysGateway: connected to 192.168.1.32
mysGateway: TSF:MSG:READ,8-8-0,s=255,c=3,t=15,pt=6,l=2,sg=0:0100
mysGateway: !TSF:MSG:SEND,0-0-8-8,s=255,c=3,t=15,pt=6,l=2,sg=0,ft=0,st=NACK:0100
mysGateway: TSF:MSG:READ,8-8-0,s=255,c=0,t=17,pt=0,l=10,sg=0:2.0.1-beta
mysGateway: TSF:MSG:READ,8-8-0,s=255,c=3,t=6,pt=1,l=1,sg=0:0
mysGateway: Attempting MQTT connection...
mysGateway: connected to 192.168.1.32
...

So GW attempts to send some stuff to mqtt server elsewhere, like that version string. But this on the server prints nothing:

$ mosquitto_sub -t mysensors-from/*

I also tried with # instead of *

I've verified mqtt works, if I pub that from mqtt client, it works.

@TimO ah, ok, explains as I don't have contoller configured yet. I assume it's then only such controller that speaks MySensors, not anything behind mqtt?

hmmm.... this went accidentally to hardware section. I was aiming for troubleshooting. Oh well...

Hi,

I was wondering why couple of my boards didn't register to gateway. They kept looping the three lines that happens if hand shake fails. Then I thought to try fixed ids.

+//#define MY_NODE_ID AUTO
+#define MY_NODE_ID 3

I changed the above, and surprise, both of the boards do work now. Is that auto node id assignment not working in such way? MySensors 2 in question, the devel branch.

Or is this not even supposed to work, and I'm wasting everyone's time?

BR,
ikke

I also confirm it fixed my problem. Thank you!

@Yveaux Thanks, I was following the thread. I confirm, the change fixed my problem too, excellent.

@tekka, the versions are:

Mysensors is development branch, I didn't pay attention while cloning, it's set to default to development:

commit 8cacb4825b256f63aa2fc51468fd11a90bb19678
Merge: 75a100f 8ccb1ca
Author: Patrick Fallberg <patrick@fallberg.net>
Date:   Thu Sep 22 19:02:11 2016 +0200

Arduino IDE is 1.6.4

$ rpm -qa arduino*
arduino-core-1.6.4-8.fc24.noarch
arduino-doc-1.6.4-8.fc24.noarch
arduino-1.6.4-8.fc24.noarch

My IDE board manager shows Arduino AVR boards version 1.6.7, and it seems there is newer one available, 1.6.14. I will update that.

Mysensors AVR board definition for Micro version is 1.0.1

@tekka the scetch is here along with the libraries, just use it as Arduino folder to reproduce:

https://github.com/ikke-t/sensebender

I'll check the versions tomorrow (UTC+3). The arduino ide is 1.6.xx whatever is the very latest in Fedora 24.

@cimba007 I cloned the master branch from git about week ago. Or which ever is the default. I'll come back tomorrow, already in bed now.

I hope you catch it, as I believe I'm hit by the same bug. It the happens similar way on Sensebender Micro & NRF24L01+. I have a thread on troubleshooting forum with topic of interrupt mystery. I'm arduino newbie, so I'm not much help. I'm just about to try it on Arduino Pro mini just for comparison.

Somehow the enbling of interrupts lock it within a minute or so. If no interrupt enabled, no locking.

BR,
Ikke

But weird still. If I set the sleep time to 10 secs, without interrupts it works just fine. If interrupts are enabled, it stops always in less than ten rounds. So could it be the interrupts break the radio part somehow? E.g. if interrupt comes during transmit? Are interrupts safe in arduino, or should there be some lock set or disable interrupts for time of radio transmit?

Solved the scrambled test. I removed the interrupts, and made it loop faster. It always got screwed after five rounds, so it seemed to be due the clock speed change in the template:

#ifndef MY_OTA_FIRMWARE_FEATURE
  if ((measureCount == 5) && highfreq) 
  {
    clock_prescale_set(clock_div_8); // Switch to 1Mhz for the reminder of the sketch, save power.
    highfreq = false;
  } 
#endif

Removing that takes it further. I suppose the sample code is missing something to fix the serial speed after prescaler change. I also wonder if the radio would require some reconfig after clock speed change?

Good news and bad news... I got change based interrupts to work by moving the motion to D2. That required cutting off the radio IRQ. Naturally I lost one radio there cutting too much....

So now it works initially. But after some rounds the serial text gets garbled, and it stops sending anything quite soon then.

isMetric: 1
TempDiff :127.31
HumDiff  :151.00
T: 27.31
H: 51
TempDiff :0.01
HumDiff  :0.00
Door  :0
Motion:1
TempDiff :0.01
HumDiff  :0.00
Door  :0
Motion:0
TempDiff :0.07
HumDiff  :0.00
Door  :0
Motion:1
TempDiff :0.10
HumDiff  :0.00
Door  :0
Motion:0
x00�����x00�����x00�x00x00��x00��x00x00�x00x00�x00x00x00�x00x00x00x00�x00�x00x00x00x00��x00x00�x00x00x00���������```

the last line contines for long. Any ideas what could cause it? Some trick I missed with interrupts?

Again, the fixed code is here, it's almost the original SB Micro sample:
https://github.com/ikke-t/sensebender/blob/master/SenseBender/SenseBender.ino

@hek thanks, this clears the topic. I'll try cutting off the D2 and reuse that. I'll report back...

I used pins 3 and 4 for the interruptible input from sensors. What does D2 have to do with this in my case, if none of the code is using it for interrupts?

I brought d2 and d3 up because some sample codes for sensors mentioned that only those can be used for interrupts. But I assume now this is not the case for SB, thanks to the pic above.

According to the above pic, there is plenty of interrupt pins. If thats what the int means in their name. Why can't I use other than the D2 for interrupt, and make sure D2 is not used for interrupts?

Is it safe to cut off radio irq pin? So it's not used by the MySensors code?

Hi,

I don't get interrupts working for door and PIR sensors. Any help appreciated.

I connected door trigger on pin 3 (I assume thats D3) and PIR motion sensor on pin4 (D4). They are defined like this in code:
https://github.com/ikke-t/sensebender/blob/master/SenseBender/SenseBender.ino#L114

#define DOOR_PIN       3
#define MOTION_PIN     4

Then I try do stuff based on their value, waking up interrupt as described here:
https://www.mysensors.org/download/sensor_api_20#sleeping

  sleep(digitalPinToInterrupt(DOOR_PIN), CHANGE,
        digitalPinToInterrupt(MOTION_PIN), CHANGE,
        MEASURE_INTERVAL);

Somehow I don't get any changes from the PIR, and The door sensor only sends when the door opens. But then after couple times printing out values the serial from SB micro just goes bananas, outputting junk instead of readable stuff. Do the use of wakeup interrupt screw up the serial output?

Another mystery is, that I read from some sample codes that only pins 2&3 can cause interrupts. But I don't see it mentioned in SB Micro page. And there is no D2 in SB micro, I assume it's used by the internal sensors. Is this true with SB Micro?

So any idea how to make me understand how wrong I am?

The code and all the necessary libraries are here:
https://github.com/ikke-t/sensebender/blob/master/SenseBender/SenseBender.ino

BTW, the door sensor worked fine until I changed it to be interruptible. But I don't want to poll in loop.

Thanks,
ikke

@hawk_2050 thanks for the reminder! I recalled it was somehow configurable, but I forgot it was through . /configure options. I'll try after getting pir working also.

Continuing the learning here, new questions... Thanks so far, I've now got the temp/hum/door messages sent and received from sensebender micro to raspi2. The next thing I would like to do is to send the messages as mqtt to the next box hosting some controller.

How to get the mysGateway to send the stuff forward as mqtt? I tried to look into Makefile, MyConfig.h and such, but didn't quite figure out yet how to do that. Any pointers?

So I'd like to have the following: sensebender -> radio -> raspi2 -> some box hosting the controller. Perhaps even outside of home, so routable traffic e.g. to OpenShift.com.

Should I now somehow configure and build mysGateway to send stuff as MQTT, or pipe the traffic somehow to mqtt like mosqitto? How is this normally done if the controller server is not running on the gateway Raspi?

Thanks for the patience, I'm just getting into all this interesting stuff

OK, then I just screwed up something. Thanks for the info, so I know I can do this also with my old raspi one day. My old raspi dates 2011.12 on it. Well served.

OK, then I just screwed up something. Thanks for the info, so I know I can do this also with my old raspi one day.

Just FYI for someone googling this, it works immediately with Mysensors 2.0 with Raspi2 instead of Raspi1. The problem was I never realized the pinouts were not for the raspi with 26 pins but the raspis with 40 pins, like b+/2/3.

Yahooo! It works, finally. I bet my problem was Raspi1 all along. I never realized the pinouts in github were for raspi with 40 pins, b+/2/3. Thanks!

@mfalkvidd Thanks, I now compiled the 2.0 version, and about to wire it up. It's a bit shame that in many of the pinout descriptions it's not mentioned clearly which version of raspi pinout it is. The picture in this one is clear, it leaves no doubts.

So this 1.6 pinout would still apply? https://forum.mysensors.org/topic/2437/step-by-step-procedure-to-connect-the-nrf24l01-to-the-gpio-pins-and-use-the-raspberry-as-a-serial-gateway-mysensors-1-x

No, looking it again, it's vice versa, so yours is for Raspi2, right?

@marceloaqno , I assume your link for the wiring pinout behind the link is for Raspi 1 A+ with 26 pin header? Or for which version?

I'd like to try this with raspi 2 B, would you have instructions how to wire it?

Raspi2:

Raspi1:

Thanks

Thanks, and now that I had a second thought, I recalled I already wired another arduino once via serial ports without usb. That would do. But I would like to do it without extra arduino, so I'll try the raspi2 + mysensors hinted in the other hardware thread. It seems to work for some, I'll give it a shot.

Hi,

as I'm having troubles with connecting my raspi1A and sensebender both with mentioned radios, I thought I switch to Raspi2B for trial. I failed to google pinout diagram for Raspi2 and NRF2L01+ , which to use with MySensors. I got a bit worried looking at the pinout differences between Raspi1 and Raspi2. Mainly that where should I connect the pins CE, CSN, SCK from radio to raspi2?

I assume this pinout is for the Raspi1 with 26 pins? https://github.com/mysensors/Raspberry

Here is a reference how someone uses radio with raspi2, but the pins used are not the same as with MySensors Raspberry example: https://www.element14.com/community/community/raspberry-pi/raspberrypi2/blog/2015/04/07/raspberry-pi-2-gpio-usage-with-nrf24l01-arduino

I assume I could switch those from the MySensors code too. But I bet I'm late to the game, and someone would already have figured out the answers before me

@hek to be honest, it's going to take some time, as I have yet no glue how I would attach it to my raspberry

@hek I'll try that.

Damned. I changed both of the radios, and the sensebender. No help. Still no connection forming. Is there some radio parameters I could try tweaking? Or am I so unlucky that all the radios are broken as new?

I get lots of these:
!TSM:FPAR:NO REPLY
TSM:FPAR
TSF:MSG:SEND,8-8-255-255,s=255,c=3,t
=7,pt=0,l=0,sg=0,ft=0,st=bc:

!TSM:FPAR:NO REPLY
TSM:FPAR
TSF:MSG:SEND,8-8-255-255,s=255,c=3
,t=7,pt=0,l=0,sg=0,ft=0,st=bc:

!TSM:FPAR:FAIL
TSM:FAILURE
TSM:FAILURE:PDT

and on raspi side some of these:

read: 8-8-255 s=255,c=3,t=7,pt=0,l=0:
send: 0-0-8-8 s=255,c=3,t=8,pt=1,l=1,st=ok:0
read: 8-8-255 s=255,c=3,t=7,pt=0,l=0:
send: 0-0-8-8 s=255,c=3,t=8,pt=1,l=1,st=fail:0
read: 8-8-0 s=255,c=3,t=24,pt=1,l=1:1
read: 8-8-255 s=255,c=3,t=7,pt=0,l=0:
send: 0-0-8-8 s=255,c=3,t=8,pt=1,l=1,st=fail:0
read: 8-8-255 s=255,c=3,t=7,pt=0,l=0:
send: 0-0-8-8 s=255,c=3,t=8,pt=1,l=1,st=fail:0
read: 8-8-255 s=255,c=3,t=7,pt=0,l=0:
send: 0-0-8-8 s=255,c=3,t=8,pt=1,l=1,st=fail:0
read: 8-8-255 s=255,c=3,t=7,pt=0,l=0:
send: 0-0-8-8 s=255,c=3,t=8,pt=1,l=1,st=ok:0
read: 8-8-255 s=255,c=3,t=7,pt=0,l=0:
send: 0-0-8-8 s=255,c=3,t=8,pt=1,l=1,st=ok:0
read: 8-8-255 s=255,c=3,t=7,pt=0,l=0:
send: 0-0-8-8 s=255,c=3,t=8,pt=1,l=1,st=fail:0

and now after while there are occational OKs:
send: 0-0-8-8 s=255,c=3,t=8,pt=1,l=1,st=ok:0
read: 8-8-255 s=255,c=3,t=7,pt=0,l=0:
send: 0-0-8-8 s=255,c=3,t=8,pt=1,l=1,st=ok:0
read: 8-8-255 s=255,c=3,t=7,pt=0,l=0:
send: 0-0-8-8 s=255,c=3,t=8,pt=1,l=1,st=ok:0
read: 8-8-255 s=255,c=3,t=7,pt=0,l=0:
send: 0-0-8-8 s=255,c=3,t=8,pt=1,l=1,st=ok:0

BTW, this is the output on Raspi side, somehow it sees the nodeid 8:

$ sudo PiGatewaySerial
Starting PiGatewaySerial...
Protocol version - 1.4
Created PTY '/dev/pts/1'
Gateway tty: /dev/ttyMySensorsGateway
================ SPI Configuration ================
CSN Pin = CE0 (PI Hardware Driven)
CE Pin = Custom GPIO25
Clock Speed = 8 Mhz
================ NRF Configuration ================
STATUS = 0x0e RX_DR=0 TX_DS=0 MAX_RT=0 RX_P_NO=7 TX_FULL=0
RX_ADDR_P0-1 = 0xa8a8e1fc08 0xa8a8e1fc00
RX_ADDR_P2-5 = 0xff 0xc4 0xc5 0xc6
TX_ADDR = 0xa8a8e1fc08
RX_PW_P0-6 = 0x20 0x20 0x20 0x00 0x00 0x00
EN_AA = 0x3b
EN_RXADDR = 0x06
RF_CH = 0x4c
RF_SETUP = 0x23
CONFIG = 0x0e
DYNPD/FEATURE = 0x3f 0x06
Data Rate = 250KBPS
Model = nRF24L01+
CRC Length = 16 bits
PA Power = PA_LOW
read: 8-8-255 s=255,c=3,t=7,pt=0,l=0:
send: 0-0-8-8 s=255,c=3,t=8,pt=1,l=1,st=fail:0
read: 8-8-255 s=255,c=3,t=7,pt=0,l=0:
send: 0-0-8-8 s=255,c=3,t=8,pt=1,l=1,st=fail:0
read: 8-8-255 s=255,c=3,t=7,pt=0,l=0:
send: 0-0-8-8 s=255,c=3,t=8,pt=1,l=1,st=fail:0
read: 8-8-255 s=255,c=3,t=7,pt=0,l=0:
send: 0-0-8-8 s=255,c=3,t=8,pt=1,l=1,st=fail:0
read: 8-8-255 s=255,c=3,t=7,pt=0,l=0:
send: 0-0-8-8 s=255,c=3,t=8,pt=1,l=1,st=fail:0
read: 8-8-255 s=255,c=3,t=7,pt=0,l=0:
send: 0-0-8-8 s=255,c=3,t=8,pt=1,l=1,st=fail:0

Thanks for the tip. I do have RaspberryPi with nrf24l01+ and I have terminal open there with serial gateway running in foreground. The radio on raspi side seems to report it's address and info at the start. Only very rarely I see some read:* send: pairs there. Both radios have a 100uF capacitor in place, as I didn't have smaller.

Perhaps I need to try with a new radio. All the parts are brand new, apart from the Raspi.

To be clear, this is what the printouts are. I changed the NodeId to make sure the code being run is mine, so the upload succeeded:

TSM:INIT
TSM:INIT:TSP OK
TSM:INIT:STATID,ID=8
TSF:ASID:OK,ID=8
TSM:FPAR
TSF:MSG:SEND,8-8-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
!TSM:FPAR:NO REPLY
TSM:FPAR
TSF:MSG:SEND,8-8-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
!TSM:FPAR:NO REPLY
TSM:FPAR
TSF:MSG:SEND,8-8-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
!TSM:FPAR:NO REPLY
TSM:FPAR
TSF:MSG:SEND,8-8-255-255,s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
!TSM:FPAR:FAIL
TSM:FAILURE
TSM:FAILURE:PDT

Hi,

I'm finally starting to do something with the SenseBender micros that I bought. But I fall in the very first steps. None of the debug prints come out, any idea why?

I took the sensebender sample code from github, and tried modifying it a bit to see the my version uploads and runs. For some reason none of the debug prints show up. However, the MySensors printouts do come out of the serial. What could block this, is there some hidden define for printfs that I just don't see?

I uploaded the code here: https://github.com/ikke-t/sensebender

That's the whole ~/Arduino directory, which I just created from scratch to be sure. All my changes are in SenseBender/SenseBender.ino file history. The changes are pretty much trying to enable the printouts.

I've tried setting the serial speed to 115200 and 57600. Both do print out the MySensors printouts, but none of the Serial.print lines from SenseBender.ino.

I have SenseBender micro board, and I soldered NRF24L01+ onto it, along with battery case. The NRF24L01+ has 100uF capacitor added for stable voltage.

Thanks for any help, I'm pretty sure it's something rather trivial I just don't see

BR,
ikke

I just hit the same. Some update gone bad?

@hek thanks, that did it. To be precise, one should go to IDE preferences, and at the bottom of the dialog add the following URL into "Additional boards managers URLs:" field and hit OK:
https://raw.githubusercontent.com/mysensors/ArduinoBoards/master/package_mysensors.org_index.json

Editing the /usr/share/arduino/dist/package_index.json file does no good, as it will break the signature of the file.

Hi,

how to get Sensebender Micro to Arduino IDE's boards list? This guide page is outdated: https://www.mysensors.org/hardware/micro-ide-setup

I have Arduino IDE 1.6.4 in Fedora 24 Linux, and I've used the library manager to download the MySensors libraries. The Sensebender Micro board does not show up in boards list, nor does any MySensors related stuff in boards manager.

How should the programming be done? I have FTDI programmer connected to board, and I can see it prints out error messages from sending data. Occationally it succeeds according to printouts. So HW should be OK, I just don't know the method to add board to IDE, please help.

BR,

ikke