Data Provider - exception in log

[curbz 22]

Hi Nico,

I'm writing an experimental data provider and I'm seeing the following in the logs:

Connecting QNHReader to UDP port 49004 ...
QNHReader connected
Connecting TrafficReader to UDP port 49003 ...
TrafficReader connected
20:57:44 ? Unhandled exception in processLine invalid stoul argument
20:57:52 ? Unhandled exception in processLine invalid stoul argument
20:58:00 ? Unhandled exception in processLine invalid stoul argument
20:58:06 No QNH?
20:58:08 ? Unhandled exception in processLine invalid stoul argument
20:58:16 ? Unhandled exception in processLine invalid stoul argument
20:58:24 ? Unhandled exception in processLine invalid stoul argument
20:58:32 ? Unhandled exception in processLine invalid stoul argument
20:58:36 No QNH?
20:58:40 ? Unhandled exception in processLine invalid stoul argument
20:58:48 ? Unhandled exception in processLine invalid stoul argument
20:58:56 ? Unhandled exception in processLine invalid stoul argument
20:59:04 ? Unhandled exception in processLine invalid stoul argument
20:59:06 No QNH?

Do you know what might be the cause?

thanks

Darren

[kiek 1,213]

19 minutes ago, curbz said:

20:57:44 ? Unhandled exception in processLine invalid stoul argument
20:59:06 No QNH?

The invalid stoul argument means that PSXT tries to convert a string to an unsigned long, for the hex-id (decimal), but what you provide is not un unsigned integer...

No QNH means that during the last 30 seconds no QNH message was received.

[curbz 22]

32 minutes ago, kiek said:

The invalid stoul argument means that PSXT tries to convert a string to an unsigned long, for the hex-id (decimal), but what you provide is not un unsigned integer...

No QNH means that during the last 30 seconds no QNH message was received.

thanks - most helpful