Art-Net implementation: wrong package header
  • User avatar
    cansik
    member
    Posts: 20
    Joined: Mon Apr 27, 2015 9:40 pm
    Location: Zurich
    Contact:

    Art-Net implementation: wrong package header

    by cansik » Sat Mar 10, 2018 12:16 am

    It seems that Mad Mapper is sending an Art-Net package without a valid header. The header of the package I receive (only from time to time, and it is not the OP_DMX package) looks like the following:

    HEX: 41 72 74 2D 45 78 74 00
    Dec: 65 114 116 45 69 120 116 0
    Ascii: Art-Ext
    But as documented in the specification it should be:

    HEX: 41 72 74 2D 4E 65 74 00
    Dec: 65 114 116 45 78 101 116 0
    Ascii: Art-Net
    The OP_CODE of the message is 8193 / 0x33303 which refers to no official Art-Net OP_CODE. The package length is 2048 bytes long.

    So could you please help me to understand why you are sending this message and how to interpret it?
  • User avatar
    cansik
    member
    Posts: 20
    Joined: Mon Apr 27, 2015 9:40 pm
    Location: Zurich
    Contact:

    Re: Art-Net implementation: wrong package header

    by cansik » Sat Mar 10, 2018 12:24 am

    Found an answer on my own. It looks like Matthieu has created an own discovery extension for Art-Net which is called Art-Ext:

    https://github.com/mattbeghin/Art-Ext-Poll
  • mad-matt
    garageCube team
    Posts: 573
    Joined: Mon Sep 09, 2013 5:50 pm

    Re: Art-Net implementation: wrong package header

    by mad-matt » Tue Mar 20, 2018 1:13 am

    That's an extension we designed together with Advatek but it's now useless since both Advatek Pixelite & MadMapper are following ArtNet 4 specifications (about polling when a device uses more than 4 universes). We keep it for compatiblity with old Pixelite firmware for a few years and will remove it.

Who is online

Users browsing this forum: No registered users and 50 guests