List of available com ports on Labview based on Vista

Hi,
Labview 8.5 on Vista is behaving different to the one on XP, in terms of showing a list of available COM ports on the drop down Port Resource name.
What is the actual reason and can it be rectified?

Can you post a couple of screen shots of what you mean?
(Preferably .png or .jpg files. Not .bmp's. And not screenshots embedded in a word document please.)
Message Edited by Ravens Fan on 03-09-2009 07:44 PM

Similar Messages

The UNIX tool that lists all available IP ports is called ...

(1) Sorry. I can't remember. What's the utility that will show you all the IP ports your ISP has open for use? I ran it a few days ago but can't seem to `apropos' it into existence.
(2) Also, is there another way to find out?
(3) I'm asking because every time I use eMule it I get assigned a "LOW-ID" which it says is "because you're behind a firewall or router."
Thanks.

Thanks, but I mean the utility that lists all the available PORT NUMBERS: like 25, 80, 8080, 4000, etc.
aMule is big on ports like: 4661, 4242, 6543, 4500, 4000, and 1111.
Anyone know the name of the app or utility that lists the open port-numbers?

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

Communicating via the Com port (comm)

Hi Folks,
I'm trying to communicate to the com port on my device but apparently can't "see" any available com ports.
Actually I'm trying to communicate via the Infrared port on my device and have been able to do so on a Nokia using COM0, however, on an Orange SPV, no ports are available. I'm using the Connector class from GCF.
I've used
System.getProperty("microedition.commports")
and on the Nokia get a load of ports back, however, on the other device I get back null. The device does have a IrDA port so I feel like I should be able to access it, I just don't know how.
I wondered if there is other ways to get hold of a port?
Reading http://developers.sun.com/mobility/midp/questions/properties/index.html it implies that the above property is implementation specific, does that mean Midlet Manager implementation specific (the SPV device uses Intent Java).
Thanks for any suggestions or any tips / links on IrDA / serial communication with ME :)
Cheers,
Toby

Start with the NI modbus library.
http://sine.ni.com/nips/cds/view/p/lang/en/nid/201711
Or download portmon and use it to watch the data as modscan is working. Then use VISA and serial port commands to transfer data bytes until it matches what modscan is transmitting. You'll learn more doing it this way.
Also download the modbus protocol pdf file.
http://forums.ni.com/ni/board/message?board.id=170&message.id=197677&query.id=96682#M197677
Message Edited by unclebump on 03-10-2008 06:04 PM

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.

Programatically Changing Com Ports

I need to programatically change the COM port within LabView.
I am writing a program for clients and need to save the COM port settings within an exicutable. I was going to atchieve this by writing to an ini file. I cannot directly save the VISA variable but can save the following properties.
Intf Inst Name
Intf Type
Intf Num
The problem is I cannot write to these properties on the initialization state of the program. Is there a way I can save which COM port was being used from one session to another of an exe? Thanks in advance for all your help.
Jesse

Hi Jesse,
you can store it as a string. If you read the string from a file you can directly connect it as a com port selection. It also works if you typecast the string to the com Port type.
Mike

Assign permissions to com port

I am trying to get help or information on assigning permissions for com ports. I am getting communication read errors on software that we use to read meters. The com port is correct in device manager and for the particular software. Communication is good,
as long as we are logged in as administrator. We have assigned admin rights to the software for the users, but it appears that the com port needs admin priviledges assigned. The software vendor recommended giving admin rights to the user over the entire machine.
I would only do that as a last resort. Does anyone know how to assign permissions on com ports?

Hi,
If you don’t want to grant the administrator privileges for your users, I suggest you distribute the software via Group Policy.
You may refer to: Permissions and rights have been removed from the Power Users group in Windows Vista
http://support.microsoft.com/kb/2028493
Also, if these COM ports are usb based, check the usb devices too.
As I known, it is not possible to access Advanced screen or Advanced settings without the administrator rights. This issue is more related to hardwre device drivers, you'd better follow the device manufacturer's instructions. I think, you may give admin
rights to the user over the entire machine as software vendor recommended.
Hope it helps.
Regards,
Blair Deng
Blair Deng
TechNet Community Support

How do I get LabVIEW to recognise a Gaussmeter as a device through COM port 1?

Hello everyone.
I am trying to do display the readings from a GM05 Gaussmeter in LabVIEW through COM Port 1 on my computer. I have installed the relevant drivers and MAX recognises that something is plugged in by listing COM 1, COM 2 and LPT 1 under devices, but it does not recognise the Gaussmeter as a device (it does not say 'device #' in brackets next to COM 1).. Therefore when I come to create a new Virtual Channel in the Data Neighbourhood I cannot select my COM port as a device. Can anyone help me to solve this problem, any advice would be greatly appreciated.
Regards,
Rob.

Unlike GPIB the com port or serial communication usually does not have an identify query, so it wont auto recognize the device. You should look in the manual of the device and send an appropriate string (there might be a self-test or identify string) and check for the correct response. Not all devices communicate both ways (some are talkers, some are listeners and many are both).
Paul
Paul Falkenstein
Coleman Technologies Inc.
CLA, CPI, AIA-Vision
Labview 4.0- 2013, RT, Vision, FPGA

VISA resource name control: want to refresh list of COM ports programatically

When the app is running, and you first click this control, it takes 2-5 seconds to respond and populate the list for the first time.
Therefore, I want to auto populate the first time the application is loaded. Can I do this?
Solved!
Go to Solution.

Hi,
I'm joining in here since the thread addresses delay problems when using VISA resources.
I would like to share my experience when using VISA on real-time targets.
The hardware I use is a cRIO NI-9074 with two NI-9870 (4 x RS232 each) and one NI-9871 (4 x RS485). These modules are used in scan mode to avoid excessive port programming in FPGA.
My first problem was that the twelve COM ports of the NI-9870/9871 modules did not show up in the list of available VISA resources when placing a VISA resource control on the front panel or a VISA resource constant on the block diagram. However, the workaround using "VISA Find Resources" seemed to work fine. When starting the real-time program from the development machine, the list was populated and by indexing the list I was able to use the port.
BUT: When building an RT executable from this VI, deploying it to the RT target and setting it as startup, nothing happened. It took me some time to find out, that there has to be a significant delay (in my case about 10 s) before calling the VISA Find Resources function. Otherwise it will not give the correct output. By some reasons, the ports do not seem to be available when the RT startup application begins to run. I tried to play with the delay and found out that the resource list would be empty when calling the VISA Find Resources function almost immediately on startup, after a few seconds it would return the ports of the first NI-9870, after seven seconds the ports of two modules, and after about ten seconds all ports would be available.
I would appreciate if somebody could tell me what happens since it was quite a pain in the ass to solve this issue.
Best regards,
Karsten

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

Why is my com port missing from my list of VISA devices

Hello all,
I have an Agilent E5810 ethernet to GPIB gateway. I installed Agilent IO library and chose to make Agilent my primary VISA because otherwise the devices on the gateway didn't show up in my VISA device list. Now all of my GPIB devices show up (local and via gateway) but my com port is missing. The com port is actually a USB to serial adapter. It shows up in device manager as CP2101 uart interface COM6. I reloaded NI-VISA but COM6 still oesn't show up. I reloaded Agilent IO and unchecked "make Agelent primary VISA" but that didn't fix it. It is also missing from MAX. I added COM6 ASRL6 but VISA doesn't see it
I think the root of my problem is getting Agilent VISA and NI VISA to work together but why won't my com port show up?
Thanks alot

Hello,
Can you please follow the steps outlined in the following forum post and reinstall NI-VISA and Agilent VISA?
Problem with NI VISA and Agilent VISA
If the problem still exists, please call 1-866-275-6964 and reference your call to your service request number (1194753).
Thank you,
Simran K
National Instruments
Applications Engineer

USB TO COM port drivers in LabVIEW..

Hi Everyone,
I have virtual com port equipment (hardware) from STmicroelectronics and i need to communicate it with LabVIEW through USB.
I have done with NI-VISA Wizard which i have gone through previous posts but am not able to communicate.
Can i get any drivers for this communication.
In MAX, i can see it as COM4, COM5 like that but i want it as USB.
Thanks,
Sony.
'' A professional is someone who can do his best work when he doesn't feel like it''...........

To expand on Sir Dennis' point, it is not uncommon for vendors with USB widgets to sell to implement the interface to them as virtual serial ports, and the reason is simple: Nearly any environment can talk to a serial port, and you don't need any special hardware. In addition, because it is a **virtuall** serial port you don't even have to worry about cables.
The point to remember is that when you plug in one of these devices you are in essence adding in both the device AND the port to talk to it.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

FTDI virtual com port driver (VCP) and Labview 2009 - random connection loss

Hi,
I am using an FTDI chip to go from USB to serial communication (FTDI Driver: 2.06.00). It seems to work at first but then after some time the connection gets lost ("connection for the given session has been lost" or "I/O error"). This happens in MAX as well as the built executable of the program I am running. Latest VISA drivers are installed - 4.6. I have tried flushing the buffer before and after communication with both visa clear and visa buffer flush vis. The lost connection seems to happen randomly.
I have seen other threads about this issue but they never reach a resolution. One thing i notice is that there are two FTDI devices in this system and only one fails, however when I unplug the working device the one that fails is able to connect again.
To sum up here are the system specs:
Windows XP SP3
FTDI 2.06.00 and older 2.04.02 drivers both fail.
2 FTDI devices on the system - they do get assigned different COM ports
Labview 2009 run-time
VISA 4.6 run-time
Thanks for any help.

We use Targus ACH63US Super Mini USB 2.0 4-Port Hub. It doesn't require external power but if you have a high power device you will have to plug the Targus hub into two usb ports on your pc (one provides power and the other does power and data transfer). They provide the usb Y cable to do this.

VISA unable to communicate with or see RS232 serial com port

I have a Dell Optiplex GX260 which has recently had Windows XP (Service Pack 2) re-installed on it. National Instruments VISA is unable to communicate with the single RS232 serial com port on the computer. Neither the "VISA Resource Name" control in LabVIEW 8.5 nor the "Measurement and Automation Explorer" can see the serial port. Refreshing the list does not help. "HyperTerminal"is able to both see and communicate with instruments connected to the serial port. In Windows "Device Manager, the serialport appear in the list of hardware without any warnings.
Can anyone please help with suggestions as to how I may be able to get VISA in LabVIEW to 8.5 to see and communicate with the serial port?
System Details:
Dell Optiplex GX260 (One RS232 serial port)
Windows XP Home Edition Service Pack 2
LabVIEW 8.5
Solved!
Go to Solution.

AKA_TG wrote:
Just passing by but I gotta say
Guyts who answer like that do really irritate me
Someone oughta apologize to the porr guy trying to get some help here.
Go ahead and put me on your ignore list please!
First, there is a plethora of messages on this forum and a plethora of information in the NI KnowledgeBase. If someone doesn't make the simple effort to take 5 minutes to perform a search what does that say? The issue being raised has come up, literally, dozens of times. Do you like answering the same question over and over and over and over and over again?
Second, my feelings are not unique. You will find that the irritation of people not bothering to do a simple search is shared by most of the regulars here. Why do you think search engines are available? Just so that ads can be sold?
Third, posting the SAME question in multiple threads is self-defeating. People who try to answer don't know what's already been suggested, and end up wasting their time as well as the poster's time in providing the SAME answer and/or suggestions that were provided in the other thread.
Fourth, simple forum netiquette. In both threads the poster essentially hijacked someone else's thread. This is frowned upon in just about every forum that I've ever seen.

How to use shared variables to address multiple Watlow controllers on the same COM port

Hello,
I am trying to use LabVIEW 2010 to control 4 Watlow temperature controllers on one COM port. 3 are Model 96 and 1 is an EZ zone controller. Each controller has a unique modbus address, and I am trying to read from and write to individual registers (such as closed loop setpoint) using shared variables. I am getting return data when reading (although the data appears to be invalid), but am unable to change the value in the register by writing. How can I be sure that the Modbus server is sending commands to the correct controller?
Chuck
Solved!
Go to Solution.

Peter,
Thanks for the reply. I have actually solved that problem. I realized that the Modbus server address has to be the same as the controller's Modbus address.
I have, however, run into another problem. Perhaps you could help me with that. I have a system with 4 Watlow controllers, 3 are series 96 controllers, one is PID only and 2 are ramping. The 4th controller is an EZ zone. I am using RS485 for communications and the controllers are all wired in parallel for communications and power.
I have set up 2 Modbus servers for 2 of the controllers.
This is the first I have ever worked with Modbus based communications. I have successfully programmed using the Modbus read/write VIs, and am wanting to move to shared variables. My questions right now revolve around addressing, Modbus I/O servers and COM ports. Specifically, at this point, I know the addresses need to match up between the server and the slave device (Watlow controller in my case), how many servers can I create and use on one COM port? If the number is limited, is there a way I can specify an address that I want the server to talk to? Will the broadcast mode work to request data values from the controllers?
I'd appreciate any information you can help me with, or if you could point me to some sort of concise 'How-To' for Modbus communication.
Thanks.
Chuck

List of available com ports on Labview based on Vista

Similar Messages

Maybe you are looking for