To successfully set up the Pira CZ Remote COM Port tool (Piracom), you must configure it as a network TCP server that links a physical COM port on a remote PC to automation clients over the network. This utility allows broadcast automation software or control applications like Magic RDS to manage hardware devices (such as a PIRA32 RDS encoder) remotely over TCP/IP networks. 1. Server-Side Configuration (PC Connected to Hardware)
Run the Pira CZ Remote COM Port utility directly on the PC physically connected to the RDS encoder hardware.
COM Port: Select the physical, local COM port number where your RDS hardware device is attached.
Baudrate: Adjust this to match the exact baud rate of your hardware device (typically 19200 or 9600 bps depending on your encoder configuration).
Network Port: Define the local TCP listening port (e.g., 10001) that remote network clients will target.
TDMA Settings: If multiple clients are sending data simultaneously, switch this to RDS. This manages concurrent RX lines to smoothly stream incoming data packets without timing collisons.
Buffer Adjustments: Set a higher Tx Buffer Size if your application regularly broadcasts large data scripts, preventing common Buffer Overflow (B/O) errors.
Initiate Server: Click the Run! button to initialize connection listening and open communication channels. 2. Client-Side Software Setup
Once the server application is actively running, point your studio playout software or control tool toward the host server. Configured with Magic RDS Open the application and go to the Preferences panel. Select the TCP/IP communication protocol option.
Input the IP address of the remote server PC along with the assigned network port number.
Increase the application’s internal COM port timeout limit to a minimum of 4 seconds to prevent unwanted communication error alerts.
Save your settings, close the dialog, and verify that the status bar displays Connected. Configured with Broadcast Playout Automation (e.g., NexGen)
Navigate to your playout tool’s Data Export / Formatting options menu.
Establish an export output profile using the TCP-IP connection configuration.
Input the target server machine’s IP address along with the precise listening port mapped inside the server utility.
Map your desired text output parameters (such as RT1= for Radiotext fields) to dynamically forward real-time song data over the network. 3. IP Access Restrictions & Security
You can secure network communication directly from within the application directory by managing text lists:
Create a text file titled piracom.ban inside the application folder to specify explicit, line-separated network IP addresses that should be denied connection rights.
Create an optional piracom.vip text file to declare authorized exceptions to your banned listing filters.
Note: Both text layouts fully support standard wildcard text characters (*).
If you run into any initial timeout blocks, ensure your local router or network firewall policy explicitly permits traffic through your designated TCP listening port. To help you troubleshoot further, tell me:
Which RDS encoder model (e.g., PIRA32, P132, P164) are you deploying?
What specific broadcast automation or control software are you using?
Are your devices operating across a Local Area Network (LAN) or an external Wide Area Network (WAN)? Pira CZ Remote COM Port
Leave a Reply