|
Post by SDL on Mar 5, 2018 20:44:43 GMT -8
It will be a couple of weeks. I'm meeting with the people this week and I expect it will take them a few weeks to move through the process.
BP
|
|
lee
New Member
Posts: 36
|
Post by lee on Mar 8, 2018 11:52:52 GMT -8
Glad you found the fix!!! So, do I just wait for my board to be returned, or a newer revision?
Thanks!
|
|
|
Post by SDL on Mar 9, 2018 8:22:57 GMT -8
Lee,
Did you have an RMA#?
We just got the first two boards from our rework and are testing them this morning.
Should have all the new boards reworked by next week. It's a pain and expensive, but we have to do it!
BP
|
|
|
Post by SDL on Mar 9, 2018 9:58:28 GMT -8
Folks, We have tested our reworked boards and they work! Will be detected by all known Raspberry Pi boards (until a new one comes out no doubt). It's not 100% clear exactly what the problem was with the Raspberry Pi Zero and Zero W according to John, but he suspects it was a timing tolerance issue on the Zero and W. The new ThunderBoards only work at address 0x02 and you can't change them. We should have boards to start shipping as of Monday or Tuesday. Please private message (not post!) me with your shipping address and we will start shipping the replacements next week. BTW, if you don't have a detection issue (like on the Raspberry Pi 3), don't bother with the exchange because it won't behave any differently (except that it now is locked to address 0x02). Sorry for the problems on this board, but at least we solved the problem. Our philosophy is to admit our mistakes (although it is not clear on which end, ours or the Raspberry Pi Zero end it is on) and fix them. As quickly as possible! Breathing much better now, BP
|
|
lee
New Member
Posts: 36
|
Post by lee on Mar 10, 2018 11:58:11 GMT -8
I sent you the RMA again, this time in a PM. Thanks!
|
|
mcinflyre
Junior Member
Posts: 53
Raspberry Pi: Yes
Other Device: PC, Mac and Android devices.
|
Post by mcinflyre on Mar 22, 2018 7:06:41 GMT -8
Hi,
I have not been able to get the updated Thunder Board to work on my GroveWeatherPi build. It probably comes down to not knowing where Channel 1 is on the I2C Mux board. It was mentioned in the 2018 Bug Week post to connect it to Channel 1 on the Mux. In all of the ports I have tried to connect it to, it appears to be conflicting with the DS3231. I'm doing the best I can to try and figure out this stuff on my own, but I'm getting anywhere.
**** Update: The Board is detect and everything works with the DS3231 removed. So I have a conflict with the Thunder Board and the DS3231. ****
I've tried J3, J1 on the Mux, direct connect to I2C ports on Pi2Grover. None work.
(Note: I don't have the rain or wind sensors attached at this time to this build)
When the Thunder Board to J3 on the Mux: pi@odyssey1:~/SDL_Pi_GroveWeatherPi $ sudo python GroveWeatherPi.py deviceID = 0x1050
GroveWeatherPi Solar Powered Weather Station Version 2.99 - SwitchDoc Labs
Program Started at:2018-03-22 09:51:00
---------------------- I2C Mux - TCA9545: Present BMP280: Present DS3231: Present HDC1080: Present HTU21DF: Not Present AM2315: Present ADS1015: Not Present ADS1115: Present AS3935: Present OLED: Present SunAirPlus: Not Present Sunlight Sensor: Not Present WXLink: Not Present
UseMySQL: Present Check WLAN: Present WeatherUnderground: Not Present ---------------------- ----------------- Scheduled Jobs ----------------- Jobstore default: sampleAndDisplay (trigger: interval[0:00:10], next run at: 2018-03-22 09:51:14 CDT) patTheDog (trigger: interval[0:00:10], next run at: 2018-03-22 09:51:14 CDT) blinkSunAirLED2X (trigger: interval[0:00:10], next run at: 2018-03-22 09:51:14 CDT) tick (trigger: interval[0:01:00], next run at: 2018-03-22 09:52:04 CDT) sampleWeather (trigger: interval[0:05:00], next run at: 2018-03-22 09:56:04 CDT) sampleSunAirPlus (trigger: interval[0:05:00], next run at: 2018-03-22 09:56:04 CDT) writeWeatherRecord (trigger: interval[0:05:00], next run at: 2018-03-22 09:56:04 CDT) writePowerRecord (trigger: interval[0:05:00], next run at: 2018-03-22 09:56:04 CDT) updateRain (trigger: interval[0:05:00], next run at: 2018-03-22 09:56:04 CDT) checkForShutdown (trigger: interval[0:05:00], next run at: 2018-03-22 09:56:04 CDT) sampleWeather (trigger: interval[0:15:00], next run at: 2018-03-22 10:06:04 CDT) sampleSunAirPlus (trigger: interval[0:15:00], next run at: 2018-03-22 10:06:04 CDT) doAllGraphs (trigger: interval[0:15:00], next run at: 2018-03-22 10:06:04 CDT) WLAN_check (trigger: interval[0:30:00], next run at: 2018-03-22 10:21:04 CDT) ----------------- ----------------- Local WeatherRack Weather Sensors Sampling ----------------- Rain Total= 0.00 in Rain Last 60 Minutes= 0.00 in Wind Speed= 0.00 MPH MPH wind_gust= 0.00 MPH ------Patting The Dog------- Wind Direction= 0.00 Degrees Wind Direction Voltage= 0.000 V ----------------- ----------------- DS3231 Real Time Clock ----------------- Raspberry Pi= 2018-03-22 09:51:14 No handlers could be found for logger "apscheduler.executors.default" month must be in 1..12 File "/usr/local/lib/python2.7/dist-packages/apscheduler/executors/base.py", line 125, in run_job retval = job.func(*job.args, **job.kwargs) File "GroveWeatherPi.py", line 1230, in sampleAndDisplay Scroll_SSD1306.addLineOLED(display,"%s" % ds3231.read_datetime()) File "./RTC_SDL_DS3231/SDL_DS3231.py", line 153, in read_datetime self._read_minutes(), self._read_seconds(), 0, tzinfo=tzinfo)
----------------- Local WeatherRack Weather Sensors Sampling ----------------- ------Patting The Dog------- Rain Total= 0.00 in Rain Last 60 Minutes= 0.00 in Wind Speed= 0.00 MPH MPH wind_gust= 0.00 MPH Wind Direction= 0.00 Degrees Wind Direction Voltage= 0.000 V
====================================================================================== pi@odyssey1:~/SDL_Pi_GroveWeatherPi/SDL_Pi_TCA9545 $ sudo python testSDL_Pi_TCA9545.py
Test SDL_Pi_TCA9545 Version 1.0 - SwitchDoc Labs
Sample uses 0x73 Program Started at:2018-03-22 10:01:31
-----------BUS 0------------------- tca9545 control register B3-B0 = 0x0 ignore Interrupts if INT3' - INT0' not connected tca9545 control register Interrupts = 0x0 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f 10: 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20: 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 30: 30 31 32 33 34 35 36 37 38 39 3a 3b 3c 3d 3e 3f 40: 40 41 42 43 44 45 46 47 48 49 4a 4b 4c 4d 4e 4f 50: 50 51 52 53 54 55 56 57 58 59 5a 5b 5c 5d 5e 5f 60: 60 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70: 70 71 72 73 74 75 76 77
-----------------------------------
-----------BUS 1------------------- tca9545 control register B3-B0 = 0x0 ignore Interrupts if INT3' - INT0' not connected tca9545 control register Interrupts = 0x0 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f 10: 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20: 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 30: 30 31 32 33 34 35 36 37 38 39 3a 3b 3c 3d 3e 3f 40: 40 41 42 43 44 45 46 47 48 49 4a 4b 4c 4d 4e 4f 50: 50 51 52 53 54 55 56 57 58 59 5a 5b 5c 5d 5e 5f 60: 60 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70: 70 71 72 73 74 75 76 77
-----------------------------------
-----------BUS 2------------------- tca9545 control register B3-B0 = 0x0 ignore Interrupts if INT3' - INT0' not connected tca9545 control register Interrupts = 0x0 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f 10: 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20: 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 30: 30 31 32 33 34 35 36 37 38 39 3a 3b 3c 3d 3e 3f 40: 40 41 42 43 44 45 46 47 48 49 4a 4b 4c 4d 4e 4f 50: 50 51 52 53 54 55 56 57 58 59 5a 5b 5c 5d 5e 5f 60: 60 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70: 70 71 72 73 74 75 76 77
-----------------------------------
-----------BUS 3------------------- tca9545 control register B3-B0 = 0x0 ignore Interrupts if INT3' - INT0' not connected tca9545 control register Interrupts = 0x0 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: 03 04 05 06 07 08 09 0a 0b 0c 0d 0e 0f 10: 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20: 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 30: 30 31 32 33 34 35 36 37 38 39 3a 3b 3c 3d 3e 3f 40: 40 41 42 43 44 45 46 47 48 49 4a 4b 4c 4d 4e 4f 50: 50 51 52 53 54 55 56 57 58 59 5a 5b 5c 5d 5e 5f 60: 60 61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70: 70 71 72 73 74 75 76 77
-----------------------------------
When I try to run GroveWeatherPi.py again: pi@odyssey1:~/SDL_Pi_GroveWeatherPi $ sudo python GroveWeatherPi.py deviceID = 0x0 sh: echo: I/O error visible= 0 Traceback (most recent call last): File "GroveWeatherPi.py", line 344, in <module> ds3231.read_datetime() File "./RTC_SDL_DS3231/SDL_DS3231.py", line 153, in read_datetime self._read_minutes(), self._read_seconds(), 0, tzinfo=tzinfo) ValueError: month must be in 1..12
==============================
I will remove the DS3231 board and see what happens.
|
|
|
Post by SDL on Mar 22, 2018 8:08:29 GMT -8
Something is seriously hanging the I2C bus. Everything is responding to everything. Take off one device at a time until you start to see mostly zeros in the testSDL_Pi_TCA9545.py output.
Nothing is working!
BP
|
|
mcinflyre
Junior Member
Posts: 53
Raspberry Pi: Yes
Other Device: PC, Mac and Android devices.
|
Post by mcinflyre on Mar 22, 2018 10:02:24 GMT -8
So far I've seen it work by removing the DS3231 and the separately, the BMP280.
I've tried a different DS3231 which didn't solve the problem. Didn't think it would, but gotta try to be sure.
I don't have a spare BMP280, so I will keep moving things around to see if I can isolate it.
Dumb question: Since this is running on a wired power, do I really need the DS3231? Can't the date and time come from the RPI?
I'll get something working one of these days, ha!
Thanks for your help,
Richard
|
|
mcinflyre
Junior Member
Posts: 53
Raspberry Pi: Yes
Other Device: PC, Mac and Android devices.
|
Post by mcinflyre on Mar 22, 2018 11:32:36 GMT -8
*** See next post for new info - keeping info below for documentation ***
I think it may be time for me to take up knitting instead...
Note: The Thunder Board is plugged into J3 on the Mux.
So when I run GroveWeatherPi.py with the DS3231 removed, it works with the Thunder Board detected. If I stop the script with cmd+c and try to start the script again, I get the DS3231 error (even though I don't have it installed):
pi@odyssey1:~/SDL_Pi_GroveWeatherPi $ sudo python GroveWeatherPi.py deviceID = 0x0 visible= 0 Traceback (most recent call last): File "GroveWeatherPi.py", line 344, in <module> ds3231.read_datetime() File "./RTC_SDL_DS3231/SDL_DS3231.py", line 153, in read_datetime self._read_minutes(), self._read_seconds(), 0, tzinfo=tzinfo) ValueError: month must be in 1..12
If I shut down, unplug and start up again, it will work same as above, only one time.
When I remove the BMP280 and the DS3231, I get the same results. When I remove the BMP280 and plug in the DS3231, I get the same results.
Things I've found with the DS3231 removed, DS3231 & BMP280 removed, and just the BMP280 removed:
1. When I run the test script, testSDL_Pi_TCA9545.py, BUS0 looks good, but then BUS1 through BUS3 are all filled with values. If I run GroveWeatherPi.py first (after shutdown, unplug), it runs, but only once and as noted below, not fully functional.
2. In the scenario where the script does run, the Thunder Board is detected and appears to be working. However, the white interrupt light is always on while the script is running. I've tried using the Lightning simulator to see if that would trigger a detection, but to no surprise, it does not detect an interrupt and nothing changes.
3. I'm out of ideas. Headed to the Yard Barn to get some designs for a sweater, perhaps and water bottle holder... (No offense to anyone that does enjoy knitting).
I guess the next test will be to swap out the RPI. After that, I will swap out the Pi2Grover. If those changes produce the same results, then I truly will be out of ideas.
Sorry for all the problems.
Thanks for your time.
Richard
|
|
mcinflyre
Junior Member
Posts: 53
Raspberry Pi: Yes
Other Device: PC, Mac and Android devices.
|
Post by mcinflyre on Mar 22, 2018 12:52:08 GMT -8
I received 2 of the updated Thunder Boards a week or so ago. In the post above, I detail a lot of issues where the Thunder Board did not work.
I swapped out the Thunder Board with the 2nd of the new Thunder Boards and I'm having different issues than with the 1st updated Thunder Board.
I tried it first plugged into J3 on the Mux, it was not detected. I then moved it to the Pi2Grover I2C port, top port, next to GPIO pins. The Thunder Board is detected, however it does not respond to the Lightning simulator and eventually the script stops running with an error related to the AS3935:
pi@odyssey1:~/SDL_Pi_GroveWeatherPi $ sudo python GroveWeatherPi.py
GroveWeatherPi Solar Powered Weather Station Version 2.99 - SwitchDoc Labs
Program Started at:2018-03-22 15:37:21
---------------------- I2C Mux - TCA9545: Present BMP280: Present DS3231: Present HDC1080: Not Present HTU21DF: Not Present AM2315: Present ADS1015: Not Present ADS1115: Present AS3935: Present OLED: Present SunAirPlus: Not Present Sunlight Sensor: Not Present WXLink: Not Present
UseMySQL: Present Check WLAN: Present WeatherUnderground: Not Present ---------------------- as3935 Interrupt ----------------- Scheduled Jobs ----------------- Jobstore default: sampleAndDisplay (trigger: interval[0:00:10], next run at: 2018-03-22 15:37:34 CDT) patTheDog (trigger: interval[0:00:10], next run at: 2018-03-22 15:37:34 CDT) blinkSunAirLED2X (trigger: interval[0:00:10], next run at: 2018-03-22 15:37:34 CDT) tick (trigger: interval[0:01:00], next run at: 2018-03-22 15:38:24 CDT) sampleWeather (trigger: interval[0:05:00], next run at: 2018-03-22 15:42:24 CDT) sampleSunAirPlus (trigger: interval[0:05:00], next run at: 2018-03-22 15:42:24 CDT) writeWeatherRecord (trigger: interval[0:05:00], next run at: 2018-03-22 15:42:24 CDT) writePowerRecord (trigger: interval[0:05:00], next run at: 2018-03-22 15:42:24 CDT) updateRain (trigger: interval[0:05:00], next run at: 2018-03-22 15:42:24 CDT) checkForShutdown (trigger: interval[0:05:00], next run at: 2018-03-22 15:42:24 CDT) sampleWeather (trigger: interval[0:15:00], next run at: 2018-03-22 15:52:24 CDT) sampleSunAirPlus (trigger: interval[0:15:00], next run at: 2018-03-22 15:52:24 CDT) doAllGraphs (trigger: interval[0:15:00], next run at: 2018-03-22 15:52:24 CDT) WLAN_check (trigger: interval[0:30:00], next run at: 2018-03-22 16:07:24 CDT) ----------------- processing Interrupt from as3935 Last Interrupt = 0x1: Noise Floor too low. Adjusting ----------------- Local WeatherRack Weather Sensors Sampling ----------------- Rain Total= 0.00 in Rain Last 60 Minutes= 0.00 in Wind Speed= 0.00 MPH MPH wind_gust= 0.00 MPH ------Patting The Dog------- Wind Direction= 0.00 Degrees Wind Direction Voltage= 5.000 V ----------------- ----------------- DS3231 Real Time Clock ----------------- Raspberry Pi= 2018-03-22 15:37:35 DS3231= 2018-03-22 15:37:34 DS3231 Temperature= 153.00 C ----------------- ----------------- BMP280 Barometer ----------------- Temperature = 26.83 C Pressure = 101.87 KPa Altitude = -45.44 m Sealevel Pressure = 102.53 KPa ----------------- ----------------- Sunlight Vi/IR/UV Sensor Not Present ----------------- ----------------- HDC1080 Temp/Hum Not Present ----------------- ----------------- HTU21DF Temp/Hum Not Present ----------------- ----------------- ----------------- AS3935 Lightning Detector ----------------- Last result from AS3935: Noise Floor: Noise Floor too low. Adjusting Lightning Count = 0 ----------------- ----------------- AM2315 Temperature/Humidity Sensor ----------------- outsideTemperature: 25.0 C outsideHumidity: 44.5 % crc: 0 ----------------- -----------------
=-=-=-=- Cut output to get to error -=-=-=-=-=
----------------- Local WeatherRack Weather Sensors Sampling ----------------- Rain Total= 0.00 in Rain Last 60 Minutes= 0.00 in Wind Speed= 0.00 MPH MPH wind_gust= 0.00 MPH ------Patting The Dog------- Wind Direction= 0.00 Degrees Wind Direction Voltage= 4.946 V ----------------- ----------------- DS3231 Real Time Clock ----------------- Raspberry Pi= 2018-03-22 15:39:25 DS3231= 2018-03-22 15:39:24 DS3231 Temperature= 153.00 C ----------------- ----------------- BMP280 Barometer ----------------- Temperature = 26.90 C Pressure = 101.87 KPa Altitude = -45.28 m Sealevel Pressure = 102.54 KPa ----------------- ----------------- Sunlight Vi/IR/UV Sensor Not Present ----------------- ----------------- HDC1080 Temp/Hum Not Present ----------------- ----------------- HTU21DF Temp/Hum Not Present ----------------- ----------------- ----------------- AS3935 Lightning Detector ----------------- Last result from AS3935: ----No Lightning detected--- Lightning Count = 0 ----------------- ----------------- AM2315 Temperature/Humidity Sensor ----------------- outsideTemperature: 25.0 C outsideHumidity: 44.5 % crc: 0 ----------------- ----------------- Local WeatherRack Weather Sensors Sampling ----------------- Rain Total= 0.00 in ------Patting The Dog------- Rain Last 60 Minutes= 0.00 in Wind Speed= 0.00 MPH MPH wind_gust= 0.00 MPH Wind Direction= 0.00 Degrees Wind Direction Voltage= 4.966 V ----------------- ----------------- DS3231 Real Time Clock ----------------- Raspberry Pi= 2018-03-22 15:39:34 DS3231= 2018-03-22 15:39:34 DS3231 Temperature= 153.00 C ----------------- ----------------- BMP280 Barometer ----------------- Temperature = 26.88 C Pressure = 101.87 KPa Altitude = -45.19 m Sealevel Pressure = 102.53 KPa ----------------- ----------------- Sunlight Vi/IR/UV Sensor Not Present ----------------- ----------------- HDC1080 Temp/Hum Not Present ----------------- ----------------- HTU21DF Temp/Hum Not Present ----------------- ----------------- ----------------- AS3935 Lightning Detector ----------------- Last result from AS3935: ----No Lightning detected--- Lightning Count = 0 ----------------- ----------------- AM2315 Temperature/Humidity Sensor ----------------- outsideTemperature: 0.0 C outsideHumidity: 0.0 % crc: -1 ----------------- as3935 Interrupt processing Interrupt from as3935 exception - as3935 I2C did not work Traceback (most recent call last): File "GroveWeatherPi.py", line 1853, in <module> tca9545.write_control_register(TCA9545_CONFIG_BUS0) File "./SDL_Pi_TCA9545/SDL_Pi_TCA9545.py", line 74, in write_control_register self._write(TCA9545_REG_CONFIG, config) File "./SDL_Pi_TCA9545/SDL_Pi_TCA9545.py", line 52, in _write self._bus.write_byte_data(self._addr, register, data) IOError: [Errno 121] Remote I/O error
So, I now think the 1st new Thunder Board is simply bad. The 2nd one is closer to working, but still no luck.
This is with the DS3231 and BMP280 connected (related to post above) and the HDC1080 removed.
I have no idea what else to do...
Thanks,
Richard
|
|
mcinflyre
Junior Member
Posts: 53
Raspberry Pi: Yes
Other Device: PC, Mac and Android devices.
|
Post by mcinflyre on Mar 22, 2018 13:25:37 GMT -8
Edit - Script failed after about 15 minutes of running with the same error msg related to TCA9594: ...... cut output to show error AS3935 Lightning Detector ----------------- Last result from AS3935: ----No Lightning detected--- Lightning Count = 7 ----------------- ----------------- AM2315 Temperature/Humidity Sensor ----------------- outsideTemperature: 0.0 C outsideHumidity: 0.0 % crc: -1 ----------------- as3935 Interrupt processing Interrupt from as3935 exception - as3935 I2C did not work Traceback (most recent call last): File "GroveWeatherPi.py", line 1853, in <module> tca9545.write_control_register(TCA9545_CONFIG_BUS0) File "./SDL_Pi_TCA9545/SDL_Pi_TCA9545.py", line 74, in write_control_register self._write(TCA9545_REG_CONFIG, config) File "./SDL_Pi_TCA9545/SDL_Pi_TCA9545.py", line 52, in _write self._bus.write_byte_data(self._addr, register, data) IOError: [Errno 121] Remote I/O error I have the 2nd updated Thunder Board connected to the I2C port, top port under GPIO pins. The bottom I2C port on the Pi2Grover is connected to the Mux (J1). No other I2C plugs in the Pi2Grover. I've included a picture of what is working for a little while: I don't have the HDC1080 sensor connected, I want to keep the Pi2Grover I2C ports as open as possible. So it works for a little while. I will hang the 1st updated Thunder Board on the wall of frustration as that appears to simply be a bad board. Thanks, Richard
|
|
|
Post by SDL on Mar 23, 2018 7:45:28 GMT -8
Richard,
This is frustrating to us too. Our system works fine. We will be happy to replace #1 though. PM your shipping address and we will send you one that is tested specifically by me.
Any board using the AS3935 is sensitive to bus I2C loading. You must plug the AS3935 into the Mux Board Bus 1 by itself (JP3). This is important.
Even your picture above has more than one thing on the I2C bus where the Thunderboard is plugged in. You have the Mux board attached too.
BP
|
|
mcinflyre
Junior Member
Posts: 53
Raspberry Pi: Yes
Other Device: PC, Mac and Android devices.
|
Post by mcinflyre on Mar 23, 2018 11:09:03 GMT -8
I followed the wiring instructions for the GroveWeatherPi. That's why I have the other I2C ports connected to the other I2C sensors or boards. J1 is connected to the Pi2Grover I2C bottom port. J2 to the I2C hub per the directions. The I2C hub has the oled, Grove digital to anolog converter board and sun / uv sensor.
If I can't connect anything else to the mix, how can I connect other sensors?
Where do I connect the Mux?
|
|
|
Post by SDL on Mar 23, 2018 15:14:57 GMT -8
Richard,
That does not look like the picture you sent.
Richard, please annotate your picture so I know what exactly is where. It still looks to me that the thunderboard is not plugged into J3 and you have two of the Pi2Grover I2C slots full.
BP
|
|
mcinflyre
Junior Member
Posts: 53
Raspberry Pi: Yes
Other Device: PC, Mac and Android devices.
|
Post by mcinflyre on Mar 23, 2018 15:47:05 GMT -8
You are right, I do currently have the Thunder Board plugged into the Pi2Grovee, top port on the right. When I connect it to J3 on the Mux, the Thunder Board is not recognized. The only way I could get it to be recognized and sort of work was connecting it the way I have it.
I’m at the point now where it’s not making much sense to keep banging my head against the wall with the GroveWeatherPi. I have an OurWeather Plus board giving me the data that it will provide and I have another RPI running the Thunder Board and I’m getting that data. I was hoping to get those in one system, but I don’t know that that it’s worth the time, given that the GroveWeatherPi does not have the REST capability.
So, for now I have what I need from the two systems.
Thanks,
Richard
|
|