Das ist der Follow-up Defekt von #261.
Beim kontinuierlichen Abfragen vom Gewicht wird von Zeit zu Zeit zu einer Exception in der Function Parse().
An unhandled asynchronous non-synchronized exception occurred while running Albatros.
Albatros Beta 4 Candidate 3 Development Version 1.00.07
Exception
Exception:
Type: YAT.Domain.Parser.FormatException
Message:
"L" is no ascii mnemonic!
The following formats are supported (type without quotes):
Default "OK"
Binary "\b(01001111 01001011)"
Octal "\o(117 113)"
Decimal "\d(79 75)"
Hexadecimal "\h(4F 4B)"
Character "\c(O K)"
String "\s(OK)"
ASCII controls (0x00 to 0x1F) "<CR><LF>"
Format specifiers are case insensitive, e.g. "\H" = "\h", "4f" = "4F", "<lf>" = "<LF>"
Formats can also be applied on each value, e.g. "\d(79)\d(75)"
Formats can be nested, e.g. "\d(79 \h(4B) 79)"
Three letter radix identifiers are also allowed, e.g. "\hex" instead of "\h"
In addition, C-style escape sequences are supported:
"\r\n" instead of "<CR><LF>"
"\0" instead of "<NUL>" or \d(0) or \h(0)
"\01" instead of \o(1)
"\12" instead of \d(12)
"\0x1A" or "\x1A" instead of \h(1A)
Type \\ to send a backspace
Type \< to send an opening angle bracket
Type \) to send a closing parenthesis
In addition, the following keywords are supported:
Clear the monitors "Send something\!(Clear)"
Delay sending "Send something\!(Delay)Send delayed" according to advanced settings
Output break state on "\!(OutputBreakOn)"
Output break state off "\!(OutputBreakOff)"
Output break state toggle "\!(OutputBreakToggle)"
Output break state only applies to serial COM ports
Source: YAT.Domain
Stack:
bei YAT.Domain.Parser.Parser.Parse(String s, Modes modes, String& parsed) in D:\_Projekte\Albatros\05-Source\Albatros\YAT\YAT.Domain\Parser\Parser.cs:Zeile 1233.
bei YAT.Domain.Parser.SubstitutionParser.Parse(String s, CharSubstitution substitution, Modes modes, String& parsed) in D:\_Projekte\Albatros\05-Source\Albatros\YAT\YAT.Domain\TextTerminal\SubstitutionParser.cs:Zeile 190.
bei YAT.Domain.Parser.SubstitutionParser.Parse(String s, CharSubstitution substitution, Modes modes) in D:\_Projekte\Albatros\05-Source\Albatros\YAT\YAT.Domain\TextTerminal\SubstitutionParser.cs:Zeile 180.
bei YAT.Domain.TextTerminal.ProcessParsableSendItem(ParsableSendItem item) in D:\_Projekte\Albatros\05-Source\Albatros\YAT\YAT.Domain\TextTerminal\TextTerminal.cs:Zeile 303.
bei YAT.Domain.Terminal.ProcessSendItem(SendItem item) in D:\_Projekte\Albatros\05-Source\Albatros\YAT\YAT.Domain\Terminal\Terminal.cs:Zeile 590.
bei YAT.Domain.Terminal.SendThread() in D:\_Projekte\Albatros\05-Source\Albatros\YAT\YAT.Domain\Terminal\Terminal.cs:Zeile 566.
bei System.Threading.ThreadHelper.ThreadStart_Context(Object state)
bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
bei System.Threading.ThreadHelper.ThreadStart()
New test case added: YAT.Model.Test.MtSicsDeviceTransmissionTest
'S' test case executed with 1 - 10 - 100 - 1000 - 1 Mio Loops (24 hours): Issue could not be reproduced
'SI' test case executed with 240000 loops (1 hour): Issue could not be reproduced
'I1' test case executed with 72'000 loops (1 hour): Issue could not be reproduced
'S' + 'SI' + 'I1' + 'I6' test cases executed (total execution time more than 4 hours, didn't include 24 hour test cases): Issues could not be reproduced
Several test cases repeated while Cpukiller3 was using 98% of all CPU cores: Issues could not be reproduced
Format exceptions while sending are now reported as error messages within the terminal (bug #270)