Internal Error Retrieving Device Control
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| up vote 1 down vote Mscomm32.ocx is still fully supported by Microsoft. You could ask their support people to help. If you have an MSDN subscription, you may be entitled to free support incidents. Apologies if you'd already thought of that, I hope someone else can give you a direct solution. share|improve this answer answered Feb 20 '10 at 12:06 MarkJ 24.9k34878 add a comment| up vote 1 down vote I've got the same problem and that is why entered into this forum. After going deeper into the problem of communication getting lost, found the intermitence belongs to my USB-RS232 converter module. Mainly because it is working controling external ha
Community Support Report a Bug Developer Support Dealers Become a Dealer! Downloads HomeSeer Message Board > Legacy Software & Plug-ins > Legacy Plug-ins > Legacy 3rd Party Plug-ins > WAF-AB8SS (3P) Getting Error 8021 (Internal error retrieving device control block for the port) User Name Remember Me? Password Register Downloads FAQ Calendar Today's Posts Search WAF-AB8SS (3P) Discussions related to the WAB8SS speaker switcher 3rd party plug-in. Search Forums Show Threads Show Posts Tag Search Advanced Search Search Downloads Advanced Search Go to Page... Thread Tools Display Modes #1 September 6th, 2006, 07:30 PM MasterMog Seer Plus Join Date: Jul 2001 Location: Chattanooga, TN, USA Posts: 75 http://stackoverflow.com/questions/2299429/mscomm-serial-error-8021-internal-error-retrieving-device-control-block-for-the Getting Error 8021 (Internal error retrieving device control block for the port) When I first startup Homeseer the AB8SS runs fine but after about 30 minutes my log fills up with the following message and I have to shutdown and restart Homeseer: 9/6/2006 6:04:06 PM AB8SS Plug-in Diagnostic Error 8021 (Internal error retrieving device control block for the port) in procedure send_command_string of User Control hspi Any ideas what could be causing this problem? http://board.homeseer.com/showthread.php?t=115620 Thanks Mack MasterMog View Public Profile Find all posts by MasterMog #2 September 7th, 2006, 08:40 AM dkindred Seer Master Join Date: Sep 2001 Location: Kemptown, Maryland Posts: 877 Mack, This sounds as if it might be an issue with the COM port. Is it connected to a standard COM port? --David dkindred View Public Profile Visit dkindred's homepage! Find all posts by dkindred #3 September 8th, 2006, 08:49 PM MasterMog Seer Plus Join Date: Jul 2001 Location: Chattanooga, TN, USA Posts: 75 No, it was connected to a 4 port USB Serial Adapter as I don't have any standard serial ports available. I did try connecting to a standard port and the problem went away. I'm thinking that I need to purchase a different USB Serial Adapter. Do you know of a USB to Serial Adapter that people have had succcess running the AB8SS device? Thanks Mack MasterMog View Public Profile Find all posts by MasterMog #4 September 11th, 2006, 09:58 AM dkindred Seer Master Join Date: Sep 2001 Location: Kemptown, Maryland Posts: 877 Hi, Mack, I'm afraid I don't know which serial adapters are successful. The AB8SS has no buffer, so its timing needs are more critical than other serial devices. Anyone using an AB8SS with a USB seria
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit https://www.experts-exchange.com/questions/21404755/Run-Time-Error-'8021'-with-MSComm.html Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing https://autohotkey.com/board/topic/19080-serial-port-communication-using-mscomm-control/ Store Headlines Experts Exchange > Questions > Run-Time Error '8021' with MSComm Want to Advertise Here? Solved Run-Time Error '8021' with MSComm Posted on 2005-04-27 Visual Basic Classic 1 Verified Solution 8 Comments 4,641 Views Last Modified: 2013-12-25 Hi all, I currently am using two MSComm object to read from two serial ports. One is connected to a barcode internal error reader and the other to a weigh scale. After running for some time i recieve an Run-Time Error '8021' Internal error retrieving device control block for the port. I am not sure why i am getting it and can't seem to find any way to solve the problem. Has anyone run into this problem before? I will be happy to post sections of the source code if necessary. Thanks Much. 0 Question by:jbutterfieldAtDiamond Facebook Twitter internal error retrieving LinkedIn Google LVL 10 Best Solution byedwardiii Found some info here (http://www.tech-archive.net/Archive/VB/microsoft.public.vb.winapi.networks/2004-08/0035.html) that seems to indicate the problem you're having may be a result of the client PCs Go to Solution 7 Comments LVL 10 Overall: Level 10 Visual Basic Classic 9 Message Expert Comment by:edwardiii2005-04-27 Hi, jbutterfieldAtDiamond. Hopefully an Expert with experience will post a better answer, but possibly the direction at this URL is the way to go: http://www.mp3car.com/vbulletin/showpost.php?p=138304&postcount=82 E.g. set up an error trap to reset the comm port to your devices? 0 Message Author Comment by:jbutterfieldAtDiamond2005-04-27 Hi Edwardiii, Thanks for the idea but this really isn't an option for me becuase each time i close and reset, because of this error, i miss a box. This is an automated system and any missed packages can spell disaster. Of course i have error trapped the condition already but i would like to find a solution to this one.. i am def. stumped. I should mention that i the client pc is a Windows XP SP 2 with a SIIG PCI two port serial card and two NIC cards installed. One NIC is onboard, the other is a PCI card. The comptuer also has an onboard serial port we are not using. Justin. 0 LVL 10 Overall: Level 10 Visual Basic Classic 9 Message Ex
Community AutoHotkey Ask for Help View New Content Javascript Disabled Detected You currently have 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 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 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 one or more invalid communications parameters. comSetCommStateFailed = 8015; //Operation valid only when the port is open comPortNotOpen = 8018; //Error reading comm device comReadEr