Survey Pro 5.2 with Trimble S8

> We have been running Survey Pro 5.2 with Trimble S6 Total Stations with no problems. We have just introduced 2 Trimble S8's, but have encountered problems. It seems that whenever we Autolock to a prism (we tried different prisms) the sighting laser turns on and the Total Station cannot read an accurate distance or get a good backsight lock. The laser setting is definitely turned off in Survey Pro. As I said, it does not do this with the S6, only the S8?! Has anyone encountered this problem, or have any suggestions for a fix??

I run an S8 with Trimble Access and there is no problem. I think many on this forum have said in the past that the S series instruments run seamlessly with Access, However you are giving up the functionality of Survey Pro.
BTW It's the first time I've heard of anybody using that combination.

Ralph

Have you contacted Spectra Precision, I am interested in how good their support is now that they are not the old stand alone tds. Jp

[email protected]
720-587-4700

Im running Survey Pro 5.2 and dealt with Jerry yesterday to help me with an issue getting aerial imagery in my controller for background basemaps. He was a real help resolving the problem I was having.

Waiting to see if they can help with some other issues I'm having with Survey Pro & TBC not playing well together.

What sort of issues are you having with Survey Pro and TBC ?

I am trying the Demo Survey Pro in my Trimble TSC3.My TSC3 also has Trimble Access fully operational,which I like,with a Trimble S6.

Our crews have used TDS for years,and some do not like Trimble Access.

We also have switched from TDS Foresight to TBC,also which I like.

I have tried to load a TBC Corridor ( ext .rxl ) to Survey Pro but unable to,as Survey Pro has an ext. .rd5

Has anyone had any success with this?

Thank you,

John

I'm sitting on fourteen years worth of surveys using the old TDS Foresight and Survey Pro. If I open one of the old .job files in Spectra's Survey Pro 5.2 and convert to a .survey, expand it with GPS/conventional work and then try and import the .survey into TBC, TBC flatlines and floods my project directory with a seperate conversion file for each and every old point. Only seems to work as designed with virgin .survey files.

If I convert the resulting .survey back into .job/.raw format and try and open the .raw data in Foresight to view and print, Foresight crashes.

I sent them example files to reproduce the problem along with my work flow and they are looking into it.