Database Search
If you can't find the information using the categories below, post a question over in our WinBatch Tech Support Forum.
TechHome
Serial
 |
- !!NEWSFLASH!!
- !List of Errors Returned from pGetLastError
- Can you do a FileCopy to an Active Port
- Capture Caller ID Information from a Modem
- Comport Being Accessed by More than one Program
- Default X-10 Monitor Sample Code
- Detect if a Line is Busy
- Detecting Valid COM Ports
- Digital Multimeters with Serial Ports
- Direct Serial Connection - No Modem
- Framing Error with Serial Extender
- Hardware Overrun Error
- How to Force a Modem to Continue
- How to Handle the Multiple Downloads with pRecvFile
- Kermit Type Transfers
- Paging and pPutLine
- pComControl
- pComOpen Error 100
- pModemDial Clicking but not Audibly Dialing
- pRecFile Failure
- pSendFile bad port handle
- Receiving Mouse Button Info on Serial Port
- Receiving Parity Error with pRecvFile
- Send Power On Hex Command to a Nec Display
- Sending Control Characters to Com Port
- Serial Communications Problems with pWaitfor
- Serial Extender - Timeouts - Boxes Functions
- Serial Extender and PPP connections
- Serial Modem Transferring Files
- Uploading Text Files using Serial Extender
- Using pCapture to Capture Log
- VT100 Emulation - ANSI chars and Serial Extender
- X-10 Control Sample Script II
- X-10 Control Sample Script
- X-10 FAQ
- X-10 What2Do WBT
Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.
Hardware Overrun Error
Question:
I am using the serial extender, and am running into a periodic problem where I receive a Hardware Overrun Error.I know this is a pretty vague question, but can anyone provide some insight as to why this might happen?
- This the data that is returned when I set pCaptureOn
pcominfo("0#COM1","2") OK = 1
pgetbinary("0#COM1","1980488","3500") OK = 408
[ ***** HARDWARE OVERRUN ERROR ***** ]
pcominfo("0#COM1","2") OK = 0
Answer:
Basically the hardware overrun error is a result of data arriving at the serial port faster than Winbatch and the serial extender can offload it.This can indicate...
- Not using hardware handshaking.
You may be able to fix this. Maybe not
- Receive buffer is too small. I do not think this is the issue. The serial extender has a large receive buffer.
- Some other process is chewing up *all* the cpu time and the serial extender is not getting any time to move characters from the hardware to the receive buffer.
- Baud rate is too fast for the system to keep up with it. Use lower baud rate.
- The best bet is to investigate the handshaking. That is *supposed* so solve problems like this.
Article ID: W16860
File Created: 2007:07:03:14:26:38
Last Updated: 2007:07:03:14:26:38