Question about baud rate throttle of RealPort

hi, I am a new user of RealPort and PortServerII.

I installed RealPort on my host and connect to PortServerII. My host want to use virtual COM port installed by RealPort to send data to other devices connected to PortServerII.

My question is:

  1. How fast can my software on host send data to RealPort? Is it possible to no do throttle on my software? My software do not want to control the baud rate when write data to COM.
  2. Can Port ServerII control the baul rate during output?
  3. Can PortServerII broadcast data recieved from RealPort to all COM port connected to it?
    thank you very much.

RealPort is designed to allow the software to control the speed at which the serial port is opening at. It is not controled at the device level. If you need to have the Digi control the baud rate, you may want to look at using something like TCP Sockets where you do hard code the baud rate on the Digi. You would not be using COM ports when setup this way, however.

The maximum speed you can open the serial port at would be 115200 bps.

The PortServer II does not have the port sharing feature that would allow the data received on the serial port to broadcast to all devices listening on that port. You would need our PortServer TS product line to have that feature.

thank you very much for your explaination.

Our need is that a host sends out data via TCP or UDP and a device or software is needed to transfer these data to some devices connected with COM port.

Is it possible for my host to connect to Digi device via TCP or UDP directly (RealPort is not needed) and Digi device transfer data to COM port devices with baud control? Is there this kind of Digi product?
I think there is a protocol between host and Digi device for data transfer via TCP/UDP. Where can I find that protocol?

thank you.

Digi PortServer TS products, the PortServer II and some other products allow you to configure a port for a TCP or UDP connection and there is no need for using a RealPort driver.
No additional protocol is required.
Using hardware flow control is recommended.
Check the Configuration and Administration Guide for details: