ProLink has been replaced by 'Sokkia
Link' which is now superceded by SDXpress (Australasia
The information below is for existing
ProLink users, who may continue to use ProLink for its
extensive export customisation functionality.
Here are a few things to be aware of:
1. ProLink requires Administrator rights when using
projects. Each project is stored in a directory of its own.
2. (GPS RTK only) Prolink does not use a geoid
model, so be aware you may find height differences between
the results from the data-collector and the reduction from
Prolink. Reduce in the data-collector. If you've downloaded
an unreduced file for archiving purposes, you may send it
back to the controller to be reduced or to continue field
3. Change of target height
Sometimes a change of target height is skipped in the
reduction process, leading to incorrect heights for all
points till the next target height change.
4. Sin and Cos functions in customised exports don't work
5. (GPS RTK only). Reducing RTK data in Prolink:
Antenna height of second and subsequent base stations in the
same file are ignored - so if the second base station has a
different antenna height, you'll see incorrect elevations
for all points observed using that second base station. This
only seems to happen on certain Operating Systems.
6. When re-opening a project, the co-ordinate order
reverts to Northing, Easting, even if you set the
default to Easting, Northing.
Total Station to the PC
To transfer a file from a Sokkia Total Station you can use the 'receive'
function in ProLink. After you have 'received' the file on the PC, you can
'import' it into a ProLink project.
For most Sokkia Total Stations use the SDR33 (SDR) device. You'll need to set the PC ready to receive and
then 'send' the job from the Total Station.
If your Total Station or SDR data-logger is sending the job (records are counting)
but the PC is still displaying 'waiting to receive' check the following:
- are you connected to the correct com port? In case of doubt, try all
- are the communication parameters the same on the PC and in the
instrument? Check the speed (baud rate) but also the parity, data bits, stop
bits. Leave Xon/Xoff unchecked and handshake 'none' for now.
- is the com port available? Not occupied by Activesync, for instance.
Older models like the SET2Cii and other C series with built-in Sokkia data cards
will use the 'SCR2' device (set to 9600 baud regardless of RS232 speed in
instrument !) to communicate. Set File Type in the left hand screen to *.SCR. These instruments should be set 'On Line' in the
Menu/Card/Comms menu and will receive a *.scr (not SDR) file to the PC.
The same settings apply if you're using an external SCR2 card reader.
If you have (intermittent) communication problems between the SDR33 and the
Total Station, the cable attached to the SDR33 is likely to be faulty. Once you have a
new cable, make sure not to squash the cable by inserting the SDR33 head first
into the carry pouch.
' I'm importing
an ASCII file and ProLink crashes '
Have a look (with e.g. Notepad, not MSWord) at the data-file, to see whether the
import format you selected actually matches the contents of the ascii file:
- remove header record - ProLink will try to decode it as the first
- check for empty code fields
- check that the separator (comma, space or tab) before an empty (code)
field is present.
- replace the PtENZCd_FBK_Comma_Del_Imp.TDF file that came with Prolink
1.15 to this one:
'XFM not found' error message
You'll see this error message when the transformation file (*.xfm) which was
used on the SDR datalogger in a GPS RTK survey, is not present on the PC.
For Australia, typically the AUST0002.xfm
file is used and it should be in the \prolink\xfm folder.
Another possibility is that the Windows registry is telling Prolink to search
for your xfm in a different folder, a legacy from installs of an earlier version
of Prolink, or Sokkia Link.
'Not an XFM project ....
The first file you import into a new ProLink project determines the
coordinate system used in that project. So if the first file is recorded on e.g.
GDA94- zone 56, you'll get an error message if following files are recorded on
other zones or did not use an .xfm file.
Known or unknown Base coordinates - what's the go?
1. If you do not have known coordinates for the GPS base station, use
'unknown' setting. You can now enter completely arbitrary coordinates. But you
must visit a known point with the rover and perform a calibration on the
data-collector to get to your desired coordinate system.
2. If you do have known coordinates for your base, use 'known' setting -
and you don't need to do a calibration. But visit a known point as a check.
'Known' implies that the initial coordinate system will be using the entered
known northing and easting as starting point.
'Unknown' implies that the initial coordinate system will use the autonomous GPS
coordinates, converted to northing and easting. This should get your job within
a few meters.
Similarly to the xfm setting of the first file, it is the setting in the first file which determines whether 'known' or 'unknown' initial coordinates
are used in a ProLink project.
3. In case you entered known coordinates for your base station, but left the
Base Coord field 'unknown' by accident , and you did not do a calibration, you
will find all of your coordinates off by the same amount. To correct this
situation, change 'arbitrary' to 'known' in ProLink's field book view,
export the field book file as SDR file and import this new file into a NEW
project. Or import another file with 'known' setting first ...