I have a problem with the PMS5003 (air particle sensor). I've been using it for several years. Since the driver of this sensor did not support the SET and RESET pins in the past, I wrote a rule and the measurement itself is run with TuskRun.
I updated FW, last time a year ago, using sources from March last year.
I use the same configuration and my own rule script to handle the sensor all the time.
The readout is made every 10 minutes.
When using sources from mega-20230306, the sensor is not read. In the logs I have information that the SET and RESET pins are supported, but as if TaskRun was not executed.
Below are screenshots of the sensor configuration.
What could be the cause of the sensor not working?
In addition, in the main menu of the sensors, the assignment of the TX and RX lines seems to me to be the opposite than in the detailed configuration. I don't know if I'm right.
However, with FW from a year ago it works fine.
PMS5003 and mega-20230306 problem
Moderators: grovkillen, Stuntteam, TD-er
-
- Normal user
- Posts: 531
- Joined: 07 Jun 2018, 06:47
- Location: Gdynia/Poland
Re: PMS5003 and mega-20230306 problem
The only relevant change to this plugin since last year March that I could find is an added check against a buffer overflow during receiving data. That doesn't seem really relevant to me, but I don't own such sensor, so I can't test this myself
In November 2021 some bigger changes were made to this plugin, but that is already part of the March 2022 release you have been using. The Serial configuration also hasn't changed since your previous build.
The screenshots you show have been made using the March 2022 release, I assume? As the PMS task is showing some values.
But why is your interval set to 65535 seconds? As that's 45 days and ~5 hours. Did you possibly restore the configuration from an older version of ESPEasy, that maybe used a different configuration layout? Also the IDX values of 64 seem a bit strange to me.
Maybe you could delete the task, and re-add it, to start with a clean slate/state.
In November 2021 some bigger changes were made to this plugin, but that is already part of the March 2022 release you have been using. The Serial configuration also hasn't changed since your previous build.
The screenshots you show have been made using the March 2022 release, I assume? As the PMS task is showing some values.
But why is your interval set to 65535 seconds? As that's 45 days and ~5 hours. Did you possibly restore the configuration from an older version of ESPEasy, that maybe used a different configuration layout? Also the IDX values of 64 seem a bit strange to me.
Maybe you could delete the task, and re-add it, to start with a clean slate/state.
/Ton (PayPal.me)
Re: PMS5003 and mega-20230306 problem
That interval value is really strange indeed.
Since I'm using this plugin for an active project of mine, I know for a fact that the plugin is working.
Even if the interval is set to completely unusable values, you should still see a number of log entries in the logs, when you give the command "TaskRun" with the nr (or name) of that task.
Logs like these:
Since I'm using this plugin for an active project of mine, I know for a fact that the plugin is working.
Even if the interval is set to completely unusable values, you should still see a number of log entries in the logs, when you give the command "TaskRun" with the nr (or name) of that task.
Logs like these:
Code: Select all
68401299: PMSx003: Oversampling using 25 samples
-
- Normal user
- Posts: 531
- Joined: 07 Jun 2018, 06:47
- Location: Gdynia/Poland
Re: PMS5003 and mega-20230306 problem
Yes, screenshots are from FW from March 2022.The screenshots you show have been made using the March 2022 release, I assume? As the PMS task is showing some values.
Yes, I use config and rule script which is at least 4-5 years old. The value 65535 seconds is used because at the time I create that config/script the only way to do not start task itself was to enter such value. The whole unit is soft rebooted daily at 3:05. So the readout of sensor will never start automatically.But why is your interval set to 65535 seconds? As that's 45 days and ~5 hours.
Its because I use TaskRun to initiate readouts.
Who is online
Users browsing this forum: No registered users and 53 guests