Use a serial-to-Ethernet device with local buffering when the Ericsson PBX must retain outgoing serial logs during PC or network outages. A basic Ethernet-to-serial converter with a virtual COM port can deliver the stream to a listening PC, but it does not provide the same outage protection described for PortStore. Confirm the PBX serial settings and the required retention behavior before selecting or configuring either approach.
What does each log-capture path preserve?
The PBX emits log strings from its serial port. The receiving device or PC must accept those bytes, transport them across Ethernet, and write them to disk. The key selection question is where data is held when the PC or Ethernet connection is unavailable.
| Signal or stage | Source | Wrong-value or failure symptom |
|---|---|---|
| Serial log bytes | PBX serial output | No received text, unreadable characters, or incomplete records can indicate mismatched serial settings or wiring. |
| Serial-to-Ethernet delivery | Converter and Ethernet path | Data arrives only while the network path is available; a non-listening PC can lose outgoing data. |
| Local log buffer | PortStore internal memory | Logs remain available for later transfer when the Ethernet connection is interrupted, subject to the device's buffer capacity and configuration. |
| Disk file | PC software or receiving application | Data may be received but not retained if the application fails to write or save the file. |
A virtual COM arrangement is appropriate when the PC application can stay connected and listening. The described PortStore arrangement is intended for cases where logs must be collected during a network interruption and downloaded after connectivity returns. Neither description establishes a specific buffer size, serial standard, rate, or supported PBX model; read those from the PBX and selected device documentation.
How do symptoms separate serial faults from delivery faults?
Trace the path in order rather than changing settings at random. First determine whether the PBX is producing readable serial output at its port. Then check whether the receiving device sees those bytes, whether Ethernet carries them to the PC, and whether the PC application writes them to disk.
- No data at the receiver: Check that the PBX is configured to emit the expected log output and that the serial connection uses compatible electrical interface, wiring, and communication settings.
- Garbage or malformed characters: Compare the serial format on both ends, including the settings actually exposed by the PBX and capture device. Do not infer a baud rate or framing from the log symptom alone.
- Data arrives only when the PC is open: This is the expected limitation of a converter/virtual-COM workflow if the PC must be listening continuously.
- Data resumes after an outage but has a gap: Determine whether the selected device buffers locally and whether the outage exceeded its available capacity. A converter without local buffering cannot recover bytes it did not deliver.
- Data appears at the PC but no file grows: Check the receiving software's session state, destination path, write permissions, and file-save behavior.
How does buffering change the signal path?
With a virtual COM converter, the PBX serial stream crosses the converter and network to a virtual serial port on the PC. The PC application reads that virtual port as though it were a local serial connection. Because the PC application is the receiver, it must be active and able to consume the outgoing stream; otherwise the log data can be lost.
With PortStore, the device sits at the PBX serial output and captures outgoing strings. When Ethernet connectivity to the PC is available, it forwards the data. When connectivity is absent, it stores data in its internal buffer and can send it after the connection returns. The associated PS Eye software is described as a means to download stored data and save it to a disk file; the stated free-use condition is for non-commercial purposes.
Buffering changes where temporary retention occurs; it does not by itself prove that a log has been archived. The end-to-end record still depends on a successful transfer and disk write. Check the actual device documentation for buffer capacity, overflow handling, supported serial interface and settings, and software compatibility.
How do you install and configure the capture path?
- Inventory the interface. Identify the PBX serial connector, electrical interface, pinout, and configured communication format from its documentation or configuration. Match these to the capture device; do not connect based only on connector shape.
- Choose the retention model. Select a virtual COM converter if a PC application will remain connected and listening. Select a buffering device such as PortStore when logs must be retained through a PC or Ethernet interruption.
- Connect the serial link. Wire the PBX output to the capture device using the documented pinout and compatible interface. Set matching serial parameters at both ends where configurable.
- Configure the Ethernet and host side. Set the network path and configure the PC application to receive the stream. For a virtual COM solution, install the device's virtual COM software and confirm the application uses the resulting port. For PortStore, use the supplied PC software to retrieve and save captured logs.
- Set up persistent file handling. Choose a known destination and verify the receiving software can create and append or otherwise retain log data there. Establish an operational routine for retrieving buffered records after a disconnection.
Do not assume Internet access is necessary for a local Ethernet installation. The device description mentions gateway access as an option, not a requirement. If remote access is required, configure and review that network path separately from the serial capture function.
How do you verify complete logs and avoid recurring failures?
Verify each link independently. Compare a known PBX-generated log event with what appears at the receiver, then confirm the corresponding text is present in the saved file. Check that characters and record boundaries remain readable, and confirm that new data continues to be written during a sustained capture period.
Test the chosen outage behavior deliberately during commissioning. With the virtual COM arrangement, confirm that the PC listener is active before relying on collection; loss of the listener can mean lost output. With a buffer-equipped unit, interrupt Ethernet briefly, restore it, retrieve the stored records, and check that the expected interval appears in the downloaded file. This test demonstrates the actual device and software behavior in the configured installation; it does not establish unlimited outage retention.
Recurring mistakes include treating Ethernet transport as guaranteed storage, assuming a virtual COM port captures data while its host is offline, and overlooking the final disk write. Also avoid selecting an interface or serial format by guesswork. Read the PBX and device manuals, check actual status and buffer information, and verify the saved file rather than relying only on a connected indicator.
Frequently asked questions
How do I capture Ericsson PBX serial logs over Ethernet?
Connect the PBX serial output to an Ethernet-to-serial converter and receive it through a PC virtual COM port, or use a buffering capture device such as PortStore. Choose based on whether collection must continue when the PC or Ethernet link is unavailable.
How do I prevent log loss when the PC is offline?
Use a device with local buffering, then retrieve its stored records after the PC connection returns. A virtual COM workflow requires a listening PC and can lose outgoing data when no application receives it.
How do I save PortStore logs to disk?
Use the supplied PS Eye software to download data held in the device's internal memory and save it as a disk file. Check the software licensing terms for the intended use; the stated free version applies to non-commercial purposes.
How do I troubleshoot unreadable serial log characters?
Compare the PBX and capture-device serial settings and verify the electrical interface and pinout. Check the received stream before troubleshooting Ethernet or file-writing behavior.
When should I stop and contact official support?
Stop before connecting if the PBX interface, pinout, or serial format cannot be identified, or if the selected device documentation does not confirm compatibility. Contact the PBX or capture-device manufacturer through its official support channel with model details, configuration, and observed diagnostics.