Prinect reconnect after network reconfig

Discussion in 'Heidelberg Printing Presses' started by bryhal, Jul 12, 2024.

  1. bryhal

    bryhal New Member

    Joined:
    Jul 2024
    Messages:
    1
    Location:
    Toronto
    Hi all, new here, more of an IT/prepress guy here. I've been tasked with getting Prinect to work after the IP address of the consoles (XL, CX) were changed (network reconfiguration). Anyone who might have known how this works doesn't work here anymore ;-)
    I'm poking around the config areas of Cockpit and don't see anything linking Prinect to a press IP address. How does the a press console link to a Prinect server? I can ping the IP of the consoles from the Prinect server successfully but there are 'unavailable' in cockpit.
    They just want Prinect for job data collection, they previously used it for ink key settings until being superseded by Inkzone DIPlot. Job PPF files come from Prinergy, that part I have figured out.
    I'm not a press operator so have zero familiarity with the press console GUI, is it involved in re-establishing this connection?
     
  2. Adil

    Adil Senior Member

    Joined:
    Nov 2021
    Messages:
    1,287
    Location:
    Casablanca
    Enter to the menu diagnosis then puch network the machine will be ping after that it give you where is the communication problem.
    Normally the communication is doing by a standard protocole tcp/ip .
    But Firstly, the Heidelberg offset machines and the Prinect server need to be connected to the same computer network. This could be a local area network (LAN) within the print shop installation.
    Please can you tell me why do you need configuration for prinect .
    If you have some difficult to do that there is another way to monitor real-time performance of the offset machines, collect data on ongoing jobs, and provide analytics that help optimize printing processes and improve productivity.
    Let me know i have a good solution
     
Loading...