Starnet JobXML converter (trimble access)

> Is anyone using this successfully and could maybe help me out what I am doing wrong?

I don't have an answer, but I have a question. Do you have the option of exporting the data in some other format that Star*Net will also convert? SDR? RAW?

I think that you can still download v7. You might try it and see if the converter in that version gives you the same problem. I recently discovered a problem with a file converter in v8 that had worked fine in v7.

I can attest that the file converter for Trimble Survey Controller worked just fine in v6. Unfortunately I no longer have access to it. I do not think that any of the settings in the converter are what is giving you your present troubles.

Everybody who uses StarNet should be using a data converter. Without that the experience would be an unhappy one.

Trimble has a little utility called "Ascii File Generator" which can be used to convert .job and .jxl files to other formats. Among the available style sheets is a Starnet converter. I have run your file through it and have what appears to be valid data.

#
## This file has been exported from Trimble Survey Controller!

## Job File:        150108                        
## Created:         2015-01-08                    
## Instrument:      S6 2 DR Plus                  
## Serial Number:   93010230                      
#
##

C   2             -13.587       -1.750   20.718 * * *
C   1             100.000       -1.750   20.000 * * *

##
.DELTA OFF
A       2-1-318           355-53-11
A       2-1-420           353-45-41
A       2-1-320           355-24-12
A       2-1-220           357-24-58
A       2-1-120           359-01-31
A       2-1-421           353-21-25
A       2-1-321           355-06-21
A       2-1-221           357-14-31
A       2-1-121           358-56-43
A       2-1-422           352-56-51
A       2-1-322           354-47-31
A       2-1-222           357-02-34
A       2-1-122           358-51-01
A       2-1-423           352-27-53
A       2-1-323           354-25-58
A       2-1-223           356-48-42
A       2-1-123           358-44-14
A       2-1-424           351-50-13
A       2-1-324           353-57-45
A       2-1-124           358-36-29
A       2-1-224           356-31-51
A       2-1-425           351-13-26
A       2-1-325           353-28-52
A       2-1-225           356-14-25
DV      2-1                                             1.646/1.643
DV      2-318                       59.920 91-37-09 1.646/0.000
DV      2-420                       54.191 91-48-02 1.646/0.000
DV      2-320                       53.950 91-44-51 1.646/0.000
DV      2-220                       53.781 91-47-10 1.646/0.000
DV      2-120                       53.733 91-43-15 1.646/0.000
DV      2-421                       51.068 91-52-06 1.646/0.000
DV      2-321                       50.884 91-49-11 1.646/0.000
DV      2-221                       50.784 91-51-32 1.646/0.000
DV      2-121                       50.749 91-47-37 1.646/0.000
DV      2-422                       48.289 91-56-59 1.646/0.000

....and so on for many pages. It makes me think that the problem is with the StarNet converter and not with your data.

Thanks very much, both of you, for your help.

I have already (successfully) used the StarTSC converter to convert from Trimble DC format.
Also the Trimble stylesheet used above (I used it on the logger directly).

I am not 100% happy with the output though as it uses DV and M records (StarTSC) and DV and A records (Trimble stylesheet).

The problem with these records (for me) is - for example - I had a situation the other day where I had to take my monitoring readings first, and backsight last. I was waiting for fog to lift, it saved standing for 1 hour as the monitoring stations were much closer to the instrument I could see them. I would normally take backsight before AND after but in this situation I was prepared to take the risk and check the data thoroughly and redo if necessary if the orientation drifted.

As the M and A readings describe horizontal angle from the backsight, the backsight cannot be changed. (without recalcing all the angles). The DM records would be ideal for my purpose.

I forgot to link to a DAT file converted from a different JXL where it put a few DM records in but I can't work out what was different about these points!

JXL file - http://tinyurl.com/mtph45w
DAT file - http://tinyurl.com/mcamrpg

Also both of the above methods averages my f1/f2 readings before they get into the DAT file. I want to see these ideally, for example to remove an unbalanced reading (2 f1 and 1 f2). I don't like going into the DC file to delete these, which is what I've had to do.

These methods also average multiple sets eg merging backsight readings and backsight checks at end. Even though I have unticked the box (in StarTSC) to do this.

Basically I want something where I can see every reading and chop and change, the raw data. I like the text based format DAT file for this. The LSA facility is also great when I need it. As you can see in the files on that day there is no redundancy (or any need for it).

So it seems no-one is using the StarJXL converter? I will have to enquire with Microsurvey. I am not sure what their support is like for trial customers?

Thanks again, Roger

> Everybody who uses StarNet should be using a data converter. Without that the experience would be an unhappy one.
>
Understatement.
:good: