# AVRGUI not displaying telemetry **URL:** \ **Category:** AVR Drone Software\ **Created:** [September 27, 2023, 1:49am UTC](https://forum.theavr.org/t/avrgui-not-displaying-telemetry/601 "2023-09-27T01:49:54Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Jonah](https://avatars.discourse-cdn.com/v4/letter/j/7feea3/32.png) [@Jonah](https://forum.theavr.org/u/Jonah)\ **Post date:** [September 27, 2023, 1:49am UTC](https://forum.theavr.org/t/avrgui-not-displaying-telemetry/601/1 "2023-09-27T01:49:54Z")
![messages](https://canada1.discourse-cdn.com/flex007/uploads/avr/original/1X/272ce2dffbfb65d4f84ca4e4fe5e453518a134c5.png) ![modules](https://canada1.discourse-cdn.com/flex007/uploads/avr/original/1X/9ff5ef76849fe7bfbdc581f36cdec013947eaac3.png) [https://pastebin.com/Ntx67JbL](https://pastebin.com/Ntx67JbL) - FCM error code I’ve been having a weird issue recently where my AVRGUI isn’t displaying any of its telemetry data, despite said data clearly existing as shown in the message debugger. I’ve triple checked all the wiring, and the FCM is absolutely connected (as shown by the message debugger) and I ran setup.py and start.py right before this test. I don’t know what’s causing the FCM error code in the pastebin above. ---
**Author:** ![nathan](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.theavr.org/nathan/32/4_2.png) [@nathan](https://forum.theavr.org/u/nathan)\ **Post date:** [September 27, 2023, 9:49pm UTC](https://forum.theavr.org/t/avrgui-not-displaying-telemetry/601/2 "2023-09-27T21:49:34Z")
The pastebin link you sent definitely shows the flight control module being unable to connect to the MQTT server. It looks like it was not running, as the connection was refused. As for the GUI, was there any output to the console? You’re using the GUI from the AVR-2022 repo, correct? ---
**Author:** ![Jonah](https://avatars.discourse-cdn.com/v4/letter/j/7feea3/32.png) [@Jonah](https://forum.theavr.org/u/Jonah)\ **Post date:** [September 28, 2023, 8:49pm UTC](https://forum.theavr.org/t/avrgui-not-displaying-telemetry/601/3 "2023-09-28T20:49:00Z")
I am indeed using the GUI from the 2022 repo. Is there a new build for 2023? I don’t know why the FCM can’t connect to the server, and I’ve reset basically everything to the Bell AVR standard software. I pulled from the github repo recently, ran setup.py, and even tried swapping out the jetson. I’d appreciate any insight you have on what could be causing the connection issue, and whether it’s a hardware or a software thing. ---
**Author:** ![nathan](https://yyz1.discourse-cdn.com/flex007/user_avatar/forum.theavr.org/nathan/32/4_2.png) [@nathan](https://forum.theavr.org/u/nathan)\ **Post date:** [October 3, 2023, 1:06am UTC](https://forum.theavr.org/t/avrgui-not-displaying-telemetry/601/4 "2023-10-03T01:06:08Z")
You should be using the 2022 one, 2023 is not backwards compatible. What happens if you just run the `mavp2p`, `mqtt` and `fcm` modules? Also re-run the setup.py script so that the latest version of the containers are pulled. @droneblocks any idea? I’m not sure on this one. ---
**Author:** ![Jonah](https://avatars.discourse-cdn.com/v4/letter/j/7feea3/32.png) [@Jonah](https://forum.theavr.org/u/Jonah)\ **Post date:** [October 13, 2023, 7:26pm UTC](https://forum.theavr.org/t/avrgui-not-displaying-telemetry/601/5 "2023-10-13T19:26:21Z")
Ok. Update. I re-ran setup.py, no errors. I did **./start.py run mavp2p mqtt fcm** Same error as last time, gathering future exception. I tried checking the dockers while start.py is running, and this is what showed: > CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES > 3bf4784931ac [Package avr/2022/fcm · GitHub](http://ghcr.io/bellflight/avr/2022/fcm:latest) “/bin/bash -l -c ./e…” 33 seconds ago Up 32 seconds avr-2022\_fcm\_1 > 3222848a1b03 [Package avr/2022/mavp2p · GitHub](http://ghcr.io/bellflight/avr/2022/mavp2p:latest) “/app/mavp2p serial:…” 34 seconds ago Up 32 seconds 0.0.0.0:5760-\>5760/tcp, :::5760-\>5760/tcp avr-2022\_mavp2p\_1 > d2a8454c07ee [Package avr/2022/mqtt · GitHub](http://ghcr.io/bellflight/avr/2022/mqtt:latest) “/docker-entrypoint.…” 34 seconds ago Up 32 seconds 1883/tcp, 0.0.0.0:18830-\>18830/tcp, :::18830-\>18830/tcp avr-2022\_mqtt\_1 So the mqtt server seems to be running, I’m just not sure why the fcm can’t access it ---
**Author:** ![Jonah](https://avatars.discourse-cdn.com/v4/letter/j/7feea3/32.png) [@Jonah](https://forum.theavr.org/u/Jonah)\ **Post date:** [October 17, 2023, 12:38pm UTC](https://forum.theavr.org/t/avrgui-not-displaying-telemetry/601/6 "2023-10-17T12:38:50Z")
Update again. I’ve tried basically every combination of scripts to launch the fcm module. Is it possible that there’s a hardware issue with connecting to the flight controller? We’ve checked most of the wires with a multimeter already, but I don’t really have another explanation at this point. ---
**Author:** ![Jonah](https://avatars.discourse-cdn.com/v4/letter/j/7feea3/32.png) [@Jonah](https://forum.theavr.org/u/Jonah)\ **Post date:** [October 17, 2023, 7:05pm UTC](https://forum.theavr.org/t/avrgui-not-displaying-telemetry/601/7 "2023-10-17T19:05:36Z")
Update #3. I tried reflashing the pixhawk, and ran setup.py again for good measure. Still getting the same error. Without the flight control module, I can’t enter position hold flight mode. Is there a way to completely scrub everything off of the jetson so that it perfectly mirrors the github? I’m worried there’s some error that isn’t getting overwritten when I do setup. I also may just be losing it after being at this error for three weeks. ---
**Author:** ![HPT1-Row\_Dyer](https://avatars.discourse-cdn.com/v4/letter/h/ce7236/32.png) [@HPT1-Row\_Dyer](https://forum.theavr.org/u/HPT1-Row_Dyer)\ **Post date:** [October 18, 2023, 2:44pm UTC](https://forum.theavr.org/t/avrgui-not-displaying-telemetry/601/8 "2023-10-18T14:44:11Z")
If you have the time and no other obvious solutions, try re-flashing the Jetson. It has helped fix issues in the past for me ---
**Author:** ![Jonah](https://avatars.discourse-cdn.com/v4/letter/j/7feea3/32.png) [@Jonah](https://forum.theavr.org/u/Jonah)\ **Post date:** [October 18, 2023, 2:44pm UTC](https://forum.theavr.org/t/avrgui-not-displaying-telemetry/601/9 "2023-10-18T14:44:46Z")
Will do! Thanks! Post must be at least 20 characters