Greg Stumpf
EF5
A 30 minute delay happened to me on 6/7/07. Hitting the reset button solved the problem.
-
While Stormtrack has discontinued its hosting of SpotterNetwork support on the forums, keep in mind that support for SpotterNetwork issues is available by emailing [email protected].
Dan Robinson
We suffered from the 30-minute delay for about 80% of the day on 6/7. We had to chase based on the lightning data alone, which along with warnings, was the only data that stayed current. Even the rotation markers were delayed. If these storms had not been good lightning producers, we'd have been flying blind all day. Reboots didn't fix it.
I'll have to try the reset button again next time it happens. It would be great if that fixes it every time.
I'll have to try the reset button again next time it happens. It would be great if that fixes it every time.
Bill Tabor
EF5
I hope all you folks keep this thread alive. This is pretty important / significant news and issue related to the use of Threatnet that so many of us use and rely on at times. Surely someone has mentioned this to Baron? If not someone definitely needs to. I know the Baron rep is on this list when they announce updates to the product. We need to get them on here to address this issue. If there is a strong chance of regular 20 to 30 minute delayed radar then Threatnet becomes a dangerous tool for use at night. Obviously David Drummond's encounter is an example of where accurate data can be crucial at night for decision making. While in the past at times I rely exclusively (for convenience) on Threatnet - this makes me think I need to start connecting via cell again and stop using the product. I've learned you really need to compare the Threatnet Base Reflectivity Blobs with more detailed radar / velocity anyway.
Dan Robinson
I experienced more 30-minute delays last week. It happens nearly every time I chase now. Hitting the reset button did not fix the issue, nor did rebooting. As with all the previous incidents, the lightning was the only data that was current. Tracks, shear SCITs and radar were all 30 minutes behind. Yes, storm tracks were 30 minutes old- they matched up with the 30-minute old radar. The only data that could be used to locate storms was the lightning. After about two hours, the problem corrected itself, then reappeared again later.
This HAS to be a Baron/XM issue and not a local machine issue. When the delay happens, when I first turn the laptop on, the very first radar/SCIT update is 30 minutes old. That means the data that I just received from the satellite is 30 minutes old. There is no way my computer could miraculously have data from 30 minutes ago when I was not connected to the radio!
This IS a critical problem that seriously handicaps chasing and introduces safety issues. I forwarded this thread to Baron in case they were not already aware of the issue.
This HAS to be a Baron/XM issue and not a local machine issue. When the delay happens, when I first turn the laptop on, the very first radar/SCIT update is 30 minutes old. That means the data that I just received from the satellite is 30 minutes old. There is no way my computer could miraculously have data from 30 minutes ago when I was not connected to the radio!
This IS a critical problem that seriously handicaps chasing and introduces safety issues. I forwarded this thread to Baron in case they were not already aware of the issue.
fplowman
Jason briefly touched on something I thought was interesting and felt I would share. Here is what I have discovered.
Placing my antenna on the dash works ok unless Im heading north. If you monitor the XM link GUI you may watch as the antenna goes from weak, marginal and good.
Ok so if the antenna doesnt have at least a "good lock" you will not recieve the radar portion of the packets of data downloaded as is my experience.
I solved this by placing the antenna in an unobstructed view on top of my roof outside of the vehicle.
Now my question of course would be. Where are those with these problems placing your antennas? And could the scenario I have suggested be the issue of why the radar on your unit sometimes doesnt download timely?
I guess the issue is if the antenna isnt in sight of the sattellite (S, SW) it will not get a "good" lock, which is a requisite of the larger radar file.
Placing my antenna on the dash works ok unless Im heading north. If you monitor the XM link GUI you may watch as the antenna goes from weak, marginal and good.
Ok so if the antenna doesnt have at least a "good lock" you will not recieve the radar portion of the packets of data downloaded as is my experience.
I solved this by placing the antenna in an unobstructed view on top of my roof outside of the vehicle.
Now my question of course would be. Where are those with these problems placing your antennas? And could the scenario I have suggested be the issue of why the radar on your unit sometimes doesnt download timely?
I guess the issue is if the antenna isnt in sight of the sattellite (S, SW) it will not get a "good" lock, which is a requisite of the larger radar file.
Last edited by a moderator:
Dan Robinson
My antenna is on top of the roof of my car, and I rarely have a weak signal. In my case the delay problem isn't dependent on signal strength. I've had a strong signal all day and still had 30-minute old data.
fplowman
Wow! Ok so It has to be a Baron issue. Or maybe this sattellite issue that others spoke about.
If you ever get an answer i hope you let us all know.
If you ever get an answer i hope you let us all know.
Eric Whitehill
EF1
Bill:
I have discussed this issue with Baron several times - what I have been told is to call in when we notice this issue with delayed radar. I called last month when I was having a problem with it being delayed, and when the WXWorx people checked their systems they did not notice a delay. They did communicate to me, however, that if the individual site is slow, then that one site would be slow in ouputting to XM.
My recommendation would be to have us call when we notice the delay - even an hour or so after the fact would help them to diagnose the issue.
-Eric
Gene Moore
EF3
I had a delay problem that put us in 80+ MPH winds during the June 6th event. We were in northern Nebraska on the cell at the head of the line. Here is the link to my page with the image, scroll to the bottom of the page:
http://chaseday.com/2007season.htm
The Threatnet information showed the storm moving NE at 81 MPH and the couplet at 149 MPH. One thing Barron's seems to do very well are the storm motions, provided the updates are on time. NWS radar confirmed very fast motions at the time. You can see where our vehicle was and the roaring high winds were right on our tail. When it hit I could not stand up. Fortunately I was behind the vehicle and got some shelter. I was almost ripped away from my grip on the door handle....and did lose some minor camera equipment. I never feared for my life, but I did fear for my camera
. This night a derecho was predicted by SPC, but generally did not come to pass except for our storm. Although I would not call this life threatning, it could have been much worse if there had been stuff to blow over. When we're out there looking through the viewfinder it's easy to lose track of things, especially at night. It's a shame Barron's is not a stand alone system, but it must be backed up when we get in close. It appears the issues with late updates are getting worse than when Bill Tabor and I started using it ....what....about four years ago.
Gene Moore
shameless plug....I do have 2007 updates on my site, more to come http://chaseday.com
http://chaseday.com/2007season.htm
The Threatnet information showed the storm moving NE at 81 MPH and the couplet at 149 MPH. One thing Barron's seems to do very well are the storm motions, provided the updates are on time. NWS radar confirmed very fast motions at the time. You can see where our vehicle was and the roaring high winds were right on our tail. When it hit I could not stand up. Fortunately I was behind the vehicle and got some shelter. I was almost ripped away from my grip on the door handle....and did lose some minor camera equipment. I never feared for my life, but I did fear for my camera
. This night a derecho was predicted by SPC, but generally did not come to pass except for our storm. Although I would not call this life threatning, it could have been much worse if there had been stuff to blow over. When we're out there looking through the viewfinder it's easy to lose track of things, especially at night. It's a shame Barron's is not a stand alone system, but it must be backed up when we get in close. It appears the issues with late updates are getting worse than when Bill Tabor and I started using it ....what....about four years ago.Gene Moore
shameless plug....I do have 2007 updates on my site, more to come http://chaseday.com
rdale
EF5
Didn't you visually see there was a storm approaching?
Gene Moore
EF3
Sure we saw it coming, at 3 bolts per second, hard to miss
. Problem is air is clear, especially at night and this strong cold outflow had moved out ahead of the storm. At the time we got hit there was absolutely no identifying features with the outflow surge...other than we heard a nice roar a minute or so earlier. As we were getting turned around I saw a thin sliver of an arc cloud form not far off the ground. That later developed into a beautiful arcus cloud. So the localized downburst that initiated this surge was just occuring. We know in the beginning down bursts come "down and out" so there was little visual warning. Also, I was cutting it thin not expecting to get hit with that much wind. But, figuring a nominal 10 minute lag with a storm moving 81 MPH and a gust front moving (faster) out ahead of that, it comes pretty fast.....an extra time lag didin't help. Actually I thought it was rather fun getting blasted that hard. The only thing that annoyed me was I never got set up to capture that vicious lightning until much of it was intracloud and in the rain. We were coming south out of South Dakota and it was all we could do to get out ahead of that forming line anyway.....gave it our best shot. Gene Moore
Dan Robinson
Just an update to mention that during the past two weeks I have not experienced the WxWorx delay at all, so it's possible the problem is fixed now. I've had the system running for several storm events in West Virginia, Virginia and North Carolina without any issues.
