-
Notifications
You must be signed in to change notification settings - Fork 20
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
Telemetry Lockups #40
Comments
@jrleeman This is probably related to issue #23. Can you describe your setup? Are you connecting through XBee or USB? Currently, there is no handshaking, so the idea is to keep the packets small and coming in a steady enough stream that they don't overflow the buffer on the FTDI chip. Windows also has a bad habit of de-prioritizing the FTDI driver, which means data isn't getting pulled frequently enough to prevent buffer overrun. It helps to close any other programs that are running, and see if that makes a difference I'll mark this duplicate for now. Thanks for the input! |
The lockup happens though XBee only in my testing. This is running on a low-end surface with Windows 10. I'd be a bit more hesitant to mark this as a duplicate. There were no other programs open and I can't find a reliable time interval between lockups. Also as @JasonDorie pointed out I'm unsure that handshaking would do anything here. |
I don't have a Surface, or anything running Windows 10, so I have no means On Sat, Sep 17, 2016 at 7:27 PM, John Leeman [email protected]
|
Yes - still says connected. I was just able to reproduce this error on a MacBook Air running 10.11.6. Telemetry runs for ~15 seconds, then locks up. If I power the ELEV8 down, the ground station still says connected. XBees are still talking from the comm activity LEDs. |
@jrleeman Are you willing to do some testing of an improvement in the dev branch? |
Sure - I don't have the GCS build environment setup. Is it built using QT Creator? |
Yes, GroundStation is built with Mingw, Qt 5.5 (though newer should be J On Sunday, September 18, 2016, John Leeman [email protected] wrote:
|
Yes, it is On Sep 18, 2016 5:12 AM, "John Leeman" [email protected] wrote:
|
Can you all duplicate? |
I won't be able to until I get back tomorrow, I'll let you know what I find when I try it out. On Sep 18, 2016 7:03 PM, "John Leeman" [email protected] wrote:
|
@jrleeman It might take me a few days before I can set this up, but I'm going to clip on a serial monitor and watch all of the data going through - I'm starting to suspect that the xbee is going into command mode or getting "illegal" combinations of chars. I'll keep everyone posted on what I find. |
@MatzElectronics any luck on just reproducing the behavior? From the activity LEDs I think data is still being sent, but haven't verified with a serial dump. |
Not yet. I haven't been able to get this all set up yet as we have a On Sep 23, 2016 5:48 AM, "John Leeman" [email protected] wrote:
|
Any luck? I'm hoping to write this up for a Servo Magazine article, but want to make sure it is a working system first. |
@jrleeman
In the meantime, I'll work on putting together and testing an entire Flight Controller + Telemetry system to send to you tomorrow if we don't get anywhere from trying another computer and checking for interference. |
Did someone on this thread mention that it was repro'd on a non-windows On Wed, Oct 12, 2016 at 11:21 AM, Kyle M [email protected] wrote:
|
I did reproduce on a mac as well. I’m on the road again, but will take a screen video this weekend and check for interference. Jim was having this same problem though.
|
I have a Mini Mac, and will have a Macbook next week, so I can try to repro On Thu, Oct 13, 2016 at 1:04 PM, John Leeman [email protected]
|
Good news/Bad news. I borrowed Ken's xBee setup, and it's having the intermittent connectivity issue, so I should finally be able to start troubleshooting first thing tomorrow. But this indicates the issue is probably not related to your operating system or interference. |
I suppose that's good news! Looking forward to hearing what you find.
|
Ok, I've been able to re-create (and then fix) the issue by changing the CE Routing/Messaging mode setting of base-station xBee using XCTU. To see if that's what's causing your problem, try this fix:
|
@RoboTechie I'll give this a shot tonight/tomorrow morning and let you know. |
Ok - that does the trick it looks like. On my tablet (Windows 10) there would be very occasional and brief losses of telemetry, but that's possibly due to it's weak processor. Was maybe a few seconds every 5 minutes at most. MacBook Air had no issues at all. |
I've done some reading and experimenting with my own XBee pair here and
These two settings reduce the latency from FC to PC significantly. You can also bump the baud rate to 115,200 on both sides. This means On Fri, Oct 14, 2016 at 8:18 PM, John Leeman [email protected]
|
Interesting. I'm anxious to try this out over the weekend! On Oct 14, 2016 10:57 PM, "Jason Dorie" [email protected] wrote:
|
Publison here. Jim |
Good evening, Did you reinstall version 2.0.1 of the FC firmware back on your v3? The On Oct 16, 2016 8:19 PM, "John Leeman" [email protected] wrote:
|
Yes (visible in the screenshot, both are running 2.0.1)
|
Sorry! I can't see the screenshot from my phone. Jason may have to answer On Oct 16, 2016 8:43 PM, "John Leeman" [email protected] wrote:
|
Hmm - I haven't seen that before. I'll take a look tonight. I flip On Sunday, October 16, 2016, Matthew Matz [email protected] wrote:
|
No, I don’t. I may blast everything clean and try again if you can’t reproduce. |
Try bumping back to the other version, use GroundStation to save a prefs That might not work, but the prefs are written is such a way that they are On Sunday, October 16, 2016, John Leeman [email protected] wrote:
|
I had already deleted V3. Bad news is that the problem is replicated on my Mac which has never had anything but 2.0.1. I re-downloaded a clean set of firmware and set the XBees back to 57600. No luck. Should we close this issue since telemetry is indeed flowing, but open a new issue for the display? |
It'll be an issue with the format of the data coming from the Elev8, most When you re-flashed the firmware, you programmed to EEPROM, not just RAM, J On Tuesday, October 18, 2016, John Leeman [email protected] wrote:
|
Yes - EEPROM programmed. I noticed my radio settings carried over. Settings file attached. Sticks on screen and some telemetry are fine, others like battery are not working. |
I'll take a look after dinner and see if I can spot anything. Meanwhile, J On Tuesday, October 18, 2016, John Leeman [email protected] wrote:
|
More to the point, what you're suggesting shouldnt be possible with On Tuesday, October 18, 2016, John Leeman [email protected] wrote:
|
Okay - I reset all factory defaults and reflashed. Indicators are back working now. Sorry for all the back and forth. Hopefully the data format is settling down soon? w.r.t. trying future dev stuff. Is master working generally and all development in ActiveDev? |
Going forward, yes. Master should always be working and stable. ActiveDev J On Tuesday, October 18, 2016, John Leeman [email protected] wrote:
|
Happy to contribute to the write-up/tutorial if there's an easy way to. Is that content on GitHub somewhere or does it live on a Parallax server somewhere? |
Probably not - that would all exist within Parallax. Matt's baby. J On Tuesday, October 18, 2016, John Leeman [email protected] wrote:
|
Going to hold this open until I edit related docs, once there, I will close. |
Assigned to Matt as he's holding open until docs are updated. |
Did the parallax docs ever get updated on this? Servo released the article as a free and open to all article: http://www.servomagazine.com/index.php/magazine/article/January2017_MultiRotorHobbyist_Telemetry |
Hey John. Looks like it's still available:
https://forums.parallax.com/discussion/165345/esp8266-drone-atmosphere-sound
ing
…_____
From: John Leeman [mailto:[email protected]]
Sent: Wednesday, March 08, 2017 11:47 AM
To: parallaxinc/Flight-Controller
Cc: hurricanehover; Comment
Subject: Re: [parallaxinc/Flight-Controller] Telemetry Lockups (#40)
Did the parallax docs ever get updated on this? Servo released the article
as a free and open to all article:
http://www.servomagazine.com/index.php/magazine/article/January2017_MultiRot
orHobbyist_Telemetry
-
You are receiving this because you commented.
Reply to this email directly, view
<#40 (comment)
096437> it on GitHub, or mute
<https://github.com/notifications/unsubscribe-auth/AH_3BJ3RjQTXFEbYhus_GgvlM
Aey3zpGks5rjtuZgaJpZM4J_r6G> the thread.
<https://github.com/notifications/beacon/AH_3BAQK6MXXrikSfFBlKH2bWFZCUojCks5
rjtuZgaJpZM4J_r6G.gif>
|
Right - I mean the online "assembly guide/tutorial" from Parallax that needed some revision after the issues we found troubleshooting this. |
Good morning,
No, unfortunately I (and most of our team responsibile for documentation)
have been pressed to meet a deadline for the BlocklyProp project, and it
may still be a few weeks before I am able to circle back to some
documentations needs for the ELEV-8. This need, as well as a couple others
will be addressed, but we haven't been able to get there recently.
-M
*Matthew Matz | STEM/Robotics Educator*
Parallax Inc. | Direct: 916-625-3019 | www.parallax.com | @m
atzElectronics <http://twitter.com/MatzElectronics>
…On Wed, Mar 8, 2017 at 9:56 AM, John Leeman ***@***.***> wrote:
Right - I mean the online "assembly guide/tutorial" *from Parallax* that
needed some revision after the issues we found troubleshooting this.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#40 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AS0quAqcb_vIW7oTzvDTgYdTdej2sQ_1ks5rjuu_gaJpZM4J_r6G>
.
|
No worries - I was just going through cleaning up issues, etc I'm involved with :) @hurricanehover It was mostly the setup of the XBee radios that we changed I believe. |
Using the 2.0 firmware and 2.0 ground station on Windows 10 the telemetry will lock up every few minutes for up to a minute before restoring. This has been a problem in the last couple of releases.
The text was updated successfully, but these errors were encountered: