CRTN Outage

[Jim Frame]

I was unable to connect to my local CRTN station (UCD1) this morning. After a brief attempt to troubleshoot the problem in the field, I switched to a local base and carried on. But tonight I looked at the CRTN status map and saw a ton of red dots (stations down). I tried one of the blue dot (supposedly up) mountpoints, but I was unable to get useful data using my receiver. I connected to it from my desktop using BNC and got a stream of some sort, but was unable to decipher it to tell if it was correct or not.

Anyone know what's going on with the network?

[SPMPLS]

Now the real-time CRTN map does not display at all. I will make some inquiries.

[falcon]

Just today at 12:19 pm I got an email with the following text:


"We have experienced an issue with the CRTN map server - it turns pink after initial display. We are working on it.
Also, we temporarily lost connectivity to some of our Northern California stations. Should be okay now.

--Yehuda"

[Jim Frame]

I'm still not able to get data from UCD1 or P268. My receiver shows "connected," but no corrections are being received.

I can make the pink wash on the status map go away by unchecking the READI Sites map layer, but all sites are then shown as red (down). I don't know if that's real or just a map display problem.

[SPMPLS]

The CRTN team at SOPAC is working on the issues. The map display issue has been corrected, except it shows almost all of the stations as a red symbol. One of the challenges is that one of the key members is in Argentina at a conference. It is interesting that you still aren't getting corrections from UCD1 because Dr. Bock said he fixed that issue yesterday after you first reported it.

I will follow-up.

[Jim Frame]

It is interesting that you still aren't getting corrections from UCD1 because Dr. Bock said he fixed that issue yesterday after you first reported it.

As you were, I figured it out. Somehow my receiver setup had unchecked RTCM 3.0 as the stream protocol, and that left it unable to decipher what the caster was sending. (I think!) In any case, I've got it working now, and I apologize to any CRTN folks who I may have caused some head-scratching.