@samuel-wieczorek Hi Samuel. I positioned the sensor over the 1 liter wheel. I did not used the TCRT5000 module, but made a custom built PCB. Howver the principle is the same (in fact the schematics is 100% the same as the TCRT module.
If you go to https://www.openhardware.io/view/15/Itron-Aquadis-watermeter-sensor-V10 you can see pictures of the module. Some tips I can share with you:
Shield the sensor and the rotating disk area from incoming light. This influences the sensor. Use a piece of plastic tube for example. In NL we have electrical wire tubes that can be used (the grey ones)
Bring the sensor close to the disk. The reflection should do the rest. Setting up the TCRT is tricky as you have little room to manouver (considering reflection and the point where the schmit trigger swaps state)
Be aware that when the disk stops with the edge near the sensor you get false readings. That is why I swapped to a software driven solution using SW hysteresis on the arduino.
Hope this helps. If you can open it, I can share a DXF file with the sizes of the bottom plate I use. Let me know!

Ralph

Hi All,

Like the design thinking of this, although an older topic I did manage to get me one of these dishes. After taking it apart, I have one question that came to mind. Is the ventilation in the dish enough for the humity sensor? Is there any experience with that after running this sensor for a while?

Thx

Ralph

No hurries here! First celebrate the new year :-)

Hi dbemowsk,

Can you post some more details on your projects, like schematics

Thanks in advance!

Ralph

Hi There Sineverba,

Can you post some more details on this project, like the schematics.

A more detailed BOM would also be great!

Thanks!

Ralph

Hi all,

I. m facing similar problems. like you. I was working on upgrading my network to 2.1.1. I got stuck with strange behaviour of the GW. I programmed it with:
IDE version: 1.8.4
Arduino AVR release: 1.6.20
The latest 2.1.1 downloaded libraries and the latest GW version.

After connecting the GW to my network, i was perfectly able to ping it. MYScontroller could connect, however sending a command to the gateway rusults in an error (ERROR 10054).

I've been fighting with it for a day, exchanging compontents, rebuilding SW, etc.

Here is what solved it!
Changed the AVR release to 1.6.11

I know there are problems in AVR 1.6.X, but these should have been solved in 1.6.18 and higher. Apperantly that is not the case.

I hope this helps!

Ralph

@Reza Ok, and you did check the library compiled with your sketch is the correct one? the error is exactly the same as I had, so it really looks like you are using a different library. This is a tricky thing, so please check. What IDE are you using?

@Reza Hi Reza, sorry for the little delay in replying. Anyway, read the response of @mfalkvidd 4 steps up. He gives the link for the correct library. If that does not work, there might be another problem with your libraries. Did you check if you really are using the correct one. Sometimes the old one is persistent, so you think you have the correct one, but in practice you don't. Compare the one you have downloaded with the one in your IDE to be sure.

Ralph

@xydix NRF modules are sensitive to power fluctuations, so take care that you have a stable source. Is the booster of good quality or producing noise on the power lines?. The converter can produce a high frequency signal on the powerline, also know as noise. You can try to filter the noise with a small capacitor like 100nF or maybee even smaller depending on the freqency of the noise coming from the booster.
My problem was/is the distance between the GW and the sensor currently, other problems were related to power as well, solved for now (see above my findings)

@rubyan Sounds like power trouble and/or distance between GW and sensor. Powering from the Nano is in genaral not a good thing. The supply might be to week. Use an external power source and some capacitors (see above) Also try to see if putting the GW and sensors at a distance helps.

@TheoL Agreed, better safe then sorry :-). I'm interested to see how the sensors will perform if they are close together (they will probably be in a class room kind of situation). I found that this is one of my biggest pitfalls. 1.5 was always ok, even on the same work bench. 2.0 is very critical in this in my experience. For myself I wonder how this is going to work in real life situations where sensors might be close range to eachother and to the GW. If have not enough sensors now to test this on 2.0 unfortunatly, but you will have I guess some during the workshop.

@TheoL Hi Theo, thanks for your feedback. Interesting workshop you do on Friday, unfortunately I can't participate due to work obligations. Regarding the cables, I understand your experience. When using Dupont cables, it's always good practice to keep the connections as short as possible. Capacitors are always a good addition. In designing electronics, its standard practice to at least add decoupling capacitors (generally around 100nF) closed to the power connections of your integrated circuits or modules. For the radio's in MySensors I would advise to add a larger capacitor of 4.7uF or 10uF over the power connections of the radio, preferably soldered on the radio module itself. I think this is also something to share with the participants coming Friday as design rules. Regarding the performance of mySensors V2.0.0, I have my thoughts. Version 1.5 was running flawless out of the box, V2.0.0 does not in my experience. Like to hear the thoughts and experiences you have especially after the workshop.

This indeed looks like a bad Nano. I rebuild it with a spare UNO and working. There is however one thing. The W5100 can be powered on 5V right? I do so on my "old" gateway. The W5100 does have its own step down regulator. This one is not working well at 5V. It's assigning the strangest IP adresses on 5V. On 3.3V it works ok. Anyone experienced this also, or is this also a bad W5100?

@tekka I more and more start to believe i'm dealing with a crappy Nano. Whatever power I use, I noticed it is assining a very strange IP address that is changing all the time. Also when I put it in my (exisiting) gateway board, it's getting hot.

@tekka Thx for the response. I will look into both in more details.
As for power: This is always a critical one, both gateway and nodes are power with a solid supply that I used before on all my nodes, so I don't expect much issues there. But I must say that I don't use 100uF as cap, so will see what that does.
As for interference: The GW and node are on one desk, so that might be a problem. I did not have this problem playing with earlier versions of MySensors, but since this is V2, there might be a change in comms that is of influence. Also there is GW on channel 76 nearby. This setup is on channel 1, so I don't know if the other GW gives interference. AP’s are all on a distance.

@mfalkvidd Aha clear, but the mismatch stays the same, isn't it? Anyway lets close this thread, DHT is running now, so I'm happy :-).

Hi All,

After stugling with V2.0.0 for a few days now, it's time to ask for help (again). I had troubles with radio's before, those are supposed to be fixed now.
I have A GW with W5100 (nano) and two sensors (Uno and Pro Mini) running. I changed the channel to 1 (#define MY_RF24_CHANNEL 1), as I also have a 1.5 network running on the standard channel 76. That is all I changed in the standard scripts.
The is no controller attached yet.

I now get the following log from the gateway (taken from MYSController):

[2016-08-30 14:44:27.217 Info] INFO	Connected to COM3
 [2016-08-30 14:44:28.705 Info] RX	0;255;3;0;9;Starting gateway (RNNGA-, 2.0.0)
 [2016-08-30 14:44:28.706 Info] CHILD	New child discovered, node id=0, child id=internal
 [2016-08-30 14:44:28.706 Info] RX	0;255;3;0;9;TSM:INIT
 [2016-08-30 14:44:28.706 Info] RX	0;255;3;0;9;TSM:RADIO:OK
 [2016-08-30 14:44:28.706 Info] RX	0;255;3;0;9;TSM:GW MODE
 [2016-08-30 14:44:28.707 Info] RX	0;255;3;0;9;TSM:READY
 [2016-08-30 14:44:29.008 Info] RX	IP: 192.168.0.211
 [2016-08-30 14:44:29.008 Info] ERROR	ErrorFlag=255, Msg=IP: 192.168.0.211
 [2016-08-30 14:44:32.017 Info] RX	VMDPV_1|1_VMDPV
 [2016-08-30 14:44:32.017 Info] ERROR	ErrorFlag=255, Msg=VMDPV_1|1_VMDPV
 [2016-08-30 14:44:32.017 Info] RX	0;255;3;0;9;No registration required
 [2016-08-30 14:44:32.017 Info] RX	0;255;3;0;9;Init complete, id=0, parent=0, distance=0, registration=1
 [2016-08-30 14:44:36.381 Info] RX	0;255;3;0;9;TSP:MSG:READ 1-1-255 s=255,c=3,t=7,pt=0,l=0,sg=0:
 [2016-08-30 14:44:36.382 Info] RX	0;255;3;0;9;TSP:MSG:BC
 [2016-08-30 14:44:36.382 Info] RX	0;255;3;0;9;TSP:MSG:FPAR REQ (sender=1)
 [2016-08-30 14:44:36.382 Info] RX	0;255;3;0;9;TSP:CHKUPL:OK (FLDCTRL)
 [2016-08-30 14:44:36.382 Info] RX	0;255;3;0;9;TSP:MSG:GWL OK
 [2016-08-30 14:44:36.962 Info] RX	0;255;3;0;9;!TSP:MSG:SEND 0-0-1-1 s=255,c=3,t=8,pt=1,l=1,sg=0,ft=0,st=fail:0
 [2016-08-30 14:44:38.447 Info] RX	0;255;3;0;9;TSP:MSG:READ 1-1-255 s=255,c=3,t=7,pt=0,l=0,sg=0:
 [2016-08-30 14:44:38.447 Info] RX	0;255;3;0;9;TSP:MSG:BC
 [2016-08-30 14:44:38.447 Info] RX	0;255;3;0;9;TSP:MSG:FPAR REQ (sender=1)
 [2016-08-30 14:44:38.449 Info] RX	0;255;3;0;9;TSP:CHKUPL:OK (FLDCTRL)
 [2016-08-30 14:44:38.449 Info] RX	0;255;3;0;9;TSP:MSG:GWL OK

The radio gives the following log (from direct serial log):

Opening port
Port open
Starting sensor (RNNNA-, 2.0.0)
TSM:INIT
TSM:RADIO:OK
TSP:ASSIGNID:OK (ID=1)
TSM:FPAR
TSP:MSG:SEND 1-1-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
TSM:FPAR
TSP:MSG:SEND 1-1-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
TSM:FPAR
TSP:MSG:SEND 1-1-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
TSM:FPAR
TSP:MSG:SEND 1-1-255-255 s=255,c=3,t=7,pt=0,l=0,sg=0,ft=0,st=bc:
!TSM:FPAR:FAIL
!TSM:FAILURE
TSM:PDT 

As you can see failures on both ends. As the two nodes show the same behaviour, I suspect the problem lies with the GW.
Does anyone have a hint where to look.
Thx

Ralph

@mfalkvidd I agree, it's always difficult if your solution depends on external libraries. However if we use a modified version of DHT in our MySensors, we should not call it DTH, but something like MyDHT. That makes it specific for MySensors. Currently the risk is that a DHT library is in the library directory that is not standard, other sketches (non MySensors) might break on it.

I did download the full set you suggested already and applied it. The error is now gone. Now for me to sort out why radio's are not communicating, but that is off topic...

Ralph

@mfalkvidd This one: https://github.com/mysensors/MySensorsArduinoExamples/tree/master/libraries/DHT at the bottom is installation with a link to a ZIP file called DHT, this downloads the libray files.

Thx for the help by the way. Much appreciated!

Regards,
Ralph

@mfalkvidd: No, I only have one, I double checked. But you are write about the DHT lib, that is where it is going wrong. I see that you are looking in the branch itself, The version I used is from the ZIP (at the bottom of the read-me) That version differs a lot:

82  protected:
83  void readSensor();
84
85  float temperature;
86 float humidity;

That is where the error is, different version in the referenced ZIP. Confusing and put me on the wrong track :-(.

Thx
Ralph

@hek: I started with using the new DHT sketch (v1.1) from git. When opening the sketch in Visual Studio, it reports an error on: dht.readSensor(true); apperently this is not an allow function from the DHT library. The error message is:

I used the DHT library form mysensors Git.

Do you have any suggestions on this?

Thx

Ralph