Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Figure out if the pressure sensor can be linked to the SCD30 via hardware or software only #7

Open
ezio-melotti opened this issue Jan 25, 2022 · 1 comment
Labels
question Further information is requested

Comments

@ezio-melotti
Copy link
Collaborator

ezio-melotti commented Jan 25, 2022

The accuracy of the SCD30 can be increased by specifying a pressure value and the BNE668 is able to measure the pressure and provide this value.

We need to determine if the value can be provided directly to the SCD30 by physically connecting the two sensors or if it can only be set via software. If only the latter works, then we will need a way for the two sensor drivers to talk.

Perhaps the server can implement and event like msg-for that accepts the name of another client and an event, and redirects the message so that SCD30 could do sio.emit('msg-for', 'BNE668', 'get-pressure') and get back the pressure value from the BNE668 driver (see #11).

@ezio-melotti ezio-melotti added the question Further information is requested label Jan 25, 2022
@GregRRoss
Copy link
Contributor

GregRRoss commented Jun 29, 2022

I don't believe there is any way to do it via hardware.

I believe the best way to do it would be to retrieve recent pressure data from the database once it is implemented.

Some thoughts:

  1. A pressure sensor may or may not be attached.
  2. The pressure sensor could be one that is different from the BME688
  3. There could be multiple pressures in the database so the correct location for the pressure must be determined.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants