• State Not Answered
  • Date
    billy
  • Date
  • Replies 33 replies
  • Subscribers 6 subscribers
  • Views 6390 views
  • Users 0 members are here
Options
Related

CITP

I have a gen 1 Axon running 2.1.2 on the test bench. I have yet to get it to sync its custom content to the console (Hog 4 2.0). It shows up in the CITP screen when you hit patch media, and responds to control via artnet, so networking is good, but the refreshing icon in the media picker just spins and spins for hours. It eventually goes away, but the custom content never populates in the media picker. I know the media was loaded under 2.0.5 and earlier and 2.1.2 was installed later on.

Do I need to select the global fixture, a single media layer, all media layers, or all media and global before hitting update media? I think I've tried all those permutations with no success, I just want to make sure I'm doing it the right way.
Parents
  • 0
    Can you give me reproducible steps to creating the lockup that does not involve 1-24 hrs?

    Not really. As I said, it's random.

    As far as CITP goes, there has only been one instance (that I anticipated) where I could not get CITP and a Hog 4 to transfer thumbnails. Can you give me an idea of the network the Axon and Hog reside on?

    Hog 4, switch, axon. Or hog 4, router(no internet, just to give the axon an ip address), axon.

    Is it closed or open?

    Closed.

    Have you tried connecting the Axon directly to the console?

    Yes


    For a clean path to get CITP working :
    - Re-image the Axon with System Restore v3.5.1 with v2.0.4.2549 then upgrade to v2.1.2.2659
    - Re-image the Axon with System Restore v3.5.2 with v2.1.2.2659 then downgrade to v2.1.1.1636 then upgrade back v2.1.2.2659.

    I have found some system level libraries missing from the v3.5.2 system restore image. These libraries are needed for CITP to work correctly. These libraries get installed in the upgrade packages from v2.1.0 to v2.1.2.

    Note : A minute or two is needed after the graphics engine starts to write all pertinent registry data and CITP to start. Also, CITP only works in v2.1.0, v2.1.1 and v2.1.2 of Axon software.

    Hope this solves your issues with CITP.

    Would upgrading from 2.0.5 to 2.1.2 install those packages? Because I have done that and still no go. I will try your install path once I get all relevant pieces of hardware in the shop.
Reply
  • 0
    Can you give me reproducible steps to creating the lockup that does not involve 1-24 hrs?

    Not really. As I said, it's random.

    As far as CITP goes, there has only been one instance (that I anticipated) where I could not get CITP and a Hog 4 to transfer thumbnails. Can you give me an idea of the network the Axon and Hog reside on?

    Hog 4, switch, axon. Or hog 4, router(no internet, just to give the axon an ip address), axon.

    Is it closed or open?

    Closed.

    Have you tried connecting the Axon directly to the console?

    Yes


    For a clean path to get CITP working :
    - Re-image the Axon with System Restore v3.5.1 with v2.0.4.2549 then upgrade to v2.1.2.2659
    - Re-image the Axon with System Restore v3.5.2 with v2.1.2.2659 then downgrade to v2.1.1.1636 then upgrade back v2.1.2.2659.

    I have found some system level libraries missing from the v3.5.2 system restore image. These libraries are needed for CITP to work correctly. These libraries get installed in the upgrade packages from v2.1.0 to v2.1.2.

    Note : A minute or two is needed after the graphics engine starts to write all pertinent registry data and CITP to start. Also, CITP only works in v2.1.0, v2.1.1 and v2.1.2 of Axon software.

    Hope this solves your issues with CITP.

    Would upgrading from 2.0.5 to 2.1.2 install those packages? Because I have done that and still no go. I will try your install path once I get all relevant pieces of hardware in the shop.
Children
No Data

www.etcconnect.com