More actions
No edit summary |
No edit summary |
||
| Line 84: | Line 84: | ||
* undefined / un - The message sent is in the ''undefined'' category, sent in ''plain text'' | * undefined / un - The message sent is in the ''undefined'' category, sent in ''plain text'' | ||
* priority / pri - The message sent is in the ''priority'' category, sent in ''plain text'' | * priority / pri - The message sent is in the ''priority'' category, sent in ''plain text'' | ||
* error / err - Signals that an ''error'' has | * error / err - Signals that an ''error'' has occurred, sent in ''plain text'' | ||
* expressionparser / ep - | * expressionparser / ep - These messages contains debugging information regarding the internal ''expression parser'' and is used for development | ||
* | *debug / dbg - These messages contains various debugging information and is used for development | ||
* inforequest / irq - Signals that an ''info request'' has been returned. This is a | *help / hlp - Signals that the message is a response to a ''help''-command being sent to the Ekdahl FAR. These messages are structured so that a receiver, like the ''Configuration utility'', can parse information about available ''commands'' in the current ''firmware'' and relay it to a user in a structured way. | ||
* inforequest / irq - Signals that an ''info request'' has been returned. This is a specialized message that is either sent as a response to an ''rqi''-command or as a ''interrupt''-message telling the user or receiving software about different parameters in the Ekdahl FAR. These messages follows the same structure as regular ''command message''s of ''[irq]commandname:parameter1 [etc]'' so that it can be used by a receiving software to keep track of parameter changes | |||