Menu

Modifying Demo_3CN using openCONFIGURATOR

Help
Simon Fok
2017-05-09
2017-05-09
  • Simon Fok

    Simon Fok - 2017-05-09

    Hi,

    I want to understand the way the objects are being specified using openCONFIGURATOR. Specifically in Demo_3CN, under the four columns: S.No / Object / Sub-object / Length / Offset, we currently have

    1 / DigitalInput_00h_AU8(x6000) / DigitalInput(0x01) / 0x0008 / 0x0000

    What is the significance of having “00hAU8(x6000)” part of DigitalInput in naming the object? Likewise does (0x01) have any significance in specifying the Sub-object? In other words, are they for clarifications or needed to generate the correct outputs (xap.h...)?

    Instead of sending just 1 byte to CN_1, I want to send 2 additional data objects (one is 16 bit and the other 32 bit) with no sub- Objects, is the following correct?

    2 / DigitalInput_01h_AU16(x6000) / DigitalInput(0x01) / 0x0016 / 0x0016
    3 / DigitalInput_02h_AU32(x6000) / DigitalInput(0x01) / 0x0032 / 0x0048
    4/ 0x0000 / 0x00 / 0x0000 / 0x0048
    .etc....

    Thanks in advance,
    Simon

     
  • Simon Fok

    Simon Fok - 2017-05-09

    Hi,

    Please disregard my previous post, I was reading off Raspberry Pi2 instructions regarding using openCONFIGURATOR. Now I understand that if I need to make certain changes, I simply import Demo_3CN into openCOnFIGURATOR. To do what I described (8 bit data followed by 16 bit and 32 bit data), I will probably need to create a custome XDD device/file.

    Simon

     

Log in to post a comment.