AK-F1 for 2014 races

[Luis Ángel Curiel Sanz]

Hi,

is the library working for 2014 races? I get a lot of "unable to parse" error.

Thanks.

[F1 Looney]

The answer to your questions would seem to be obvious; no, the library does not work with the 2014 protocol.

[Luis Ángel Curiel Sanz]

Thanks... do you know if there are plans for an update? :(

[Piterluis RumoresF1]

Good day!

I am working with C# accessing to the dll. When session is finished, I do not have the "parsing" error. I just have it during session, I suppose when library is analyzing the data is arriving frm server. The error jumps (logically) when we execute the iMensaje = LectorFOM.Read();

If we have a look at the non public array "QueuedMessages", we see "[0] = {SetGridColumnValueMessage(DriverId=2, Column='S2', Colour='Yellow', Value='â— ')}". The cause of that error is that â character instead of a real sector time. If we could pass to the next message in queue when we obtain that error, live timming app could go on running. It is a pity not having sector times... but no chances with current Bernie' politics... 

Anyway Live Timing library is a powerfull tool without sector times. It could be great if this issue could be solved.

Thanks anyway for all efforts, people!

Pedro.

[Piterluis RumoresF1]

I clarify... It seems that now, I suppose race session is finished, I obtain also the parsing error. After qualifying (Before race) I could connect and obtain the positions and times from live timing... Yesterday I did a few tests. Now soft blocks when arrives the first "sector time"...

[Andrea Corbetta]

I made a trivial fix in a local copy of library and it works both on qualifng and in race. I tested today. There are no more sectors time (you have to use DecodeUtf8 in order to retrieve the "°" character) and I don't understand if these informations are in some unknown message or are no more available.

--
You received this message because you are subscribed to the Google Groups "F1 Live-Timing for .NET" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ak-f1-timing...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Andrea Corbetta

[F1 Looney]

r990 disables sector time parsing and also corrects the placeholder decoding.

https://googledrive.com/host/0B6M7_qBxjo9DLXVhTm0xaHYzakU/

[Luis Ángel Curiel Sanz]

One question...

sector times are no longer provided by the protocol or are encoded in a new way that we need to discover?

Thanks.

[F1 Looney]

Sector times, gaps, pit stop times, weather and speed captures are no longer provided; they have been removed from data stream.

[Luis Ángel Curiel Sanz]

But those values were available on the f1 live app... can't we get them?

Thanks.

[Luis Ángel Curiel Sanz]

Here you have some captures from the mobile app for yesterday's race. 

I noticed that there are sector times for the mobile app, but not for the web app. 

Looks like they have restricted the sector times and speed records to mobile apps (possible to avoid what ak-f1 does).

And links where you can see the same (although here there are indeed sector times on web app):

http://www.formula1.com/news/headlines/2014/3/15540.html

https://itunes.apple.com/gb/app/official-f1-app/id835022598?mt=8

https://play.google.com/store/apps/details?id=com.softpauer.f1timingapp2014.basic

Regards.

[F1 Looney]

The mobile applications use a completely different protocol to the formula1.com java applet. Support for this protocol is not going to be added (by me anyway).

[Luis Ángel Curiel Sanz]

Hi,

what about lap times? are they there? Thanks.