The WRITELOG command, which can be run from a Lua Script, writes out the .SUM file (as well as other information). More LUA code could read the .sum file and transform it to XML, but I don't think this is the most efficient approach.<br>
<br>The UDP summary information broadcast packets are well documented here:<br><br><a href="http://download.win-test.com/utils/SummaryBroadcastingSpecs.txt">http://download.win-test.com/utils/SummaryBroadcastingSpecs.txt</a><br>
<br>If that spec. is still accurate, I think a Python program could monitor these UDP packets and transform them into the format required by GetScores.<br><br>If someone can point me to what is required by GetScores, I can give it a try.<br>
<br>73,<br>Bob, N6TV<br><br><div class="gmail_quote">On Thu, Jan 13, 2011 at 4:27 AM, Stefan Pfeiffer <span dir="ltr"><<a href="mailto:stefan@fam-pfeiffer.de">stefan@fam-pfeiffer.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hi!<br><br>I am not proficient in LUA and the API Win-Test exposes, but I know others are:<br>Is there any possibility to access the information needed by GetScores via LUA Script and to write them to disk (if not send them to getScores directly), and call that script periodically?<br>
<br>Just an idea...<br><br>Vy 73 es 55 de Stefan, DL1ELY<br><br><br><div class="gmail_quote">2011/1/13 Hans Johansson <span dir="ltr"><<a href="mailto:sm0imj@gmail.com" target="_blank">sm0imj@gmail.com</a>></span><div>
<div></div><div class="h5"><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hi all,<div>Have listened to one of my ham friends who has been looking into this issue.</div><div>It would be very difficult to develop a GetScores update utility without changing the possibility to access the Win-Test summary information in a more easy way. It should not be that difficult to implement a small hack that write/update the summary information in an easily accessible format, e.g. XML.</div>
<div><br></div><div>cheers</div><div>Hans - SMØIMJ</div><div><br><br><div class="gmail_quote">On Sat, Jan 8, 2011 at 8:15 PM, G3WVG <span dir="ltr"><<a href="mailto:g3wvg@btinternet.com" target="_blank">g3wvg@btinternet.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Hello Marios and Happy New Year<br>
<br>
Your suggestion sounds a good one to even though I don't really understand it! Sadly computer programming is not my ( very limited) skill set. It would certainly seem to be worthwhile having WT users represented on the GetScores site . I completely understand that you have more pressing work, I am amazed at the massive effort you guys manage to devote to the hobby, and the majority of us simply benefit from your work. So thanks!<br>
73 Ian G3WVG<br>
<br>
Sent from my mobile<br>
<div><div></div><div><br>
<br>
On 8 Jan 2011, at 12:24, Marios Nicolaou <<a href="mailto:drmarios@gmail.com" target="_blank">drmarios@gmail.com</a>> wrote:<br>
<br>
> Hi all<br>
><br>
> HNY.<br>
><br>
><br>
> I know there has been some interest regarding the getscores conduit recently. Unfortunately, due to computer crash, I ve lost the source code so I cannot update the code in order to make it compatible with the current getscores specs. Most of the code was based on trying to listen to UDP packets, work out qsos, mults and score, decoding the type of mults depending on the contest type before reformatting them for the getscores protocol. It was mostly IF statements etc This was very prone to bugs and vulnerable to protocol changes.<br>
><br>
> My suggestion was for this information which was readily available in the summary window to be dumped in an xml format onto the hard drive every minute. It then becomes very easy for anyone to read this information and upload it to the getscores website! Unfortunately, I dont have the time to re-write the initial code [too many other projects etc] although I would consider implementing the 2nd approach I suggested above if the developers feel is a viable option.<br>
><br>
> 73s<br>
><br>
><br>
> --<br>
> Marios<br>
> 5B4WN/G0WWW<br>
</div></div><div><div></div><div>> _______________________________________________<br>
> Support mailing list<br>
> <a href="mailto:Support@win-test.com" target="_blank">Support@win-test.com</a><br>
> <a href="http://www.f5mzn.org/cgi-bin/mailman/listinfo/support" target="_blank">http://www.f5mzn.org/cgi-bin/mailman/listinfo/support</a><br>
_______________________________________________<br>
Support mailing list<br>
<a href="mailto:Support@win-test.com" target="_blank">Support@win-test.com</a><br>
<a href="http://www.f5mzn.org/cgi-bin/mailman/listinfo/support" target="_blank">http://www.f5mzn.org/cgi-bin/mailman/listinfo/support</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Hans Johansson - SMØIMJ<br>mailto:<a href="mailto:sm0imj@ssa.se" target="_blank">sm0imj@ssa.se</a><br><a href="http://sm0imj.com" target="_blank">http://sm0imj.com</a><br>
</div>
<br>_______________________________________________<br>
Support mailing list<br>
<a href="mailto:Support@win-test.com" target="_blank">Support@win-test.com</a><br>
<a href="http://www.f5mzn.org/cgi-bin/mailman/listinfo/support" target="_blank">http://www.f5mzn.org/cgi-bin/mailman/listinfo/support</a><br>
<br></blockquote></div></div></div><br>
<br>_______________________________________________<br>
Support mailing list<br>
<a href="mailto:Support@win-test.com">Support@win-test.com</a><br>
<a href="http://www.f5mzn.org/cgi-bin/mailman/listinfo/support" target="_blank">http://www.f5mzn.org/cgi-bin/mailman/listinfo/support</a><br>
<br></blockquote></div><br>