The PUC in Beovisions are loaded by dealers using a B&O Service Tool and can be changed at any time by a dealer from a library of PUC files produced by B&O.
Each 3rd party product supported by the PUC and in the library has an associated DEC file. This DEC file is a text file with a format unique to B&O, but in principle is quite simple.
The file defines everything including but not limited too:-
- Each 3rd party product encoded by B&O with its associated IR timings and binary codes
- The commands available in the MENU for that device
The following is a typical example of the GUIDE button for a TOPFIELD 5800
[Signal_btnGUIDE_RepeatSignal]
IRSEQUENCE=NEC
Pause1=0
Pause2=0
Carrier=38
BITLEN=546 570 0
PRESIGNALBITS=0 0
PRESIGNALHI=8995
PRESIGNALLO=2250
BITS=1
[Signal_btnGUIDE]
IRSEQUENCE=NEC
Pause1=39400
Pause2=95500
Carrier=38
BITLEN=546 570 1700
PRESIGNALBITS=0 0
PRESIGNALHI=8995
PRESIGNALLO=4480
BITS=111110110000010000100111110110001
REPEATSIGNAL=1
Comment=NEC 32bits=FB0427D8
I have written a Windows based programme which converts any PUC DEC file into a Beo5 XML file and doing the reverse would not be particularly difficult.
Producing the DEC file for a particular product in my view is not technically difficult, but time consuming without a software tool.
The issue is that only B&O dealers have the Service Tool and the special Masterlink cable which uses pins 9 & 10 to send the data to the PUC in the Beovision.
If you are a B&O dealer reading this and you know how to produce and upload the PUC, then you could produce your own DEC files to add to the B&O library and upload to your customers Beovision. This can be particularly important where you have a customer requirement for a 3rd party product to be controlled by the PUC, yet B&O do not have any plans to add that product to the PUC library. You may not get a big sale for what is a technically small requirement.