AI Assistant
Notifications
Clear all

R8 Model 2 "waiting for L2 SVs"

7 Posts
4 Users
0 Reactions
300 Views
alexfalli11
(@alexfalli11)
Posts: 47
Member
Topic starter
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

I got a R8. I'm trying to use with a cors network that I use with 2 Epoch 50s and 2 other model 2s. In survey controller, at the bottom I keep seeing "waiting for L2 SVs". Is there something I'm missing?

The format I'm using is cmr+, which works for my other model 2s.

Help!!


 
Posted : June 16, 2014 8:46 am
astrodanco
(@astrodanco)
Posts: 149
Member
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

> I got a R8. I'm trying to use with a cors network....The format I'm using is cmr+, which works for my other model 2s.

If you're trying to use a CORS as the base, then what format is the CORS base sending? Locally I have Survey Controller configured to connect to the base via NTRIP caster and RTCM 3.0 mount point.


 
Posted : June 16, 2014 4:54 pm
alexfalli11
(@alexfalli11)
Posts: 47
Member
Topic starter
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

My base network uses CMR+, CMRx, and RTCM3. I alway use CMR+ for my Trimble antennas. I use the same setup where i have a ntrip user and password with an ip and port number.


 
Posted : June 16, 2014 4:58 pm
paul-in-pa
(@paul-in-pa)
Posts: 6034
Member
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

Is It Waiting For All L2 SVs, Or Just Some?

Many of the CORS are now set up to output up to 11 observables. That means in some cases the L2 observable may be accompanied by a legacy P2 observable while the newer satellites will output L2C or 2C.

What exactly are your R8s looking for?

Paul in PA


 
Posted : June 16, 2014 5:18 pm
lee-d
(@lee-d)
Posts: 2382
Member
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

Have you done a hard boot on the receiver and collector? Is the Model 2 in question running the same firmware version as your other Model 2s that work correctly? If you run it as a rover off a local base do you have the same problem? Is the data collector running the same firmware as your other units that work properly?

If the answers to all of the above are Yes then put it in the shop.


 
Posted : June 17, 2014 6:14 am

alexfalli11
(@alexfalli11)
Posts: 47
Member
Topic starter
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

I have one data collector th a that I use when testing if they work. The model 2 with the issue has a different firmware. I'm not sure how to give the antenna a haRd boot. I'm sorry I don't have much details right now because I'm bit in the office right now. And I don't really try to right these things during the week. I had asked the person that I bought it from for help with it but he said it didn't have issues with him. He's agreed ton allow me to return it. I may likely be considering that option.:-S

I'm not sure how I can see what format it's actually picking up. I just use a mount point on the base cors network that broadcasts in cmr+ and within a minute I usually get a fix and am good to go.


 
Posted : June 17, 2014 8:40 am
lee-d
(@lee-d)
Posts: 2382
Member
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
 

As far as how to hard boot the receiver you simply hold down the power key. 15 seconds after all the lights go out the Satellite light should come on; that is a soft boot. After another 15 seconds the Satellite light goes back off; that is a hard boot. Just make sure you get any static files off before performing as the internal memory gets reformatted.

Just like anything, those receivers need to be rebooted on occasion to reset the software.

Regarding the firmware on the receiver, Trimble is on v. 4.84 if I remember correctly. Because of all the changes with the constellations, etc., I try to keep all of ours as up to date as possible. You may want to check just how old it really is and also what the latest version is that the warranty date will allow you to load.


 
Posted : June 17, 2014 10:24 am