Internal Error Retrieving Device Control Block For The Port
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up MSComm Serial Error 8021 “Internal error retrieving device control block for the port” up vote 0 down vote favorite Occasionally we get this error when communicating between my motion control software and a plasma cutting torch. What the serial link is being used for is a one time setup of cutting information before the cutting begins. I am using VB6 and MSComm for this. I know the port itself has lunched because after it occurs other serial comm software (diagnostics, etc) can't access the port either. I would like to understand what MSCOmm is doing when it received this error so I can find a better hardware solution. vb6 serial-port share|improve this question edited Oct 10 '12 at 19:55 dsolimano 6,11832746 asked Feb 19 '10 at 20:47 RS Conley 6,5811232 add a comment| 3 Answers 3 active oldest votes up vote 2 down vote accepted Try using a different OCX www.comm32.com has a control that mimics mscomm but has many improvements share|improve this answer answered Feb 25 '10 at 19:21 Ian 361 add a comment| Did you find this question interesting? Try our newsletter Sign up for our newsletter and get our top new questions delivered to your inbox (see an example). Subscribed! Success! Please click the link in the confirmation email to activate your subscription. up vote 1 down vote Mscomm32.ocx is still fully supported by Microsoft. You could ask their support people to help. If you ha
this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. Results 1 to 3 of 3 Thread: Trouble with MSCOMM..... Tweet Thread Tools Show Printable Version Subscribe to this Thread… Display Linear Mode Switch to Hybrid Mode Switch to Threaded http://stackoverflow.com/questions/2299429/mscomm-serial-error-8021-internal-error-retrieving-device-control-block-for-the Mode Jun 27th, 2012,12:06 AM #1 ezflyr View Profile View Forum Posts Thread Starter Member Join Date Jul 2010 Posts 32 Trouble with MSCOMM..... Hi All, I have a VB6 application that has been in use now for quite a number of years. This application uses the MSCOMM control to send/receive serial data to/from a piece of electronic http://www.vbforums.com/showthread.php?682741-Trouble-with-MSCOMM test equipment. The data transfer requirements are very modest (32 bytes of data received from the test equipment every few seconds max.) This has worked flawlessly for years until recently (the last year or so) when I began to receive reports of sporadic communications failures. The most recent report I got included the following error: "Error 8021: Internal Error Retrieving Device Control Block For the Port". I always advise trying a different computer, or a different COM port, and this always seems to resolve the situation. These reports are getting more frequent, however, and I'm looking for a more pro-active solution! The serial communication code in question has not changed in 10+ years, so I think I'm facing (1) COM port issues, or (2) OS issues. As we all know, serial ports are (mostly) going away, so users are resorting to PCI-to-serial and USB-to-Serial solutions when "native" serial ports cannot be found. Even the "native" COM ports don't seem to be as robust as they once were, and the external so
Community AutoHotkey Ask for Help View New Content Javascript Disabled Detected You currently have https://autohotkey.com/board/topic/19080-serial-port-communication-using-mscomm-control/ javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality. Serial port communication using MSComm control Started by Hardeep , Jul 03 2007 12:10 PM Please log in to reply 2 replies to this topic Hardeep Members 87 posts Last active: Sep internal error 12 2007 06:40 PM Joined: 02 Jul 2006 Can someone please help me in implementing serial port communication using the MSComm control (MSCOMM32.OCX). Going through CoHelper.ahk I couldn't understand how to use the various methods provided by an interface... :roll: I have provided below the TypeLib://Microsoft internal error retrieving Comm Control 6.0 //Version: 1.1 MSCommLib; GUID = {648A5603-2C6E-101B-82B6-000000000014}; //MS Comm Control Handshake Constants Enum HandshakingConstants; GUID = {4B4B0391-6897-11CF-953F-0020AFC28C3B}; //No handshaking NoHandshaking = 0; //XOn/XOff handshaking XonXoff = 1; //Request-to-send/clear-to-send handshaking. RtsCts = 2; //Request-to-send, XOn/XOff handshaking. XonXoffAndRtsCts = 3; //MS Comm Control Handshake Constants Enum HandshakeConstants; GUID = {72F05B40-B530-101B-82B6-000000000014}; //No handshaking comNone = 0; //XOn/XOff handshaking comXOnXoff = 1; //Request-to-send/clear-to-send handshaking. comRTS = 2; //Request-to-send, XOn/XOff handshaking. comRTSXOnXOff = 3; //Error Constants Enum ErrorConstants; GUID = {7C4FC790-BE64-11CF-95DA-0020AFC28C3B}; //Invalid property value comInvalidPropertyValue = 380; //Property is write-only comGetNotSupported = 394; //Property is read-only comSetNotSupported = 383; //Invalid port number comPortInvalid = 8002; //Port already open comPortAlreadyOpen = 8005; //Operation not valid while the port is opened comPortOpen = 8000; //The device is not open comNoOpen = 8012; //Could not set comm state, there may be on