Vision 0 Posted August 26, 2010 (edited) Hi, im usin NETCommOCX.NETComm for my COM scripts/tools works perfect for me but if i try to open a port what exsits but isnt connectet autoit will crash. here my code snip: ; >>STARTING NET COMM $NetComm = ObjCreate("NETCommOCX.NETComm") ; >>NET COMM SETTINGS With $NetComm .CommPort = $portsetting ;Port .Settings = "9600,N,8,1" ;Com Settings .InputLen = 0 ;reads entire buffer .InputMode = 0 ;reads in text mode .HandShaking = 1 ;uses both RTS and Xon/Xoff handshaking .PortOpen = "True" ;opens specified COM port EndWith so the line: .PortOpen = "True" ;opens specified COM port trys to open it but he cant and then autoit do a crit error exsample: im using bluetooth, so the Port is there but not active when the usb-stick isnt connected. when im trying to open the port autoit will crash (just logical cause he cant open the port) So is there a way to check the port if it is usable before he trys to open it? sorry for my bad english BR Vision Edited August 26, 2010 by Vision Share this post Link to post Share on other sites
DaleHohm 65 Posted August 26, 2010 Take a look at ObjEvent() that allows you to set up a COM error handler. This allows you to make COM errors non-fatal to your script... you can then trap them and decide for yourself what you want to do. Even though you are not using IE in your solution, a quick way to test this is by adding the following two lines to your code: #include <IE.au3> _IEErrorHandlerRegister() Dale Free Internet Tools: DebugBar, AutoIt IE Builder, HTTP UDF, MODIV2, IE Developer Toolbar, IEDocMon, Fiddler, HTML Validator, WGet, curlMSDN docs: InternetExplorer Object, Document Object, Overviews and Tutorials, DHTML Objects, DHTML Events, WinHttpRequest, XmlHttpRequest, Cross-Frame Scripting, Office object modelAutomate input type=file (Related)Alternative to _IECreateEmbedded? better: _IECreatePseudoEmbedded Better Better?IE.au3 issues with Vista - WorkaroundsSciTe Debug mode - it's magic: #AutoIt3Wrapper_run_debug_mode=Y Doesn't work needs to be ripped out of the troubleshooting lexicon. It means that what you tried did not produce the results you expected. It begs the questions 1) what did you try?, 2) what did you expect? and 3) what happened instead?Reproducer: a small (the smallest?) piece of stand-alone code that demonstrates your trouble Share this post Link to post Share on other sites
Vision 0 Posted August 27, 2010 thanks! i will try it, but looks good so far. Share this post Link to post Share on other sites