VOGONS


Serial port errors

Topic actions

First post, by muadeeb

User metadata
Rank Newbie
Rank
Newbie

I'm running an application that requires the serial port for data acquisition. The program runs fine for a couple of minutes, then DOSBox's CPU use drops to 0, and the console shows serial errors. What could be causing this??

System:
P3-1GHz, 512 MB mem (we are planning to put a better machine out there)
WinXP
DOSBox 0.72
McAfee HIPS (Firewall/Virus)
~80% CPU usage
serial configued as Direct (1200 8n1)

Serial errors with overrun (usually 80-100) and very occasional frame errors.

other than a new machine, anything you can think of?

May I apply spices to your beard?

-- Merv the Gryphon

Reply 1 of 8, by h-a-l-9000

User metadata
Rank DOSBox Author
Rank
DOSBox Author

USB-serial?

1+1=10

Reply 2 of 8, by jasshrie

User metadata
Rank Newbie
Rank
Newbie

I am having a very similar error when using DOSBox to try to acquire data through a USB-Serial converter. I am using a HP Laptop with WinXP and no "serial" ports (RS232), thus the USB converter. I have it configured properly in the config file as:

serial1=directserial realport:com11

It appears to work for a few seconds, and then times out with various Serial1: "overrun" errors.
Within XP, the COM11 Configuration is set properly as:
Bits per second: 9600
Data bits: 8
Parity: None
Stop bits: 1
and I assume that DOSBox uses these same values for communication.

The communication works with DOSBox on an old Win2000 box with a "real" serial port in use instead of the USB-Serial adapter.

Any suggestions or ideas?
Thanks.

Reply 3 of 8, by h-a-l-9000

User metadata
Rank DOSBox Author
Rank
DOSBox Author

You can try playing with cycles speed, core and the serial port rxdelay variable. If all fails, maybe such a thing would help:

http://www.usbgear.com/RS232-PCMCIA1.html

1+1=10

Reply 4 of 8, by jasshrie

User metadata
Rank Newbie
Rank
Newbie

I played around with these settings a bit already with no success. I will try again and report back if there is any luck.

About the PCMCIA card, would I not run the risk of the same issues with such an adapter? Or have these been proved to operate more successfully?

Thanks again!

Reply 5 of 8, by h-a-l-9000

User metadata
Rank DOSBox Author
Rank
DOSBox Author

They don't have the USB delay and bugs (you could also try a different "brand" of USB/serial converter - I have not so good experiences with Prolific).

Maybe there is a computer store near you that lets you try it out before you buy...

1+1=10

Reply 6 of 8, by jasshrie

User metadata
Rank Newbie
Rank
Newbie

Hi h-a-l-9000,

I have since acquired a PCMCIA-to-Serial adapter (LogiLink PC0050 Serial CardBus) and found the same issues. Specifically the following:

Serial1: Warning: Tried to activate FIFO
Serial1: Errors Occurred: Framing 0, Paritiy 0, Overrun xx (IFO:y), Break 0

where y was either 0 or 2 and xx was most commonly 01 with higher rxdelay settings, but xx seemed to be dependent on the rxdelay which was used in the config.

Brief trials with alternate cycle speeds and CPU type seemed to have no effect.

Any suggestions?

Thanks again-

Reply 7 of 8, by h-a-l-9000

User metadata
Rank DOSBox Author
Rank
DOSBox Author

You could try the build from my homepage (button below). It has serial FIFO and different timing.

1+1=10

Reply 8 of 8, by jasshrie

User metadata
Rank Newbie
Rank
Newbie

Thanks, I got your MegaBuild 4.1 and will test it out tomorrow. I appreciate the suggestions and will let you know how it goes.