Exe com port error

Hello,
I am writing a program to pick com ports for the main program. The com ports are actually USB devices and I want them to be able to choose different ports if they happen to change because of the USB. So I wrote the program to populate a menu ring with the names of available com ports. Everything works fine as a vi, but when I built it as an exe the property node throws errors. I am running the exe on the same machine as my vi for testing.
# -1073807246
Property Node (arg 1) in pick comports.vi.
The property node is : Property:Interface Information:Interface Description
Using this as a VI it puts out names similar to what you would see in the windows device manager. The false case just puts the words "Not Used". The input is an array of Visa references for COM1 - COM10.
Any ideas on why it breaks in an EXE?
Solved!
Go to Solution.
Attachments:
error.png ‏6 KB

_Bryan wrote:
It would be nice if the search engine would have pulled up that page you linked to.
It does if you don't search in the forums only, but on the NI Website. The website search includes the forums, so it's usually a better place to start, especially if you have an error code/message then it might find some KB articles or similar in addition to forum posts.

Similar Messages

Not enough memory error when disconnecting device on a virtual com port

I maintain a large application that collects data from many data source channels (using coustom hardware read thru a conventional COM port) and I am adding a GPS data source on a USB port using a virtual COM port driver. The application runs 24/7/365 and works well including the GPS data, if undisturbed. However, the application needs to tolerate a physical disconnect and reconnect of the GPS device without user intervention. When I disconnect the GPS, the application becomes unresponsive most of the time (the mouse responds and other programs that are open on the desktop work fine). I abstracted the serial code and made a separate vi (below) for testing. When I disconnect the GPS from the COM port, I get a "Not enough memory to complete this operation" message 9 out of 10 times and the vi is unresponsive until I clear the error message (the tenth time it continues working). I built the vi this way to collect data continuously. I suspect that this is the problem with the full app but I don't see the Not enough memory message there and therefore the full app does not respond and must be terminated via Task Manager. The full app runs full screen mode.
The LV app runs on Windows XP and LabView 7.0 (the client doesn't want to upgrade).
I have tried probing the error message lines at all points in the vi but they don't show anything when the 'Not enough memory' message occurs (they show the expected device not found error after clearing the error message).
Any suggestions would be greatly appreciated,
Mel
Still learning LV......
Please post any code suggestions as graphics as I don't have access to any version of LabView newer than 7.0.
Attachments:
SerialPortRead.png ‏22 KB

Jeff·Þ·Bohrer wrote:
First, there likley WAS human intervention that caused the GPS device to be removed. That wont happen when you lock the device inside a cabinet with the rest of the test system. Physical access control first! If someone goes and mucks with your experiment setup while its running, that's a "poor Labratory procedure" not a "new software requirement"
I think he was meaning to say without user intervention on the software side.
I have seen odd behavior if you disconnect from a com port whilst LV still has the port open. There are a couple things I myself woud try, being the experimenting type that I am. Perhaps setting up a com port check to see if it has a valid connection before polling for data. If not then a blank case or some other generic code.
The issue with this would be if it became disconnected while LV was polling data. Hard to get around this condition. Is there a way that the cause of the of the connect/disconnect (whether human or otherwise) could be set up so that a signal can be sent to the controlling system (pre-disconnect and post-connect) to trigger an event to handle the software side? A simple signal switch or something. Just thinking out loud. Withoug knowing all the particulars, it's hard to make detailed recommendations.
Doug
"My only wish is that I am capable of learning each and every day until my last breath."

I/O error with COM port

I have a RS485 line going into COM5 of my PC. Using HyperTerminal, I can talk to my serial device. However, there are problems with LabVIEW VISA functions. I can open the connection. I/O errors were given when I try to read or write. Is this because LabVIEW does not support RS485? What can cause the I/O error? Thanks.

Some tips,
First off, computer com ports are only RS-232. Make sure you are using the RS-232 port on the
ADAM-4570. Do you have to configure this port as RS-232 with Advantech software? If the ADAM is
configured as RS-485, you won't be able to talk to it without an RS-232 to RS-485 converter. Stick
with RS-232.
Secondly, make sure you have shut down all other software that is using COM5. Only one application
can use the port at a time and sometimes other applications don't release the port properly.
If HyperTerminal can talk to the ADAM, then everything is configured properly for a LabVIEW app. Be
sure to put a carriage return at the end of the command to the ADAM. HyperTerm does this
automatically, LabVIEW doesn't. Start with the basi
c commands you used with HyperTerminal.
"sy" wrote in message news:[email protected]..
> Good question. In fact, I think the problem stems from how COM5 is
> mapped to my PC. As for the second question, I got the same I/O error
> when using MAX. I believe that there is a conflict between NI
> software and the software I use to map the RS485 line to COM5.
>
> I am using Advantech's ADAM 4570 module to convert a RS485 line to
> ethernet. The ethernet cable goes into the PC. A software utility is
> used to map the ethernet connection to COM5. It is conflict between
> this utility and NI. Any idea on how to resolve the conflict? Thank
> you.

GPS Error on F3507g & Windows 7 "The GPS NMEA COM Port is not available" x200

I have an X200 with a WWAN Card 43R153 (Ericsson F3507g) running Window 7.
The WWAN reliably connects to Vodafone but I can't get the GPS to work.
Device manager shows this port Enabled:-
Ericsson E3507G Mobile Broadband MiniCard GPS Port (Com8)
Driver Invogps.sys from Ericsson AB, Version 1.0.0.28 29/09/2008.
Thinkvantage GPS version 2.50 is also installed and Lenovo System Update says everything is up to date.
When I "Turn on GPS" or run 'Lenovs GPS" I get this message:-
The GPS NMEA COM port is not available. You need to check the following things.
- Another GPS application is using the COM port.
- COM ports is disabled. You can enable the COM port in the Device Manager.
Location and Other Sensors shows nothing installed.
I've tried deleting all the drivers and reinstalling but not luck.
Has anyone else had the same problem and found a solution. I can't think of anything else to try.
ThinkPad X200 7459-1P0

If you are running a Windows 7 Weather Gadget on your desktop, try shutting it down entirely and see if that changes your GPS "in use" problem.
Cheers,
Bill
I don't work for Lenovo

Error connecting to COM port

Hi everybody!
I have create the application use Labview 2009. My application connect to COM port. It is very good on my computer that installed Labview 2009. When I create Installer, I add NI Measurement & Automation Explorer 4.6 in Addtional Installer Item. But when I install application on other computer that dont install Labview, it don't recognized COM port. I check MAX 4.6 on this computer, it don't show Devices and interface.
Please help me!
Thanks!

Hi
Did you add NI VISA to your installer?
Kudos are welcome

NImax.exe has generated errors. You must restart the program, a log file is being created.

NImax.exe has generated errors. You must restart the program, a log file is
being created.
This error occurs just after bootup, no programs started except windows..
Running Windows 2000 latest version on a brand new computer.
(pent 4 3.0 ghz 500MB ram).
Can anyone help me with this problem? Happened after install Labview 7.0
express. Installed twice and same problem occured with both installs.
Labview 7.0 is the only thing installed right now. Also selected "Visual
Basic Support" install from driver cd's.
One other thing I just noticed. System info reports 2 processors and I
think I only have one.
TIA

Happy update.
After ignoring this problem for awhile and installing some NI DAQ boards,
this problem is not happening anymore.
Would urge NI to investigate further though. Messed me up for a couple of
days, and still don't know why it happened.
Much thanks to those who helped.
JJ
"JJF" wrote in message
news:qB6Hb.48702$VB2.90660@attbi_s51...
> One other point, I found out this is a message generated by drwtsn32. Can
> get rid of the error by unchecking "show visual feedback on errors" box,
but
> don't like that fix. Still need help.
>
> Thanks,
>
> JJ
>
> "JJF" wrote in message
> news:%JRGb.138921$8y1.419649@attbi_s52...
> > Hi Nirmal and all,
> >
> > Happy Holidays to you too, and thanks for the reply.
> >
> > Making progress. Did all the uninstalling and registry editing as you
> > suggested. Also, updated Win2K at Microsoft.com as suggested.
> > Re-installed with default settings of LV express 7.0. Now I only get
> the
> > error when I exit NImax.
> >
> > Also, my p2p home network is not that hot. Have it set up as a
workgroup.
> > Sometimes when I boot up I have file access between the two computers
and
> > sometimes windows explorer can't find the workgroup network path
(between
> > the two computers). Both computers can always access the internet
though.
> > Using a 4 port Linksys cable/dsl router on a cable modem. Using XP
home
> > edition on base computer (the one set up for the isp) and Win2K on the
> other
> > computer.
> >
> > Also, any idea where this log file is going? Thought it was part of the
> > event viewer but the errors in the event viewer don't seem to correspond
> to
> > the NImax.exe logging event now. There is a file in
> > "winnt\sytem32\config\software.log" that seems to change at about the
same
> > time but I can't access the file because it is in use by the system.
> >
> > Using NImax ver 3.02.3005. Do you know if I can download "NI
measurement
> > and automation explorer" and/or the driver cd's from NI.com? Maybe I
have
> a
> > flaky disk or something. I have a feeling it may also have to do with
the
> > "on again/off again" network neighborhood connection problem.
> >
> >
> > Thanks again,
> >
> > JJ
> >
> >
> >
> > "Nirmal Sharma" wrote in message
> > news:506500000005000000AE470100-1068850981000@exchange.ni.com...
> > > Hi,
> > > Happy cristmas & new year for you & ur brand new pc...
> > >
> > > How are you uninstalling & then installing LV in your pc ?
> > >
> > > I suggest to remove complete LV (Remove All option) from your
> > > computer. Once uninstallation is completed, go to windows registry -
> > > by windows start -> run -> regedit -> Enter
> > >
> > > Goto HKEY_LOCAL_MACHINE-> SOFTWARE -> National Instruments - Delete
> > > this folder (National Instruments folder)
> > >
> > > Remove any other foloder/file related to NI's software. Be very
> > > cautious while deleting files from windows registry bcoz wrong file
> > > deletion may hang your whole system.
> > >
> > > Restart your computer..hope it should bootup without any errors.
> > >
> > > Now as answered by Alexander, update windows.
> > >
> > > After updating, bootup your system. If it boots up without any error
> > > message, install LV with the typical (default installation).
> > >
> > > Hope this helps. Your feedbacks are welcome.
> > >
> > > Best Regards,
> > > Nirmal Sharma
> > > India
> >
> >
>
>

Com ports dont work on all machines, what could be causing this?

So I completed my app and built the exe and installer and everything works fine on my PC and a PC in the lab. Then I tried to install it on a another system in the lab and neither (I use 2) com ports work. Figuring it must be the HW I tested both in Hyperterminal and they work fine. I tried closing all applications and also rebooting the PC and it still won't work. The error occurs on the com port initialization step.
What could be so different on this system that it works on all others but not this particular one? Has anyone encountered this before?
Thanks,
Dave
LV 8.2, my PC is XP and the 2 lab PCs are windows 2000, only one of which seems to work.

Centerbolt is right. I had the same problem but it went away when I included the VISA runtime while creating the installer.
Message Edited by S G on 12-07-2007 12:21 PM
S G
Certified LabVIEW Architect, Certified TestStand Developer, Certified Professional Instructor

HyperTerminal sees a COM port but VISA does not

It should not be possible that HyperTerminal sees a COM port but VISA does not. Does anyone know why or have any ideas?
Here's some more info: I wrote a LabView (LV) program and deployed it (via the Application Builder) to some of our production department's PCs (some Windows XP and some Windows 7). We use it to set up products we design and manufacture through our device's USB serial port. The USB port is actually a virtual COM port (VCP) - a USB to Serial converter or "bridge". We have a custom driver for our device and since each device's USB bridge chip is programmed with a different serial number, every time we connect a new device to the PC the installer runs and assigns a new COM port number. This is so our customers can use multiple devices on a PC. Fine. On one of our production PC's we were close to COM900 ports (HyperTerminal sees only up to COM256) when suddenly Win7 would not allow any more. We were able to uninstall orphaned (non-present) COM ports from DeviceManager ("DM") by starting it from a command console (DOS window) with a special command-line switch, "set devmgr_show_nonpresent_devices=1" then "start devmgmt.msc" (I have this in a batch file). In DM View menu you can "Show hidden devices" and uninstall them as if they were connected. I've also tried uninstalling them the normal way when the device was actually connected. Either way, sometimes, not always, depending on the COM port number, after reusing that port number by installing a new device which picks up that old, freed-up number, LV VISA doesn't see it. In other words, when "Refresh" is clicked in the COM port VISA list box, any new devices installed should be and normally are seen. (Refresh is not needed if the application is started after the device's driver is installed. It is only need if the LV application is open with the new device is added.) However, HyperTerminal does see it and lists it in the Properties screen, the "Connect using..." list box. And the port works with HyperTerminal. (Of course we've tried rebooting after uninstalling and/or reinstalling the device, with the same results.)
When I've spoken to the NI Applications Engineers in the past about serial port issues (not about this problem) they have confirmed that if HyperTerminal can see the port then NI VISA should also see it. This is crazy. I am posting this in hope that someone can shed some light on this problem.
Thank you. -Ed

Good catch. Yes, we're using the Silicon Labs CP2102 and have created a "custom driver" installation package. Our new PCBs have a factory-programmed chip, so the PC reuses that COM port (COM3 on that PC). The problem is when we we re-program the CP2102 (setIDs exe) with our PID, and device strings (including the S/N), the PC runs our installer and assigns the next COM port number. I was hoping that maybe it would go up to 64K or something! Anyway, it surpassed COM256 but we ran into this problem when almost up to COM900.)
There is a registry entry for each SN device, which shows the assigned port. If we delete the key with regedit, the COM port database (don't know the file name) still has the port number. That's where Device Manager comes in. It seems to allow us to manually delete the ports, but it would take quite a while to delete 900. (I was trying to make a batch file for DevCon, but couldn't get it to see the HW ID of the devices in need of deletion.) So we tried manually deleting a few. After doing that Device Manager shows that Windows (and HyperTerminal) can reuse the port number when a new device (new SN) is installed, but, as you know from this post, VISA cannot see unless I manually add it in MAX.
I can't see how it has anything to do with the Silicon Labs driver. I might have to delete ALL of MY devices, then uninstall the driver files, reboot, then reinstall, as you suggested with the SiLabs driver. However, I don't see how VISA will now see these changes. VISA must have it's own database. That's what I thought deleting the ports in MAX would clear out, like a fresh install, but apparently not.
I've been through Silicon Labs' tech support on other issues and they've been able to help on some. I could run this by them.
BTW, have you noticed that Silicon Labs' chip and driver, while faster than NI's own "bridge" or serial-USB converter (I returned it because at $100 it's performance was worse than a $20 converter you can buy in Staples), is substantially slower than a real serial port? For example, our device can transmit 250 readings per second (a 12 byte string). A real serial port used with my LabView program can keep up, i.e.., graph & tabulate at that rate, but with a VCP we only get about 70 RPS. Same code. Can't figure this one out. They say the've tested the driver to 900 KB claimed. We're using 115KB here. Anyway, the VCP driver makes it look like a COM port which LV thinks it is. Why is it slower than a real port when the USB should be able to work almost 10 times faster than I'm using it (up to 1024 bytes per mSec per the full-speed USB spec, which SiLabs claims they verified)?
Anyway, I appreciate your help. Thanks! -Ed

Problem removing bluetooth stack / hidden devices / COM ports not released

Hi
Having problem completely removing Toshiba Bluetooth stack / hidden devices / com ports not released
I uninstalled Toshiba BT s/w...
But:
1) Toshiba BT hidden devices still appear and I can not remove (get error)
2) COM ports occupied by Toshiba BT not released (so they cannot be used by another BT stack) and still appear in registry
ex: friendly name Toshiba BT Port (COM4) still in registry
3) These unreleased com ports do NOT appear in device manager
Thanks

It seems that you still have some configurations which were not removed during the uninstallation.
This means that the resources can not be release, because those are still necessary in case of a
new installation of the stack.
The first I would try is the following:
- Install the latest Toshiba Bluetooth stack.
- Uninstall it. Ensure that you answer all questions with "yes" ! This means also the one which asks if all configurations should be removed.
- Reboot
- Check again

Unable to create the bluetooth virtual COM port

Hi all
I install BS from Toshiba and it seems ok. Bt ir desn´t work. I see all the drivers installed, system devices, etc. No Toshiba BT ports can be seen. Local com ports only show modem port. Try to create a virtual port but get a message "unable to create a bluetooh virtual port" I have a satellite m100-145. Can anyone help on this ?
thx

Thx for your suport.
I decide to reinstall windows and all software. Now it works.
The error was due to the fact that if you have BS from Microsoft (called bluetooth monitor) and you install the BS from Toshiba after that, even if you remove the BS from MS, the BS from Tos is unable to create the virtual com ports (except modem).
I try with the latest version of BS and the problem was not solved. So if there is a previous installation of BS fom MS the BS from Tos get the message of "unable to create the bluetooth virtual com port".
Now i fixed reinstalling SO from beginning.

Satellite A300-1BZ with Vista - Com Port has disappeared

Hi everyone.
My first time and I'm a bit of a duffer with technical stuff, so please be gentle with me!
A300-1BZ with Vista.
A while ago I installed 'CarSoft V.83' (Engine diagnosis) from CD onto my laptop. It asked me to verify the com-port.
I looked in the device manager and in the list I saw 'com-port 4'. Ok, we'll go with that then. Everything worked fine and I was happily talking away to my car.
Yesterday I went to use it for the second time and it said there was an error with the com-port and to 'verify' the com-port.
So, I got the device manager back up and there is no mention of any com-ports in the list! It was there the last time I looked and now it's vanished!
I was at a loss what to do so, I uninstalled the CarSoft and then re-intsalled it again. Got the same error message.
Went to device manager. Still no com-port 4 in the list, or anything that relates to a com-port.
I don't know how or if I can get it back.
Please help!

Hi mate
First of all there are no com ports. The com port which you could see in device manager was an virtual port created by car software.
What to say
I recommend removing the car software from the system firstly.
Then download the CCleaner and clean the system and registry entries.
Reboot the notebook and run the CCleaner again
After that install the car software again
Maybe it helps

Logical port error (WS_LOGICAL_PORT) when consuming WS in PI

Hi All,
I am trying to integrate simple Currency Conversion Web Service witm my ECC program.
Program displays two fields in the selection screen (Currency From and Currency To)
WS is: http://www.webservicex.com/ws/WSDetails.aspx?WSID=10&CATID=2
The scenario is as below:
Proxy (Z-PROGRAM ) <-sync-> PI <-sync-> WS (Currency Convertor)
Looks like ABAP Proxy is done ok.
PI configuration also looks ok as I am trying it in IB's Test Configuration tool - all steps are 'Green / Passed'
Based on WSDL 3 interfaces were generated:
CurrencyConvertorHttpPost
CurrencyConvertorHttpGet
CurrencyConvertorSoap
I am using Soap one... along with WS Communication Channel
CC has configuren itself based on WSDL likn provided,
Technical Transport Settings were set to:
Target Host:               www.webservicex.net
Service Name / Port:     -1
URL Access Path:          /CurrencyConvertor.asmx
Transport Binding:          SOAP 1.1 Using HTTP
Why am I getting logical port error?
Error while determining logical port Cannot find logical port for agreement EAC1E5CF03FD3B2C827ADDECA2EA6B26 and interface urn:webservicex:com:test:currencyrates.CurrencyConvertorSoap
I searched the web for error message and I found obsolete logical port configuration using LPCONFIG, and also some 'new' approach with SOAMANAGER LogPort configuraton
(When I try to do this as suggested in [document |http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b04408cc-f10e-2c10-b5b7-af11026b2393?QuickLink=index&overridelayout=true]
then I cannot see my newly created services on the list)
... but is this the right track to follow?
Should I run Logical Port configuration in PI?
I would appreciate your comments on this.
Regards,
bob.

Hello,
Why am I getting logical port error?
Error while determining logical port Cannot find logical port for agreement EAC1E5CF03FD3B2C827ADDECA2EA6B26 and interface urn:webservicex:com:test:currencyrates.CurrencyConvertorSoap
WS Adapter is used for those that are using WS-RM (Webservice-Reliable Messaging)...See this blog
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/b00bbb77-75bc-2a10-6b9a-a6f8161515a6, but I think for now this is limited to SAP-to-SAP connections. That is why in your error it is searching for a logical port (ABAP Proxy).
You should be using the SOAP Receiver Adapter instead.
Hope this helps,
Mark

Cannot open com port

Hi all,
maybe not entirely sure if this is a labview question, but i was using labview when it happened. I am using labview to open and run a batch file using a COM connection and an FTDI RS232 to USB. Now i believe that portion of the code runs smoothly, ive tested it out and it worked at one point. After using an instr property node to check if port is open, which i now know cant be used on non ni devices anyways, it will not open to run the batch file. I have run it from command prompt and i get a communcation port cant be open error. Now i moved one of these devices from COM16 to COM2 and it works perfectly now, but the other one wont work at all and why should i have to change port numbers? any tips or troubleshooting advice?

Just in case anyone out there runs into the same problem, i followed this link here, uninstalled all com ports, then reinstalled com ports and is now functioning properly. But it seems that my port 18 which was not working before is still not working.
http://theitbros.com/how-to-delete-com-ports-in-use/

AT commands and Com port

Connection to the com port is ok and i can send AT commands.
But i need to make a few AT commands one after another. And i think i am getting errors..anyone can help?
                    outputStream.write("AT+CMGF=0\r".getBytes());
                    outputStream.write("AT+CMGS=153\r".getBytes());
                    outputStream.write(commandString1.getBytes());
                    outputStream.write("\u001a\r".getBytes()); // ctrl + Z
                    outputStream.write("AT+CMGS=153\r".getBytes());
                    outputStream.write(commandString2.getBytes());
                    outputStream.write("\u001a\r".getBytes());
as u see there are 2 "at+cmgs=153" i guess this is where the problem lies...

You must wait for the replies. I've not done this in java, but I have in VC++ and I remember that the Hayes AT commands are reversing half duplex. When you send a command read the incoming data until you see a carriage return.

VISA "Find" not seeing COM port but Win7 sees it

Allo. I'm trying to communicate via virtual com ports with a device with an FTDI chip. The device with the FTDI chip has both a USB type B port as well as a 9 pin dsub port, and I need to verify both ports work.
I'm using a laptop with Windows 7 and my program is in LV 2010. I have a Sabrent USB to serial cable to test the dsub port, and a standard USB cable to test the other port. I've installed the latest FTDI drivers and when I plug in both cables and look under Windows Device Manager, I will see both of them under unique COM port settings (usually COM4 and COM 5). So Windows sees and recognizes both virtual COM ports, and no yellow warnings.
However when I run the "VISA Find" function in LabView, it only sees COM5 (the Sabrent serial cable) but not the COM port using the USB type B cable. I send the results of the "VISA find" to a display and it will show other ports, like the parallel port, so I know it's seeing more than one port.
Any ideas why Windows can see the two COM ports but the "VISA Find" function can only see one? My guess is there's something with the FTDI driver set up.
Amateur programmer for over 10 years!

Yes, but its not for the faint of heart!
You can probably do what you want by using the refresh "F5" in MAX or add this token
[VISA-CONFIG]
ShowRegisteredDevOnly = 0
to C:\ProgramData\National Instruments\NIvisa\visaconfig.ini
Another thing to try is to recover the unused COM Port numbers each time you change the device. By default Windows will "Save" those previously connected COM port numbers an if it sees the device again it will re-assign the old number. This means that the COM number keeps getting larger and larger. At some point the PC's BIOS will say that's rediculous and you will experience trouble.
Programatically you could call
C:\Program Files\National Instruments\NI-Serial\NiPortConfig.exe to launch the same utility. there is probably even and unpublished switch to click just that one big button for you but I can't find it.
It looks like you may be running into some part of this known issue
Jeff

Exe com port error

Similar Messages

Maybe you are looking for