Announcement

Collapse
No announcement yet.

4D Systems Documentation errata:

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • 4D Systems Documentation errata:

    Visi-Genie-User-Guide-REV1.PDF

    refers to Application notes 4D-AN-P1xxx which are in disagreement with the actual
    application notes present at http://www.4dsystems.com.au/appnotes.php; it
    should read 4D-AN-P4xxx instead; Visi-Genie-Reference-Manual-REV1.PDF

    does not clearly define the sizes of the data elements being transmitted;

    does not clearly define the actions to be taken upon receipt of a ACK|NAK; implies that the host should or could ACK|NAK but is not clear as to whether it
    must ACK|NAK, or when if so;

    there appears to be some mandatory delay time required between the sending of
    one or more WRITE_OBJ commands and the processing of their respective ACKs
    which varies directly with the number of UI elements displayed; adding UI elements
    requires increasing the delay time to avoid timeouts during receive operations on
    the host; this behavior is not documented; (with a single Gauge on the display
    running at 115,200 baud 10mS delay between the checksum and the ACK receive is
    adequate, with a Gauge and one set of Leddigits being separately updated using \
    WRITE_OBJ a 100mS delay between the checksum and the ACK receive is
    adequate; these were arrived at empirically however which is not acceptable).
    WRITE_STRU is not clear as to whether the string length parameter (parameter 2)
    is expressed in bytes or characters; "Message length is 4 bytes + the number of
    string characters (including the null terminator)." further it states "including null
    terminator" then in Note2 states that "The String should not be null terminated".

    READ_OBJ states that the display will reply with a either a NAK or a REPORT_OBJ
    message but on the same page states that it only replies with "the Object-ID and
    Object Index/Item followed by 2 byte value that indicates the state of that item";

    PICASO-SPE-COMMAND-SET-REV1.pdf

    the following commands are not documented but exist in the various serial libraries:
    txt_Set
    txt_Wrap
    file_LoadImageControl

    the format of the data written to a file by the file_ScreenCapture comand and
    displayed by file_Image is not documented;

    gfx_ClipWindow requires that gfx_Clipping(1) be called after gfx_ClipWindow to
    operate properly; this behavior is not documented;

    ...M


  • #2


    Wow, great first post, I'll let the Doco people respond to the 'pure' documentation points, just want to touch on a few of the other things

    there appears to be some mandatory delay time required between the sending of one or more WRITE_OBJ commands and the processing of their respective ACKs which varies directly with the number of UI elements displayed; adding UI elements requires increasing the delay time to avoid timeouts during receive operations on....

    When you sent a command you should wait for the ACK before sending another command as per the documentation, the duration of each command varies and has practically nothing to do with the number of objects present.

    It is not possible to document how long each command takes as it is influenced by many things:-
    1. Size of the object to be displayed (single biggest influence)
    2. Latency in sending system and hardware (Windows and CE5s especially)
    3. Comms Speed
    4. uSD Speed (note the uSD uses SPI mode and manufacturers speeds are specified for SD mode, there is no relationship. uSD Speeds will only vary by about 10% in SPI mode)
    5. What the display is doing (eg, playing video / sound)
    6. What the user is doing (eg touching or moving touch)

    the following commands are not documented but exist in the various serial libraries:
    txt_Set
    (snip)
    file_LoadImageControl
    txt_Set is not documented because it is 'superceeded' by the shortcut commands to what it does (eg txt_Bold, txt_Italic, etc.) it exists merely to assist conversion of Designer programs to serial programs more easily.
    file_LoadImageControl is documented in section 5.6.31

    the format of the data written to a file by the file_ScreenCapture comand and
    displayed by file_Image is not documented;
    This is documented in the FAQ section of this forum http://4d.websitetoolbox.com/post/Graphics-Composer-and-the-Display-Modules-5438283?highlight=format
    Mark

    Comment


    • #3


      Thanks for the clarifications.

      Regarding the WRITE_OBJ timing, I have started another thread as I would like to discuss it further but it probably doesn't belong here. Sorry.

      Regarding the last reply on the file formatting, I would think it beneficial for the primary reference documents to have the information presented with the commands rather than having to hope to find it somewhere in a FAQ or forum.

      Comment

      Working...
      X