I just tried processing a kinematic session. Approximately 184 points, 2 base stations to a single rover.

Computer is AMD K6-2 533mhz, 128 meg ram, approx. 200meg free on c drive and more available on d or e drives (if I can set the usage of the program's location for temporary data storage)AND Win ME, Locus Processor version 1.1.

It seems to process the data between the two base stations and the rovers "static" initizialization point. It then processes one base station with all the rovers points, but when it starts the second base station with the rover it stops and gives an ECL error has occured causing an error in KERNEL32.DLL.

THE SUGGESTED REPAIR OF RE-STARTING (COLD OR WARM) DOESN'T WORK.

Any ideas ???!!!!!!???????

Jimbo Webb

Bill Martin and I discovered this in Maine once: if you're doing two bases and one rover, the bases have to be more than 100m away from each other, or the processor may choose the wrong base to use the fixed initialization bar with.

The .dll error may require a sw reload, I would wait for Tech Support to open up tomorrow, 800 229 2400

Mike,

Thanks for the hint. The 2 bases are probably less than the 100m or real close. The site(dirt pit) isn't all that large.

Didn't use the init bar but just located a new static point to start the rover from. No problems with the three points.

Jim

Jim,

I do not think the problem that Mike alluded to pertains to you here since you did not use the initialization bar.

Were all your receivers set at the same recording interval? To quickly check this, look in the Files tab of the Workbook in Locus Processor. If, for example, you set one base and the rover at 2 seconds but left the other base at 20 seconds and collected only 10 seconds of data at each point, there will be times when there is no common data between the second base and the rover. This may cause the processing engine (ECL) some heartburn. Let me know if this is the case. We will change the software to output a more intelligent message alerting the user of this problem.

If the recording intervals are the same, then I am not sure what is happening. You could try processing the data in two projects (base1 - rover, base2 - rover). If this is successful, you could then export ofiles from one project and input them into the other to adjust. If this works or does not work, I would like to look at the data. There would appear to be something wrong with the software. Could you email the data to me?

Bill Martin
Ashtech Precision Products

Bill,

I think(think - dangerous for me to do) they are the same interval but I'll have to check at the office in the AM. I had thought of trying the two project method but just haven't had a chance - other project deadlines.

Let me try this but either way I will email data but it might not be til the weekend...leaving for out-a-town project Tues. evening.

I haven't ever had this problem before but I haven't run any big files (more than 20 or so points) since I switched to WIN Me.

Jimbo Webb