PMS7003 no readings

Moderators: Voyager, BertB, rtenklooster, Stuntteam, grovkillen, TD-er

Post Reply
Message
Author
User avatar
Malanow
Normal user
Posts: 12
Joined: 18 Mar 2018, 22:47
Location: Poland
Contact:

PMS7003 no readings

#1 Post by Malanow » 29 Dec 2018, 21:44

The problem is easy to explain, the sensor does not work. Displays only zeros.
Wiring diagram according to this information -> https://www.letscontrolit.com/wiki/index.php/PMSx003
Connections checked (several times).
I use Wemos D1 mini Pro, with mega-20181218 (ESP_Easy_mega-20181220_dev_ESP8266_4096.bin).
How do you check if the sensor works?
Armageddon was yesterday, today we have a serious problem.

BertB
Normal user
Posts: 991
Joined: 25 Apr 2015, 14:39

Re: PMS7003 no readings

#2 Post by BertB » 29 Dec 2018, 22:48

How did you configure the plugin and how did you wire the dust sensor?

User avatar
Malanow
Normal user
Posts: 12
Joined: 18 Mar 2018, 22:47
Location: Poland
Contact:

Re: PMS7003 no readings

#3 Post by Malanow » 29 Dec 2018, 23:13

I did everything as described in the wiki
Image
Image
Armageddon was yesterday, today we have a serious problem.

Shardan
Normal user
Posts: 1040
Joined: 03 Sep 2016, 23:27
Location: Bielefeld / Germany

Re: PMS7003 no readings

#4 Post by Shardan » 29 Dec 2018, 23:46

Just for a test:
Disconnect the connection from Sensor-SET to GPIO16 and connect the SET via a 10KOhm resistor to VCC (3.3V)

If something with rules does not work the GPIO16 might be permanently on "0" disabling the sensor.
Regards
Shardan

BertB
Normal user
Posts: 991
Joined: 25 Apr 2015, 14:39

Re: PMS7003 no readings

#5 Post by BertB » 30 Dec 2018, 16:28

When you put the Web log level to Debug en look in the web log window, don't you see messages like:

65666: PMSx003 : pm1.0=0, pm2.5=0, pm10=0, pm1.0a=0, pm2.5a=0, pm10a=32896
67466: PMSx003 : pm1.0=0, pm2.5=0, pm10=0, pm1.0a=0, pm2.5a=0, pm10a=32896
69274: PMSx003 : pm1.0=0, pm2.5=0, pm10=0, pm1.0a=0, pm2.5a=0, pm10a=0
71073: PMSx003 : pm1.0=0, pm2.5=0, pm10=0, pm1.0a=0, pm2.5a=0, pm10a=0

You could try to connect the PMS to an USB2Serial connector and see if it sends messages.

MadNBG
Normal user
Posts: 3
Joined: 28 Oct 2018, 20:11

Re: PMS7003 no readings

#6 Post by MadNBG » 08 Jan 2019, 18:59

PMS5003 - almost same.
My setup is exactly the same as in the wiki. Gpios pulled with 10k resistors, 47yF buffering 5V
Lifetime-helper rule working. (Replaced longpulse with timer - cause there is an issue.)

Problem:
When the Sensor gets actived by timer, it lasts at least 15sec. to get the values.
And this is not even sure!
In some cases during the 15sec. timer-on, no reading is comming.
(After this15sec power-on, the power is 30sec off. And again from the beginning.)
In other cases, there are 2 readings (á 3 values) direct behind each other.
Or, the Sensor gets off (gpio16 0) and THEN values come.


It is not possible to get realtime-data from the Sensor, nor is it possible switch the Sensor on for a short time, grab the data and off again.
In the wiki (lifetimehelper), the Sensor gets on for 5sec. I have no Chance to get data.
What can I do?

My rules - I found 15sec is the min. power-on for the sensor.:

Code: Select all

on System#Boot do
  gpio,16,0
  timerSet,1,30 //Mess-Start in 30 sec. 
endon

On Rules#Timer=1 do
  GPIO,16,1
  timerSet,2,15 //Messdauer - Datenübertragung 15 sec. 
  timerSet,1,45 // Messintervall 30 sec. (45-messdauer)
 endon

On Rules#Timer=2 do
  GPIO,16,0
//  Gpio,0,1 //reset
//  timerSet,3,1
 endon

//On Rules#Timer=3 do
//  Gpio,0,0
// endon 

Here's a typical log:

Gpio,16,1 = Sensor on
Timer1= 45sec
Timer2=15sec Sensor (Gpio16) on

Code: Select all

168565313: EVENT: Rules#Timer=1
168565324: ACT  : GPIO,16,1
168565326: SW   : GPIO 16 Set to 1
168565330: ACT  : timerSet,2,15
168565340: ACT  : timerSet,1,45
168565355: Command: timerset
168565356: Command: timerset
168581313: EVENT: Rules#Timer=2
168581328: ACT  : GPIO,16,0
168581330: SW   : GPIO 16 Set to 0
168582868: WD   : Uptime 2810 ConnectFailures 0 FreeMem 14288
168611313: EVENT: Rules#Timer=1
168611324: ACT  : GPIO,16,1
168611326: SW   : GPIO 16 Set to 1
168611330: ACT  : timerSet,2,15
168611339: ACT  : timerSet,1,45
168611355: Command: timerset
168611355: Command: timerset
168612868: WD   : Uptime 2810 ConnectFailures 0 FreeMem 14288
168613314: EVENT: Clock#Time=Tue,18:04
168619983: EVENT: Partikelsensor#pm1.0=4.00
168620002: EVENT: Partikelsensor#pm2.5=6.00
168620036: EVENT: Partikelsensor#pm10=6.00
168627324: EVENT: Rules#Timer=2
168627343: ACT  : GPIO,16,0
168627345: SW   : GPIO 16 Set to 0
As you can see, on the first gpio16,1 nothing happens. the second gpio16,1 it takes a long time to get values.




Btw & off-topic: running with static IP, no wifi drops. Maybe this helps on other place.

BertB
Normal user
Posts: 991
Joined: 25 Apr 2015, 14:39

Re: PMS7003 no readings

#7 Post by BertB » 12 Jan 2019, 14:56

What do you mean with a long time?
Somewhere in the documentation of the device, I read it takes about 30 secondes for the device to stabilise after a wake up.
https://www.google.com/url?sa=t&rct=j&q ... xBwvyOFMaB

MadNBG
Normal user
Posts: 3
Joined: 28 Oct 2018, 20:11

Re: PMS7003 no readings

#8 Post by MadNBG » 18 Jan 2019, 21:38

I read that too, but the lifetime-rule confused me. I thought, that rule is OK for that Sensor, but it is just an example.
I power on the Sensor for 15 sec now. Thats the minimum timing for my setup.
The Sensor values are OK. I compare them with an Airquality-sensor (AppliedSensor) which detects VOC (stinky organic Gases. Miefsensor)
You can see on both Sensors the smoke of a cigarette very well - and when it's time to close the window.

Post Reply

Who is online

Users browsing this forum: Google [Bot] and 3 guests