|
Post by jridao2 on May 28, 2019 11:57:24 GMT -8
Hello; I am assembling a "OurWeather" kit on behalf of the APRS radio group in our local search and rescue and have some problems with the kit (order 2673 if you're from Switchdoc Labs); when powered up with the humidity sensor installed, the unit never gets pass the "Alexa Disabled" screen. When powered up without the humidity sensor installed, the unit passes boot, connects to my wifi router ok, and gives a ip statement 10.0.0.6 and starts polling the sensors including the non existing ones like lighting, humidity and its outdoor temperature and finally will burst or transmit a package. Its seems to do this routine without fail. Hot connecting the humidity sensor into the 6 hub port (wasn't sent a 4 hub) and now updated humidity and temperature data is being displayed but only 2 loops and the OLED screen blanks out (doesn't not come back on) but status led indicates polling and transmission taking place. So I can't turn on the setup with the humidity sensor installed and I can't see the display after the sensor is installed while running the board. Power is via the kit's included usb ac dongle and cable. RTC is attached, breakout card not connected. Bios or software is ver 035. Any clues to further this along would be appreciated. Thanks, A.Lee, Calesar380. I'm also having this similar issue of being unable to progress past the "Alexa Disabled" screen if the temperature/humidity sensor is connected. But once it's been removed and the system resets, I'm able to get readings for board temperature, wind speed, etc. to display on the OLED (I should preface that I've had the OurWeather kit for only about 2 hours now). I had a question regarding the consistency of color wiring. Referencing the image below of the I2C hub, the middle connector is from the sensor in question while the rear an forward connectors are from the OLED and main board respectively.
You'll notice that from left to right, the middle connector/sensor's wires are white, yellow, red, and then black while the other two have the white and yellow reversed. Since red and black are power and ground respectively, I was wondering if it's possible the I2C leads for the sensor were switched thus causing errors? If wire color doesn't matter and I can assume the sensor is wired up properly, any other suggestions on how to resolve this issue? I'll keep on browsing the forum but I wanted to get my wiring question out first.
Thanks!
|
|
|
Post by SDL on May 28, 2019 15:23:56 GMT -8
The wire color on the AM2315 is correct. The colors for SCL and SDA are opposite to those on standard grove cables.
Your locking is caused by something else.
Calesar and Jridao2, there is something special about you two guys. Calesar, if I remember right we replaced your AM2315, right?
BP
|
|
|
Post by jridao2 on May 29, 2019 7:28:01 GMT -8
Is there any known fix on my end/other things I can explore or do I need to jump to getting the AM2315 replaced?
Thanks!
|
|
|
Post by SDL on May 29, 2019 15:52:45 GMT -8
Jrado2,
We can replace the AM2315. Send the old one in and we will send a new one. Include your shipping address in the package.
SwitchDoc Labs RMA#052919-01 909 S Shelley Lake Lane Spokane Valley, WA 99037
BP
|
|
|
Post by henningjensen on May 31, 2019 12:59:15 GMT -8
Hi, I purchased the OurWeather complete kit this winter. I have the same issue as jridao2 and some of the other users here. It just won't get passed the "Alexa disabled" message during booting, whenever the AM2315 temperature sensor is connected.
I've been reading these forums for solution, but couldn't find any. Are the sensors being replaced for now?
|
|
|
Post by SDL on Jun 2, 2019 6:55:54 GMT -8
henningjensen, Yes, we can replace the sensor. We really need a bad one back so we can figure this out. Works on our system!
Here is your RMA: SwitchDoc Labs RMA #060219-01 909 S Shelley Lake Lane Spokane Valley, WA 99037
BP
|
|
|
Post by henningjensen on Jun 2, 2019 12:12:55 GMT -8
SDL: Thanks. Stupid question perhaps, but do you only want the sensor or the board as well?
|
|
|
Post by SDL on Jun 2, 2019 13:45:04 GMT -8
Only the sensor. The AM2315.
John
|
|
|
Post by ralphcs on Jun 9, 2019 6:51:12 GMT -8
Hi SDL,
New user on this board. FYI, software developer for enough decades to be happily retired but I can’t let go of learning. I’ve read through all the posts on the problem. A question came to mind, is there still in correlation with the REST calls? Depending on what software is backing the REST calls, I have seen a similar problem. But I don’t want to lead anyone down the proverbial rabbit hole. If the REST calls have been ruled out, then please ignore my post.
|
|
|
Post by SDL on Jun 10, 2019 7:17:46 GMT -8
Ralph,
I believe these are two different problems. REST calls will hang the weather station on a very rare basis. This is a ESP8266 interval OS problem I am certain. A conflict with the WiFi. A long term fix is in design for this.
Great suggestion though. The recent AM2315 problems "may" be a test escape from the manufacturers. We are still gathering data (and a few units). One we got back from RobotSquirrel was dead. We are checking this out!
BP
|
|
|
Post by ralphcs on Jun 10, 2019 15:09:29 GMT -8
So the ESP8266 OS handles the REST calls. Assuming this device uses its version of FreeRTOS, then it can use a semaphore table to handle threading. There is a corner case that can occur when the table is exhausted. It can cause the system to stop responding to any calls.
|
|
|
Post by SDL on Jun 11, 2019 7:43:14 GMT -8
Ralphics,
The underlying OS on the ESP8266 is not FreeRTOS but some espressif custom software (however, the ESP32 contains FreeRTOS and we use it!). There is a REST library that we use, but of course, it hooks into the Wifi stack for the OS.
It appears to be a timing problem rather than a table exhaustion, but we don't have enough data to form a real conclusion.
BP
|
|
|
Post by henningjensen on Jul 31, 2019 12:51:00 GMT -8
Hi SDL, Did you receive my AM2315 sensor? Altmost two months since I sent it to you.
|
|
|
Post by SDL on Aug 2, 2019 14:08:52 GMT -8
henningjensen,
Do you have the RMA #? I'll go find it. Did we cross ship a new one to you?
BP
|
|
|
Post by henningjensen on Oct 3, 2019 11:56:18 GMT -8
SDL,
Here is the RMA #060219-01
|
|