in Search
Untitled Page

ARCHIVED FORUM -- April 2007 to March 2012
READ ONLY FORUM

This is the first Archived Forum which was active between 17th April 2007 and 1st March February 2012

 

Latest post 02-01-2011 10:26 AM by Keith Saunders. 9 replies.
Page 1 of 1 (10 items)
Sort Posts: Previous Next
  • 01-24-2011 12:52 PM

    Make an XML file?

    When I have the codes from a remote what do I need to further use to create my own XML file to my Beo5/6 !

    My Bang & Olufsen....

    • BeoCenter 2 DAB/DVD mk.II
    • BeoVision 7-40 DVD mk.III
    • BeoLab Penta mk.III
    • BeoLab 4000 icepower
    • BeoLab 4000
    • BeoLab 3500
    • Beo 5
    • Beo 4 mk.I & mk.III
    •  
    • Beocom 6000
    •  
    • A8 Earphones

     

     

  • 01-26-2011 6:28 AM In reply to

    • adro
    • Not Ranked
    • Joined on 08-26-2009
    • Posts 23
    • Gold Member

    Re: Make an XML file?

    Yes, please.

    There must be someone that are able to give us a brief tutorial.

    I have read all about it in this forum, but Lintronic have a new software, so I am a bit confused

    I am not sure what I need concerning hardware and software, please tell me.

    I know there are a few members here with good knowledge on this, and the Beo6 looks very promising.

     

    Ps

    I have access to Beo configurator,and my local Beo guy are willing to help me.

    adroSmile

  • 01-31-2011 10:11 AM In reply to

    Re: Make an XML file?

    Building any XML file without a software tool will be time consuming, but clearly can be done using any text editor.

    XML stands for eXtensible Markup Language and is a standard flat text file which is designed to transport and store data. All XML files must start with a Root parent and everything below the root will be defined by the application.

    The following is a one command basic example with IR pulses using RAW meaning the Pulses and Pauses (Mark & Space) of the IR signal in micro seconds are defined in Hexadecimal (Value to the power of 16)

    <?xml version="1.0" encoding="utf-8"?>
    <root stVersion="1.3">
      <resource>
        <image stName="NonBO" stFile="Images\NonBO.bmp" />
      </resource>
      <product stName="Tillquist" stCaption="Tillquist" stImage="NonBO" stProductType="accessories3Party" stAV="AV1" stAV1OUT="SCART" stScreenType="1">
        <source_item stName="Tillquist" stCaption="Tillquist" stShortPressCommand="Tillquist" stScreenType="0" stMenuCaption="Tillquist" stSourceType="accessories3Party" stIR="" nPreferedRow="4" nPriority="1" nPreferedColumn="1" nPage="1" nX="0" nY="95" nWidth="213" nHeight="25" nRowFinal="4" nColumnFinal="0">
          <source_subItem stName="UP" stCaption="UP" stMenuCaption="UP" stScreenType="0" stIR="RAW:GlobalManual=1#ListOfFlanks=$0239,$01B5,$0236,$01B6,$0238,$01B6,$0237,$01B5,$0237,$01B6,$0237,$01B5,$0237,$01B5,$0237,$01B6,$0237,$01B5,$0237,$01B3,$0236,$446C,$00E7,$1CA0,$00FD,$1CA6,$00FD,$1CA7,$00E7,$12F0,$00E5,$1CCA,$00CA,$130E,$00CB,$130E,$00C9,$130E,$00CB,$130E,$00CA,$130E,$00C8,$1CC6,$00CC,$62F6#IRSEQUENCE=RAW#Carrier=38000#Pause1=65000#Pause2=65000#Comment=RAW FlankList:46 Flanks" stLeave="Rel 1"  nPage="1" nX="0" nY="20" nWidth="213" nHeight="25" nRowFinal="1" nColumnFinal="0" stTextColor="255:255:255" nHidden="0" />
              </source_item>
      </product>
    </root>

    So, in my example we have a 3rd party product called Tillquest with the "UP" command being defined.

    So, if we focus on the command itself it takes the form of:-

    <source_subItem stName="UP" stCaption="UP" stMenuCaption="UP"

    then we have the actual pulses in Hex in quotes after "stIR"

    stIR="RAW:GlobalManual=1#ListOfFlanks=$0239,$01B5,7,$01B6,$0237,$00E7,$0CC6,$00CC,etc etc...#IRSEQUENCE=RAW

    The Carrier frequency and maxmium pulse string length follows still within the stIR quotes

    Carrier=38000#Pause1=65000#Pause2=65000#Comment=RAW FlankList:46 Flanks"

    What follows defines where on the screen the button is to be positioned and its colour if defined, it also shows its not hidden

    nPage="1" nX="0" nY="20" nWidth="213" nHeight="25" nRowFinal="1" nColumnFinal="0" stTextColor="255:255:255" nHidden="0"

    As you can see it is possible to create and/or edit your own XML file with any text editor and if you were planning to do this the quickest way would be to edit an existing XML file.

    You then ask, but I have captured the IR codes from the original, how do I convert it to the correct form to put into the XML file, well that depends on how you captured the IR codes. If you captured it with a Lintronics box you can either use the Lintronic software or the Beoworld XML Generator which is downloadable from the Beoworld web site.

    Regards Keith....

  • 01-31-2011 11:51 AM In reply to

    Re: Make an XML file?

    Thanks for a good post.

    Since I do not have a LinTronic box so that possibility is excluded.

    Can Beoworld XML Generator help me if I have the IR codes from eksembel Sony ?

    My Bang & Olufsen....

    • BeoCenter 2 DAB/DVD mk.II
    • BeoVision 7-40 DVD mk.III
    • BeoLab Penta mk.III
    • BeoLab 4000 icepower
    • BeoLab 4000
    • BeoLab 3500
    • Beo 5
    • Beo 4 mk.I & mk.III
    •  
    • Beocom 6000
    •  
    • A8 Earphones

     

     

  • 01-31-2011 12:09 PM In reply to

    Re: Make an XML file?

    I do not know what "eksembel" means ?

    The Beoworld XML Generator will ONLY convert Lintronic timings to a RAW XML file, so if you do not have a Lintronic box that is not an option.

    Exactly what product are you trying to create an XML file for ?

    Regards Keith....

  • 01-31-2011 12:45 PM In reply to

    Re: Make an XML file?

    Sorry, "eksembel" = examble.

    A friend of mine asked if it is possible to create a XML for a Sony amplifier.

    Which model I do not know yet.

    My Bang & Olufsen....

    • BeoCenter 2 DAB/DVD mk.II
    • BeoVision 7-40 DVD mk.III
    • BeoLab Penta mk.III
    • BeoLab 4000 icepower
    • BeoLab 4000
    • BeoLab 3500
    • Beo 5
    • Beo 4 mk.I & mk.III
    •  
    • Beocom 6000
    •  
    • A8 Earphones

     

     

  • 01-31-2011 12:55 PM In reply to

    Re: Make an XML file?

    Creating an XML file for Sony products is not normally any problems.

    If you or your friend do not have a means of capturing the IR codes for the Sony Amplifier, it is possible that someone has previously produced Pronto Hex codes for that product which can then be converted.

    The best place to find such codes is HERE

    Regards Keith....

  • 01-31-2011 1:24 PM In reply to

    Re: Make an XML file?

    Thanks Yes -  thumbs up

    My Bang & Olufsen....

    • BeoCenter 2 DAB/DVD mk.II
    • BeoVision 7-40 DVD mk.III
    • BeoLab Penta mk.III
    • BeoLab 4000 icepower
    • BeoLab 4000
    • BeoLab 3500
    • Beo 5
    • Beo 4 mk.I & mk.III
    •  
    • Beocom 6000
    •  
    • A8 Earphones

     

     

  • 02-01-2011 7:59 AM In reply to

    • adro
    • Not Ranked
    • Joined on 08-26-2009
    • Posts 23
    • Gold Member

    Re: Make an XML file?

    Thank you Keith.

    I slowly start to understand some of this.

    I have created my first xml file today.

    I is a full Panasonic plasma tv file, model Th-Pv600.

    However trying to make one for my cable box, I get an error:

     

    Error:Programs_TrimCodestring:9, subscript out of range.

     

    The box is made by Sagem, and the code is captured from the original remote with a pronto remote.

    Regards

    Atle

     

  • 02-01-2011 10:26 AM In reply to

    Re: Make an XML file?

    Atle,

    adro:

    However trying to make one for my cable box, I get an error:

    Error:Programs_TrimCodestring:9, subscript out of range.

    The box is made by Sagem, and the code is captured from the original remote with a pronto remote.

     

    If you get a "TrimCodestring" error it means one of your text values is to long in your configuration file.

    I suggest you post the 3rd party XML file you have made and I will have a look at it.

    Also, you say you captured the Sagem with a Pronto remote, however many Sagem products use the Philips RC5 protocol which means every other subsequent press of the same button will provide a different code because in this protocol bit 3 called the "Toggle" bit gets inverted with each press.

    Regards Keith....

Page 1 of 1 (10 items)