vThings Forums

Full Version: co2 monitor v3 /cdm7160 stops sending information/ jamming 433mhz rf devices
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3 4 5
Hm, I get neither I think. I don't see any value for D6 at all:
Code:
[Scheduling command: gpio_set D6 0
gpio_set D6 0
ready >]
[Scheduling command: gpio_set D6 F
gpio_set D6 F
ready >]
[Scheduling command: gpio_get D6
gpio_get D6
ready >]
yeah.. i am sorry, the current firmware has the line that dumps the status commented
I noticed it right after i sent the post, but then forgot to upload it before i went to work - i will upload it in the evening
ok, now you can update to the latest fw
Ok, thanks. Now I get this:
Code:
[Scheduling command: gpio_set D6 0
gpio_set D6 0
ready >]
[Scheduling command: gpio_set D6 F
gpio_set D6 F
ready >]
[Scheduling command: gpio_get D6
gpio_get D6
GPIO:D6(12) :0
ready >]
Which means the hardware is fine? Whats the problem then? Sad
strange..
can you verify if is is connected correctly, i do not know if there is an option to connect it wrongly and it still to be working but just in case

this is how it looks like
It goes to a connector on the board with pins

G -> Gnd
D6 -> Data
5v -> VCC

if you have a voltmeter, you can also try to measure the voltage between the data pin and gnd when it is off
it should be 0volts. i assume it is not and this is why it jams

Another thing you can measure is, when disconnecting the RF module, to measure the resistance between the Data and VCC pins (left and middle). It may be that the module is bad and it keeps the data pin HIGH, and while the device is working, it is ok as it keeps the pin actively low

i think in either case it is not software related issue, so i will send you a new board and rf module (but only next week, as now we will have holidays)
Until then you can set the "Go To Sleep" setting to 0, and it should work 
[Image: fa1000a_1_avr.jpg]
Ok, thank you. At the weekend I will try what you said and measure some things.
With the current firmware, setting the "Go To Sleep" to zero works so I can use the device now at least without jamming, thats good!
Enjoy your holidays and don't hurry! Thanks!
Well, I disassembled the sensor and quite some interesting things happened...


I disassembled everyhing and tried it again and then it worked! I could send the device to sleep and the jamming did not occur anymore. But then again after assembling everything again, the jamming reappeared :/ I played around with it for about 1 hour (reordered the components in the case, checked the cables etc.) and sometimes it worked and sometimes it did not. It really seems to be an issue with the cables or maybe a component is not soldered correctly or somehing like that. Too bad I was not able to find the exact part that causes it, everything looked quite ok for me.
But in the end I was able to find a status where it is working now inside the closed case.

But it really seems somewhere in there there is something wrong. I also had another effect in this procedure:
At one moment the device didn't boot up properly anymore. When connecting power the LED went lila and nothing more happened. No connection via the config tool was possible. I power cycled like 5 times but it didn't change. I think in this status also the jamming was happening again. Then again I opened the cased and again reordered the componentsn, then it worked again.

Also I think sometimes the LED turned off sporadically, then later again it turned on again. That seemed quite random for me.
indeed, this is very strange.. did you try to measure the voltage between the Data and VCC pins on the rf module when the jamming occured ?
though now i realize that since it is behaving so strange, it may be ok, but in the moment you move it - to become bad again
I tried to reproduce the jamming again to messure the voltage but I could not force it by dis-/reassembling Sad

But I still found a "bug": The cable of one the pins of the CO2-sensor was very loose and could be pulled without any resistance. It felt like it had barely a connection at all. I think that was the reason for my problem when the device did not boot up properly but just stayed on lila LED when booting. That is exactly what is happening when I pull the cable deliberately and then try to boot.
To fix it I removed the black casing of the cable and pressed the metal parts togehter so it now has grip when putting it onto the pin.
[Image: DSC_0139.JPG]

I don't know if this could also be related to the jamming problem.
ahhhh... i didn't expected problems from this kind, but perhaps it was some faulty cable.. i will have to check better when assembling them if they are loose.

i will also need to fix the firmware so that it doesn't hang in case some cable has disconnected

i do not thing this is related to the jamming though - so it shouldn't have fixed it right ?

( i am still waiting to get my new boards, this week, then i will send you a new one to test)
Pages: 1 2 3 4 5