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
Node.Js only everloop demo worked from the docu #8
Comments
It's very likely the format of the protobufs changed and invalidated the demos. Let us investigate. |
Same here except for
|
"Message received: UV error: 0, Invalid configuration for UV driver. Message received: UV error: 0, Invalid configuration for UV driver." You shouldn't see this. I'll take a look early tomorrow to see what can be causing this issue. |
@Mexxxo About ZigBee, we are testing with Bulbs but this is under-documented and you will need to run a program (and a new version of MALOS) to make this work. Do you have a ZigBee bulb? |
@arhuaco no I haven't tested ZigBee, currently I have also no device to test ZigBee with. |
Thanks for the suggestions. I just added the package.json file: I also removed the code that generates the following messages. We were sending invalid configurations to test the code that process them but this code is already working well. "Invalid configuration for UV driver. Message received: UV error: 0, Invalid configuration for UV driver" For humidity I get: { humidity: 74.72823333740234, temperature: 35.519264221191406 } Can you please tell us what version of MALOS you're running? You can try the next command to upgrade to the latest version: apt-get update && matrix-creator-malos Let us know... |
@arhuaco how to know the MALOS version ? The malos command line don't take argument right ? Ive tried : I have re-cloned the full
|
Have you followed the getting started page? https://github.com/matrix-io/matrix-creator-quickstart/wiki/2.-Getting-Started The second line of the following command should tell you the version that you have installed. apt-cache show matrix-creator-malos ATM the MALOS binary doesn't print the version but it should. Something to do later. ATM we're managing versions with Debian packages only. |
Yes Nelson already done the Getting Started page. After |
I have the same version. No full output needed. You should no longer see the "Invalid configuration for Humidity driver" as I removed this test and the commit is already in the master branch. We can try programming the MCU again. Please try this:
and then restart MALOS and run the following command again.
|
If that doesn't work, you can try the same as above but:
instead of:
|
Thanks @arhuaco your code just rock my Matrix. I ran all the test (except zigbee) and they work I followed your first lines :
|
Good to hear @nebiljabari . This is an issue we have. Opening matrix-io/matrix-creator-init#4 . Have fun! |
Hi @arhuaco, |
@Mexxxo what do mean by :
UPDATE - I just ran a serie of tests :
All the data seems realistic*, except :
from *but we have to keep in mind the Matrix design and the fact that the RaspberryPi (heat production for example) can biais some sensors record. I guess it's on the engineers todolist |
Hi @nebiljabari node test_humidity.js node test_pressure.js node test_uv.js node test_imu.js |
Please try:
to see if the problem persists. |
I have deleted the flag and restarted my RPi. I'm running node 6.9.0 |
I see that the protocol-buffers are on the commit 353527c. Should I use the latest master of the protocol buffers? |
The messages haven't changed but try using the latest commit from master. There is an open issue that might be affecting you: matrix-io/matrix-creator-init#10 , we do need to improve initialization. You can try programming the MCU a few times without restarting to see if this fixes the issue.
|
No success :( |
You can try installing everything again but I'm not sure it will work. I'll ask @eljuguetero to see if he has an idea of what to do. HAL is linked into MALOS so by trying MALOS you're also trying HAL. So far MALOS always works when HAL is working. Please also check that the board is properly connected to the Pi (push it...). Can you try upgrading MALOS? This is the closest we can be to a reinstall.
|
Thanks @arhuaco, Also like you said, the HAL is also returning the same zero values like the node tests. |
Hey @arhuaco, I did the following things: Thanks for your effort @arhuaco ! |
Perhaps it was a bad contact. I'm glad you can use the Creator now! 👍 FYI we're adding more documentation to MALOS... |
Update: node test_humidity.js node test_pressure.js |
With a little bit testing it looks like the values are only grabbed on a system start, but not updating. @arhuaco can you confirm this? |
I have never seen this one. I'll have to defer this issue to more people. AFAIK HAL grabs the values every time. ATM components in the board are affecting the temperature you're reading so the values you're seeing make sense. I asked here and all the values make sense. We're working on a software fix for the temperature issue and it should be released soon. |
So imu, pressure and humidity are not updating. A MALOS only restart did not changed these values. |
I updated today and all the .js test (except everloop) gave fixed values. I had to : @arhuaco I think you should put a note in the ReadMe file for others |
did an update && upgrade, rebooted pi and reprogrammed mcu. Finally the sensors are working :) With the temperature (on both sensors) showing wrong values, I could also move the creator more away from the raspi right? |
Hi,
today I tired to run all the NodeJs Demos.
I'm using Node 6.6.0, I have installed zmq and protobuffjs (btw. please add to the documentation that this must be installed, or even better at a package.json than you can simply do an npm install).
Also I needed to clone seperatly the protocol-bufers repo, here I didn't used the pointer from the malos repo, instead I took the latest master.
The everloop demo worked! :)
But the rest of the Demos:
uv, humidity, pressure and imu just returned 0 values.
Zigbee I haven't tested.
Node.Js Logs:
node test_uv.js
Sending pings every 5 secondsMessage received: UV error: 0, Invalid configuration for UV driver.
Message received: UV error: 0, Invalid configuration for UV driver.
{ uv_index: 0, oms_risk: 'Low' }
{ uv_index: 0, oms_risk: 'Low' }
{ uv_index: 0, oms_risk: 'Low' }
{ uv_index: 0, oms_risk: 'Low' }
{ uv_index: 0, oms_risk: 'Low' }
{ uv_index: 0, oms_risk: 'Low' }
node test_humidity.js
Sending pings every 5 secondsMessage received: Humidity error: 0, Invalid configuration for Humidity driver.
Message received: Humidity error: 0, Invalid configuration for Humidity driver.
{ humidity: 0, temperature: 0 }
{ humidity: 0, temperature: 0 }
{ humidity: 0, temperature: 0 }
{ humidity: 0, temperature: 0 }
{ humidity: 0, temperature: 0 }
node test_everloop.js
node test_pressure.js
Sending pings every 5 seconds{ pressure: 0, altitude: 0, temperature: 0 }
{ pressure: 0, altitude: 0, temperature: 0 }
{ pressure: 0, altitude: 0, temperature: 0 }
{ pressure: 0, altitude: 0, temperature: 0 }
{ pressure: 0, altitude: 0, temperature: 0 }
{ pressure: 0, altitude: 0, temperature: 0 }
node test_imu.js
Sending pings every 5 seconds{ yaw: 0, pitch: 0, roll: 0 }
{ yaw: 0, pitch: 0, roll: 0 }
{ yaw: 0, pitch: 0, roll: 0 }
{ yaw: 0, pitch: 0, roll: 0 }
{ yaw: 0, pitch: 0, roll: 0 }
Logs from MALOS:
MALOS starting
You can query specific driver info using port 20012.
Registered driver IMU with port 20013.
Registered driver Humidity with port 20017.
Registered driver Everloop with port 20021.
Registered driver Pressure with port 20025.
Registered driver UV with port 20029.
Invalid configuration for UV driver.
Invalid configuration for UV driver.
New delay between updates for UV is 1000 ms.
New timeout after last ping for UV 6000 ms.
Invalid configuration for Humidity driver.
Invalid configuration for Humidity driver.
New delay between updates for Humidity is 1000 ms.
New timeout after last ping for Humidity 6000 ms.
New delay between updates for Pressure is 1000 ms.
New timeout after last ping for Pressure 6000 ms.
New delay between updates for IMU is 1000 ms.
New timeout after last ping for IMU 6000 ms.
New delay between updates for IMU is 2000 ms.
New timeout after last ping for IMU 6000 ms.
The text was updated successfully, but these errors were encountered: