If it's VB-based that'll work fine. :up:

Lemme know when you think you have something...

I've sent you the source codes on your work email, so check if it didn't end up in the spam. :arrgh!:

Hasn't made it yet... but I'll keep an eye out for it.
Sometimes our system is a tad slow with outside email.

Hey, what would you like to call your tool?

"DRT TMA""
"Pos/Brg TMA"
"Least Square TMA"
"Dr.Sid's Magic Medicine"

...or do you have some other preference?

This isn't by chance an implementation of "Ekelund Ranging" is it?

I preffer Least square TMA. While Dr.Sid's magic medicine is not bad at all it does not have that hi-tek sound. :rotfl:

How much was left for 1.1? 2.0 sounds pretty juicy so if you'd rather jump on that then go for it.

Yeah... but if I have two units taking bearings at the same times I don't need the tool. The crossing LOBs indicate the location, etc. I guess it's good that the logic properly falls on the LOB intersections, but I could've used my Mk1 eyeball to figure that out.

I wanted to see a solution with non-uniform LOB points of origin (ie. variable LOB time intervals). I guess I can test it myself when it arrives...

BTW, I'm not seeing it at work. The system may have blocked it.
Can you send a copy to my home email?

Here you are. Ownship moves along a circle, times are random (not even in correct order, but that can't be seen). Note that the green circles at computed at times of the LOBs, to check that they fits them. Both ownship and target move at constant speed on this picture.

http://roger.questions.cz/other/AutoTMA3.png

Now I tried to add some position error to LOBs. Now it can be seen that near-parallel LOBs gives poor solution. I've also checked that stronger leg (bigger heading change) gives better solution, and with more then 90 degrees turn it gives good solutions even with large artificial errors.

Looks good!

I think in MoBo this:
http://www.xl-logic.com/mobo/tutoria...20081108_2.png

Might be implemented like this:
http://www.xl-logic.com/mobo/tutoria...A_20081108.png

Where we would plot a series of LOBs and then run your gadget to plot the course line and put a contact with motion vector on the last LOB.

There should be also some kind of dot stack, and possibility to adjust the solution manually and see what dots does. There should also be NUMERIC average error. My method then would only give you a estimate which you could work on manually.
But it looks great ! Have you got my mail ?

No... I haven't seen any mail come thru.

If you like you can just copy/paste the code to a PM and I can piece it together on my end. :yep:

More than likely, I'll encapsulate it as a class.

How quickly can this be integrated into Mobo? I'm anxious to try it out.

It's gonna take a little time...

I think maybe before Thanksgiving is possible.

It has been quite some time... Any progress?

Yeah, you're right, it has been a while...

I guess I didn't think there was a whole lot of interest so I wasn't exactly in a hurry. The 1.1 beta does have a few new features, including plot save and unit data entry.

Lemme scan through it again and I'll try to see where it stands.