Randy Rhodes
Member
Im getting a " No CORS in range " error.
any suggestions?
any suggestions?
no cors in range
- Thread starter Randy Rhodes
- Start date
What is the date of the raw data file? Can you share it with us.
Randy Rhodes
Member
the date is yesterday march 14th, 2018.
Randy Rhodes
Member
the base file is too large according to this site
( 6 MB )
( 6 MB )
Randy Rhodes
Member
i don't know what i'm doing here, but its never stopped me before.
Sean Joyce
Well-Known Member
I wonder if this had anything to do with it?
http://www.dailymail.co.uk/sciencetech/article-5494489/Huge-solar-storm-set-slam-Earth-TOMORROW.html
nevermind,
http://www.dailymail.co.uk/sciencetech/article-5494489/Huge-solar-storm-set-slam-Earth-TOMORROW.html
nevermind,
Last edited:
Ron Cloninger
Member
I also got the "No CORS in Range" message today for work done yesterday. ???
@Alexey Razumovsky I see this too with a file that was able to be processed yesterday.
Adam Davis
Member
I'm getting a " No CORS in range " error today, 5/8/18, for work done 5/7/18. This happened approximately 2 months ago also. Is this something that should happen this often?
Sometimes switching to the Debug server will help. In DPOS, click on the gear button at the top of the screen, then Advanced, then Use DEBUG Server to Process Data.
Adam Davis
Member
Thanks Shawn, that did the trick! Now is it recommended to keep that option on or just use it when needed?
Greg Flowe
Active Member
Same issue today No CORS in range. Use the Debug Server and it worked. Never had this happen before.
Adam Davis
Member
I went to DPOS a job that i worked on yesterday and my LS has been stuck on "3. Applying Rover CORS-Processing..." for about twenty minutes. I tried it earlier this moring with the debug server with the same result. Also the LS has been slower and glitchier since the last update, I'm wondering if i can revert to an earlier version until the bugs are worked out?
You could update to the Prerelease version if you desire. It has many improvements and bug fixes. Just be sure to backup your data and projects before updating.
Adam Davis
Member
I clicked the Prerelease option and it says my device is already up to date. Also I have a warning that says last full back time N/A but I backed up my device this morning prior to posting on the forum.
Eugene Aksyonov
Well-Known Member
Hi Adam,
PreRelease has the same build that causes "up-to-date" message. Anyway this is not a solution.
Did you post a project to support? if not attach it to here public or private. We need to see a reason and it seems it is not DPOS but jField.
PreRelease has the same build that causes "up-to-date" message. Anyway this is not a solution.
Did you post a project to support? if not attach it to here public or private. We need to see a reason and it seems it is not DPOS but jField.
Adam Davis
Member
Hi Eugene, I just posted it to support, thank you for chiming in!
Sorry, I did not realize that J-Field 2.1.0.35 had been moved to the Release branch. This is the version I was suggesting you try.