MPU-6050 has red LED but giving me Data but not BM0/BMP280

[GMW1988]

The first concern is the MPU-6050 has a red LED and not a green LED.
When I test CubeSatSim - FSK with the BMO/BMP 280 I am only giving 0s. It does not say Fail. It only gives me a bunch of 0s.
My solder work may be an issue.

[GMW1988]

Also, Raspberry Pi 0 was plugged in backwards and I powered it accidently and it got hot and short circuited but I turned it off quickly but I saw little smoke. I tested things and they were working prior to adding the sensors.

[GMW1988]

As in the past tests. The Pico flashes a green LED every second and the Raspberry Pi has the green LED flashing.

[alanbjohnston]

Hi Gregory,

Some MPU6050 Gyros have a red power LED instead of a green one. If the red LED is illuminated, it means the sensor has power. What values do you get for the MPU6050? Can you copy and paste the output of this command on the Pi Zero:

cd
CubeSatSim/config -p

This is the sensor data as received by the Pi Zero.

If your Pi Zero got hot and let out some smoke, you probably need to replace it.

If the BME280 is giving all zeros, that means the Pico isn't detecting it. The soldering looks OK on the BME280, except maybe for this pin:

But if the MPU6050 is also showing mostly zeros (it never shows all zeros), that might mean a problem with your Pico or with 4.7k resistors R23 and R24. Make sure the resistors have the right color bands and touch up these four solder joints:

You can try opening this Pico code in the Arduino IDE and Compiling and Uploading to the Pico: https://github.com/alanbjohnston/CubeSatSim/blob/master/stempayload/i2c_scanner/i2c_scanner.ino

The Serial Monitor will tell you if the BME and MPU sensors are found. The blue MPU6050 should be at address 0x68 while the purple BME280 should be at address 0x76.

Alan

[GMW1988]

The Pico when powered was flashing green every second.

[alanbjohnston]

That’s good. It means the Pico is programmed and powered.

Alan

[GMW1988]

I have another Pi Zero so I can replace it.
From my understanding if the Pi Zero is plugged into the board I will need to use SSH to get the output information using:
cd
CubeSatSim/config -p
I work on getting SSH working. I was able to get the WiFI found. I know on the Mac the terminal screen. I not exactly sure on how to find the IP Address or getting it to work.
Gregory

[GMW1988]

I was able to get this information loaded but still having an issue with FSK data.

[alanbjohnston]

This is good. Your BME data looks very good and your MPU data is non-zero. You don't need to worry about doing the SSH access as it would just show this same BME and MPU data. In FSK or BPSK, you should see these same data.

[GMW1988]

Hi Alan,That sounds good.What about the issue that when check on the FSK and click on Health and only see 0s.I  am not sure why I not getting information posted through that method.Gregory Sent from my iPhoneOn Jul 5, 2025, at 3:25 AM, Alan Johnston ***@***.***> wrote: This is good. Your BME data looks very good and your MPU data is non-zero. You don't need to worry about doing the SSH access as it would just show this same BME and MPU data. In FSK or BPSK, you should see these same data. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[GMW1988]

FSK a click on health.Sent from my iPhoneOn Jul 5, 2025, at 5:36 AM, Gregory Wetzel ***@***.***> wrote:Hi Alan,That sounds good.What about the issue that when check on the FSK and click on Health and only see 0s.I  am not sure why I not getting information posted through that method.Gregory Sent from my iPhoneOn Jul 5, 2025, at 3:25 AM, Alan Johnston ***@***.***> wrote: This is good. Your BME data looks very good and your MPU data is non-zero. You don't need to worry about doing the SSH access as it would just show this same BME and MPU data. In FSK or BPSK, you should see these same data. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[alanbjohnston]

I don’t know why you would see different data in APRS and FSK modes. You should delete the data in FoxTelem then check again - you may be viewing old data. In the Input tab click Stop to stop decoding then go under the File menu and select Delete Payload Data then click OK. Now the data in the Health tab will be the latest.

You can also try to shutdown using the pushbutton, then insert the RBF plug, then remove it to power up again. This resets the Pico.

if neither of those work, you will need to SSH into the Pi Zero (you have switched out the one that got cooked, right?) and look at logs. You don’t need to know the IP address, you can use the hostname of cubesatsim.local to login.

Alan

[GMW1988]

Hi Alan, I switched out the Pi Zero but this one may have an issue also. I forgot the password so I opted to reflash the software. With the Groundstation I cleared both BPSK mode and FSK mode. The BPSK worked with reloading info but the FSK did not work and still is showing 0s. I was able to get ssh to work. ***@***.****:*~ $* cd ***@***.****:*~ $* CubeSatSim/config -p CubeSatSim v2.1 configuration tool Real-time output from the serial port from the Pico: _START_FLAG_OK BME280 27.74 1016.69 -28.58 42.37 MPU6050 -8.63 2.93 -3.86 -0.38 -0.02 0.89 GPS 0.0000 0.0000 0.00 TMP 22.50_END_FLAG_ _START_FLAG_OK BME280 27.75 1016.69 -28.60 42.33 MPU6050 -8.90 2.61 -3.66 -0.38 -0.02 0.89 GPS 0.0000 0.0000 0.00 TMP 22.50_END_FLAG_ ***@***.****:*~ $* The other thing that is confusing to me is that I see numbers that look good. Also with the Web Radio on the Ground Station I was able to get all the information. I could redownload the GroundStation software. The reason I am wondering about the Pi Zero is due to an error I made. Yesterday I hooked the Pi Zero to a little monitor with the cords while it was hooked up to the CubeSatsim. I made an error and the screen showed info for a little time but shut off. At that point I was concerned I cooked the Pi Zero and shut it off. I can order another Pi Zero to see if that would perform better but hopefully I did not damage something. I also checked my resistors and the color codes looked good to me. I find this information confusing that I am seeing. Possibly, I am testing it wrong. It still has been a big learning experience and I am very thankful for the opportunity to learn. Gregory

…

On Sat, Jul 5, 2025 at 5:56 AM Alan Johnston ***@***.***> wrote: I don’t know why you would see different data in APRS and FSK modes. You should delete the data in FoxTelem then check again - you may be viewing old data. In the Input tab click Stop to stop decoding then go under the File menu and select Delete Payload Data then click OK. Now the data in the Health tab will be the latest. You can also try to shutdown using the pushbutton, then insert the RBF plug, then remove it to power up again. This resets the Pico. if neither of those work, you will need to SSH into the Pi Zero (you have switched out the one that got cooked, right?) and look at logs. You don’t need to know the IP address, you can use the hostname of cubesatsim.local to login. Alan — Reply to this email directly, view it on GitHub <#376 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BTYYTOCGV2KTFFVXSNNUSWL3G7DOFAVCNFSM6AAAAACA2OQ53WVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGNRWHEYTAMQ> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

[GMW1988]

Sent from my iPhoneOn Jul 5, 2025, at 7:51 PM, Gregory Wetzel ***@***.***> wrote:Hi Alan,I switched out the Pi Zero but this one may have an issue also.  I forgot the password so I opted to reflash the software.  With the Groundstation I cleared both BPSK mode and FSK mode.  The BPSK worked with reloading info but the FSK did not work and still is showing 0s.  I was able to get ssh to ***@***.***:~ $ cd ***@***.***:~ $ CubeSatSim/config -p CubeSatSim v2.1 configuration tool Real-time output from the serial port from the Pico: _START_FLAG_OK BME280 27.74 1016.69 -28.58 42.37 MPU6050 -8.63 2.93 -3.86 -0.38 -0.02 0.89 GPS 0.0000 0.0000 0.00 TMP 22.50_END_FLAG_ _START_FLAG_OK BME280 27.75 1016.69 -28.60 42.33 MPU6050 -8.90 2.61 -3.66 -0.38 -0.02 0.89 GPS 0.0000 0.0000 0.00 TMP 22.50_END_FLAG_ ***@***.***:~ $  The other thing that is confusing to me is that I see numbers that look good.  Also with the Web Radio on the Ground Station I was able to get all the information.  I could redownload the GroundStation software.The reason I am wondering about the Pi Zero is due to an error I made.  Yesterday I hooked the Pi Zero to a little monitor with the cords while it was hooked up to the CubeSatsim.  I made an error and the screen showed info for a little time but shut off.  At that point I was concerned I cooked the Pi Zero and shut it off.  I can order another Pi Zero to see if that would perform better but hopefully I did not damage something.  I also checked my resistors and the color codes looked good to me.   I find this information confusing that I am seeing.  Possibly, I am testing it wrong.  It still has been a big learning experience and I am very thankful for the opportunity to learn.GregoryOn Sat, Jul 5, 2025 at 5:56 AM Alan Johnston ***@***.***> wrote: I don’t know why you would see different data in APRS and FSK modes. You should delete the data in FoxTelem then check again - you may be viewing old data. In the Input tab click Stop to stop decoding then go under the File menu and select Delete Payload Data then click OK. Now the data in the Health tab will be the latest. You can also try to shutdown using the pushbutton, then insert the RBF plug, then remove it to power up again. This resets the Pico. if neither of those work, you will need to SSH into the Pi Zero (you have switched out the one that got cooked, right?) and look at logs. You don’t need to know the IP address, you can use the hostname of cubesatsim.local to login. Alan —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[alanbjohnston]

The CubeSatSim/config -p command shows that your BME and MPU sensors are working. The gyro on your MPU needs calibration. You can do this by plugging a micro USB cable into the Pico and running the Arduino IDE and opening the Serial Monitor. If you have the right Port selected, you will see the sensor data displayed every second. In the box at the top of the Serial Monitor window, type the letter C then click the Send button. Make sure the Pico does not move for 15 seconds while the gyro is calibrated. Now the first three numbers after MPU6050 will be close to zero unless the board is rotating.

Since your BME and MPU sensors are fully working g, I will close this topic. If you think FSK is not working, you should open a new topic and describe what you think isn’t working along with screenshots of FoxTelem showing the Input and Health tab information.

Alan