Display behavior differs by generation, so several formats are kept separately.
Evidence: SC
Format documented by the project:
F0 05 08 20 <char1> <char2> <char3>
Although Line 6 uses these characters for a preset number, the project reports ordinary ASCII characters also work.
Evidence: SC
open_fbv builds a four-character frame:
F0 05 08 <char1> <char2> <char3> <char4>
and also writes individual positions with commands:
09
0A
0B
0C
in the form:
F0 02 <segment_id> <character>
This is another generation/implementation difference worth capturing.
Evidence: SC
Its channel function sends:
F0 05 08 <group> 20 <number> <channel_char>
then clears the accidental indicator with:
F0 02 20 00
The project defines groups:
'U' = user
'F' = factory
Evidence: SC
Documented form:
F0 <text_length+3> 10 00 01 <ASCII text...>
open_fbv starts its 16-character display write with:
F0 13 10 00 10
then sends 16 display bytes.
FBV-tools also generates a 0x10 main-display transaction beginning:
F0 13 10 00 10
This independently supports a second display format distinct from the FBV3Bridge example.
Evidence: XSC, generation-specific behavior likely.
fbv2kpa and FBV-tools both use command 0x0C to write a note/character after blanking the short display.
Example form:
F0 02 0C <ASCII note>
Evidence: XSC
Both open_fbv and FBV-tools; fbv2kpa also defines the same command:
F0 02 20 <state>
with:
00 = off
01 = on
Evidence: XSC