Serial Port of Microsoft

Hello,
I have a program in LabVIEW which read from the serial Port.
I would like to know the name of the memory where is saved the information from the serial port in the Operating System of Microsoft and where LabVIEW reads the information.
I would be very glad if somebody could help me in this topic.
Ramon

Ramon,
you are on the wrong track here. This is completely hidden to the end user and/or application programs. This is necessary, because in multitasking OS it would take much too long for application programs to react to direct HW interrupts as they are used in serial communication. Long words meaning is: Let LabVIEW handle all this stuff. Just open the serial port, configure it, send some text to it and/or read strings from it. Close the port when you are done. Its that simple in first hand!
It might become more complicated when communication protocols and protocol error handling comes into play, but this is beyond you actual Q.
Hope this helps!
Greetings from Germany!
Uwe

Similar Messages

Connecting direct to serial port

Hi to all!!
I need to connect flash direct to serial port to send and
receive data.
I know that i have to look for some API, but all that i fund
is some other software to do the interface, but i realy need is
distribut only the flash and not the flash and other software...
There is a way to connect direct to serial com?
If yes, how it works, were can i found information to do
this??
Tanks in advance!
Regards from, Portugal

Yes, PCSuite supports a great deal of Bluetooth drivers. These are all built in so, give it a try.
Windows Vista x32 en x64 editions:
Microsoft Windows Bluetooth stack
Toshiba Bluetooth stack, driver versie 5.10.12
IVT BlueSoleil Bluetooth stack, driver versie 5.0.5
Windows XP x64:
Microsoft Windows Bluetooth stack
Toshiba Bluetooth stack, driver versie 5.10.12
IVT BlueSoleil Bluetooth stack, driver versie 5.0.5
Windows XP:
Microsoft Windows Bluetooth (enkel in Service Pack 2)
Toshiba Bluetooth stack, driver versie 4.0, 5.0 and 5.10.12
WIDCOMM Bluetooth stack, driver versie 1.4.2, 3.x, 4.x and 5.x
IVT BlueSoleil Bluetooth stack, driver versie 2.x, 3.x and 5.0.5
‡Thank you for hitting the Blue/Green Star button‡
N8-00 RM 596 V:111.030.0609; E71-1(05) RM 346 V: 500.21.009

Serial Ports using HyperV in Ubuntu guest OS

I need to run a terminal session (term) from within the guest OS, Ubuntu 12.04.3 LTS to a serial port on the Windows 8.1P host. In my case a USB to serial adapter that Windows has mapped to COM5.
I don't really know where to start.  In HyperV, under Settings, I see a Com1 and Com2 under hardware. The two options are None or Named pipe. Not all that clear what to do here.
Presumably this is what will be visible to Ubuntu as /dev/ttyXX   ??
Can anyone point the way to map a serial port into Ubuntu?   Or a suitable workaround?
Thanks.

"How can a VM be so cut off from the hardware like that?"
Well, for the most part, it's been a long time since I have even seen a machine with a serial port on it. It is so uncommon that one generally needs to buy an add-on card or do something like USB to serial. That trend has been going on for a
long time - that's why network based serial devices have tended to the solution for this. This is nothing new. Even Microsoft's Virtual Server, the precursor to Hyper-V (which was released five years ago) did not have access to serial ports.
Since you are asking in the Hyper-V forum, the answer is you can't get to a physical serial port on your host.
.:|:.:|:. tim

Assistance in How to Communicate to Serial Port

Hello, I am designing an Interface to communicate with RFID Device. My problem is that I cannot seem to get the data sent to loop back and be displayed back to a textbox that I have setup. The serial port pins 2 and 3 have been connected with jumper
wire so as to allow the data to transmit and return back. I have followed the example from an online source called "Simple Serial". Yet, everything seems to work except for the data return (received). Any assistance on the matter would be greatly
appreciated. My apologies, I neglected to mention that I am using C# 5.0 in Visual Studio 2013 Ultimate.

Hi,
Your issue is out of support range of VS General Question forum which mainly discusses the usage issue of Visual Studio IDE such as
WPF & SL designer, Visual Studio Guidance Automation Toolkit, Developer Documentation and Help System
and Visual Studio Editor.
Because your issue is about Serial Port, you can consult on ,Net Compact Framework forum like this thread:
https://social.msdn.microsoft.com/Forums/en-US/59db36ee-88dc-436a-9222-bb0b7f9acbeb/serial-port-communication-using-cnet?forum=netfxcompact for better support.
Thanks,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

HP Mini - Is there a serial port?

On the HP Mini 110-1030NR, I need to use software that communicates through a serial port but the Mini does not show any serial ports. Is there any way to enable the serial port? I have looked in the BIOS and the Advanced section is not listed which is where the HP website support says to go to enable serial ports. Am I out of luck?
Thanks-

HI,
DaleWA wrote:
Sorry I mixed too many issues in the last message.
I think the simpler question is: Can I use a USB to serial adapter with the HP Mini 110-1030NR?
If so, how do I get it to work? I have installed the driver that came with the adapter. I know the adapter worked on an old Dell laptop. So, the issue must be the HP.
Do you still have the manual that came with the adapter?
Does the device show up in Device manager?
which OS is installed on your mini?
look under Device Manager of the System Properties screen. (Go there by Start-Setting-Control Panel-System Properties-Hardware-Device Manager-Select View-Device by connection).
The device should have installed as a “USB Serial Port (COMx)” attached to “USB High Speed Serial Converter”.
Change COM Port Properties & COM Port Number
This feature is particularly useful for programs, such as HyperTerminal, which only work with COM1 through COM4. Please ensure that you do not change the COM Port Number already in use.
To change the virtual COM port properties:
Select the “USB Serial Port”
Click “Properties”
Select “Port Setting”
Select “Advanced”
Click the drop down arrow on COM Port Number and scroll to the required COM port.
Select “OK”
Return to the Device Manager Screen. You will see that the USB Serial Port installation has been changed to the new COM Port Number.
Best regards,
erico
****Please click on Accept As Solution if a suggestion solves your problem. It helps others facing the same problem to find a solution easily****
2015 Microsoft MVP - Windows Experience Consumer

Windows Kernel Debbuging: Debug over virtual serial port with WDK 8.1

I'm currently having some issues doing kernel debugging of a Windows 7 x64 target from my Windows 8.1 x64 host machine. I'm running Visual Studio 2013 with WDK 8.1 on my host and have provisioned my target machine running in VMWare.
Here are my configurations for the target machine. It was configured by reading mostly from here - http://www.codeproject.com/Tips/545835/Kernel-Mode-Debugging-in-a-VM-using-Visual-Studio :
    Windows 7 x64
    Serial port COM2 with VMWare with name \\.\pipe\com2. All proper options in VMWare are checked
    Debug flag for OS enabled through msconfig. Debug port is COM2 running at 115200 baud.
    I ran the test target client "WDK Test Target Setup x64-x64_en-us.exe" on the machine before provisioning the computer
I was able to provision the computer properly -- it created the WDK Remove User account. However, I'm running into some issues actually debugging. Below are the steps
    Launch the Windows 7 x64 target image in VMWare and wait on the boot menu
    In Visual Studio (host machine), go to Debug -> Attach to process -> Select my computer -> Select process "Kernel" -> Attach
    In VMWare, press enter to boot Windows
    It takes a while, but on my host machine, Visual Studio eventually connects. I can choose to "Break All" and actually use the debugger.
However, I can't seem to connect to the debugger if I don't do it before booting the kernel. And I can only attach once. For example, I can't let Windows initialize to the desktop and then build my driver and begin debugging. The debugger will always hang on
"Waiting to reconnect...". The same goes for if I begin debugging on kernel initialization, decide to stop debugging, then try to reconnect or reattach; it will hang on "Waiting to reconnect..." indefinitely as well.

Follow the directions here: https://msdn.microsoft.com/en-us/library/windows/hardware/jj200334%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396
You are using user mode debug setup menus, that won't work.
Mark Roddy Windows Driver and OS consultant www.hollistech.com

Attaching serial ports to Hyper-V ?

is it possible to attach serial port to Hyper-V ? what is named pipes redirection and how does that work ?

Hi,
You can refer to the following links:
Serial over IP Network
http://www.virtualserialport.com/products/serial-over-ethernet/
Serial/IP COM Port Redirector
http://www.tacticalsoftware.com/products/serialip.htm?gclid=CPegqv-Y35wCFcItpAodoSnyIw
Important Note: This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control these sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the use of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet.
Best Regards,
Vincent Hu
and ... what I can use named pipe serial port redirection for ?

Sending/reading hex data to a serial port in Powershell

I have a device which responds to serial port requests. Using portmon I can see a request formatted as a six byte hex string.
e.g. x'02031005E6 the last byte being a crc which I can work out.
I don't seem to be able to write this data to a comm port as if I write
[Byte[]] $request = 0x02,0x03,0x10,0x05,0xE6
$port.Write($request)
I see
0.00189600 powershell_ise IRP_MJ_WRITE LSerial0 SUCCESS Length 12: 32 20 33 20 31 36 20 35 20 32 33 30
where I was expecting Length 6: 02 03 10 05 E6
even if I write
[Byte] $request = 0x02
$port.Write($request)
I get
0.00188317 powershell_ise IRP_MJ_WRITE LSerial0 SUCCESS Length 1: 32
I have a nasty feeling I am misunderstanding how Powershell handles hex strings/arrays and will assume the sucking of air through clenched teeth on the reply.

Your handling of Bytes, hexadecimal literals and arrays is fine. What type of object is the $port variable referring to?
Edit: If it's a [System.IO.Ports.SerialPort] object, then the problem is that you're calling SerialPort.Write() with a single argument. The only overload of that method which takes a single argument accepts a String parameter, and PowerShell
is automatically turning your bytes / arrays into a string representation (which is then being converted back into a byte stream.)
To use SerialPort.Write with a Byte[] argument, you need to pass in 3 arguments: The array, the offset, and the byte count. For example:
[Byte[]] $request = 0x02,0x03,0x10,0x05,0xE6
$port.Write($request, 0, $request.Count)
See
http://msdn.microsoft.com/en-us/library/System.IO.Ports.SerialPort.Write(v=vs.110).aspx for more info.

Connect a PIC/MCU micro controller to serial port of phone

Hello,
I am relatively new to j2me programming and i would lke to ask if it's possible to connect a MCU to the serial port of the phone and receive streamng data while the MIDlet is on?
If so how can this be done> Does it work the same way a serial connection? I connect the MCU to the USB pins then to the mobile phone.
Does anyone who have worked with this care to share their valuable experience? Thanks in advance.

Hi, i checked with the helpdesk from motorola and they replied that i require a license to access the proprietary interface (please refer to the reply below). I'm thinking ofusing Sony Ericsson k610i since it's JP-7. However, I wonder if they have similar issues with it.
It seems that since we are to interfacing with a PC, the allocation of a virtual port might be a problem, that'smy main concern.
FAQ found in motorola website:
We'd like to connect a RS232 device to a RAZR V3 phone. From a Java API perspective this is possible via the CommAPI.
We have succesfully tested to connect the RAZR V3 Mini-USB with a PC via a USB-cable - and we were able to transmit data from the RAZR V3 to the PC (Hyper Terminal) and vice versa.
Which technology is needed in the RS232 device (no PC - just a stand alone RS232 device) to communicate to the RAZR V3 via the Mini-USB?
Answer
We do not normally support the use of non-PC RS232 connections to current Motorola handsets. The only serial connection supported is serial-over-USB, where the handset is connected to a USB port on a PC, and the PC operating system assigns a virtual COM port to the USB connection for this purpose. Microsoft Windows is normally needed to meet this requirement.
Although RS232 functionality exists within the handsets, it is a Motorola proprietary interface only available to firms who licence the technology from us. Motorola currently licenses the CE Bus technology to selected 3rd party companies interested in building accessories for our PCS devices. Please contact Gene Eggleston ([email protected]) or telephone 847-523-4976 (USA) for information on the license and business arrangement. As a licensee you will receive a specification that details the access and use of Motorola's CE Bus.

Serial port hang/freeze

On rare occasions my application freezes. What I believe is happening is that the VISA Read or VISA Write vi never returns. (The program is an executable, so I can’t go to the diagram to be sure. I just released a new version that will help me isolate it further, but it takes time to propagate new software to users.) I do have the timeout set to 500ms, and I know this works because it timeouts when I have no hardware attached.
When the freeze happens, I have to go to the Task Manager to kill my application; however, it never actually quits. It goes away on the Applications tab, but won’t leave the Processes tab. Selecting End Process on the Processes tab won't make it go away either. I can get it to go away, however, by unplugging the USB cable. I then plug the cable back in, relaunch my application, and all is OK. (A restart works, too.) I am using the FTDI 2232 USB to dual serial port chip (set up for RS485) in my system.
My first question is whether anyone has seen this before or has a suggestion to get this work.
My second question is how do I figure out what is actually hanging? My LabVIEW 8.5.1 executable calls a VISA 4.41 driver. The VISA driver calls a Windows COM port driver. The Windows COM port driver calls the FTDI driver (Version 2.4.6). The FTDI driver calls the USB driver. We are running Windows XP with all updates installed.
I have about 50 of these systems running continuously. I see about one freeze like this once every few days on a random system. I am not able to reproduce it on demand. Any debug solution will have to be deployable to all 50 systems; otherwise, it is possible that I won't see the bug for weeks, if ever.
Thanks in advance for the help.
Matt K.

Just dug out the email from FTDI support....
Blue
Hello,
If it is an application problem then what could happen is you ask to read 10
bytes but only receive 5. The application would appear to hang waiting for
the remaining 5 bytes unless you have set timeouts to allow the read to
abort.
The fact you need to unplug and re-insert suggests the driver needs to
reload.
This could in theory be a result of a surprise disconnect.
What this means is the device handle is open and the device disappears from
the PC (like unplugging - but could be an EMC/noise event).
When the device re-appears to the PC the handle and the hardware no longer
match as the stack is not maintained during a disconnect.
This would result in you not talking to the actual device but some "rogue"
device handle which could theoretically hang the application.
Some ideas for debug:
1.
Verify the driver version installed is 2.04.06
http://www.ftdichip.com/Drivers/CDM/CDM%202.04.06%20WHQL%20Certified.zip
2.
Ensure you have set read and write timeouts in your application
3.
Use WM_DeviceChange to determine if you are disconnecting.
http://msdn.microsoft.com/en-us/library/aa363480.aspx
4.
Try increasing the resetpiperetrycount to make the device more immune to
noise events.
http://www.ftdichip.com/Documents/AppNotes/AN_AdvancedDriverOptions_(FT_0000
73).pdf

Problem connecting N79 to serial port using blueso...

Greeetings to All,
I have a big problem, when i connect my n79 using bluesoleil v3.0, i got File transfer, dialup networking and object push services only.
If i try to start serial port service to connect my n79 to a serial port it displayes error "can not start service".
i have tried various bluesoleil versions but the problem remains same everytime. on the other hand i can connect my sony k750i to a serial port without any problem.
can someone tell me how to connect n79 to a serial port using bluesoleil
OR
Does N79 not support bluetooth serial port connectivity?
or is there any other way to connect n79 to a serial port using blesoleil and my bluetooth dongle on a WINXP SP2 system?
Thanks in Advance

Yes, PCSuite supports a great deal of Bluetooth drivers. These are all built in so, give it a try.
Windows Vista x32 en x64 editions:
Microsoft Windows Bluetooth stack
Toshiba Bluetooth stack, driver versie 5.10.12
IVT BlueSoleil Bluetooth stack, driver versie 5.0.5
Windows XP x64:
Microsoft Windows Bluetooth stack
Toshiba Bluetooth stack, driver versie 5.10.12
IVT BlueSoleil Bluetooth stack, driver versie 5.0.5
Windows XP:
Microsoft Windows Bluetooth (enkel in Service Pack 2)
Toshiba Bluetooth stack, driver versie 4.0, 5.0 and 5.10.12
WIDCOMM Bluetooth stack, driver versie 1.4.2, 3.x, 4.x and 5.x
IVT BlueSoleil Bluetooth stack, driver versie 2.x, 3.x and 5.0.5
‡Thank you for hitting the Blue/Green Star button‡
N8-00 RM 596 V:111.030.0609; E71-1(05) RM 346 V: 500.21.009

Unable to capture data from Serial port using LVRT2010 in single core pentium 4 machine

I am using application written in Labview using windows Labview
Runtime environment 2010. Application creates a tunnel to intercept data from
Serial port.
My problem is, Currently, I am using single core Pentium
processor. When I am trying to intercept the data between COM1 and COM7 (COM 7
is a virtual port) it is not able to capture data.
When I am running Labview RT environment using dual core
processor machine it is running normally. I wonder whether it could be the compatibility issues with
single core Pentium processor.

Hi Magnetica
Are both of the machines running the same runtime engine,
drivers ect?
Have you had RT applications running on this
machine before?
Is the development computer a 64bit machine?
The processor is a supported model (See link below).
http://zone.ni.com/devzone/cda/tut/p/id/8239
Regards
Robert
National Instruments UK & Ireland

Problem on WinXP / Labview 6.1 with VISA (serial port)

There is a problem on WinXP / Labview 6.1 with VISA which i use to poll the state lines of the serial port. The only functions that i use are "VISA Open", "Find Resource", line state properties and "VISA close".
On my own machine (WinME) it works fine as a standalone application (with runtime engine in the same direction), even if i rename the Labview directory so that Labview is not found.
From my VXIpnp directory i deleted all but these files:
directory "Win95",
subdirectory "Bin" containing "NiViAsrl.dll",
subdirectory "NIvisa" containing "visaconf.dll".
When shipping this to WinXP (and copying "VXIpnp" to the root directory), the serial port was not found, so i renamed the direction "Win95" to "
WinNT", but this did not work also.
I installed the VISA server, although it seems not to be required -- no result.
Final question:
What must i do for distributing the program as a standalone application for all windows platforms?

Hey Joachim,
In order to create an installer that includes the VISA Run-time engine for serial IO you will have to purchase LabVIEW 7.x. See screen shot. This packages a small compact version of the run-time that can only be used for serial, but it takes up much less space. The installer that I created has my application, the LV Run-time, and the VISA run-time and it is about 26 MB.
That is much smaller than if I had to include the 32 MB LV 7.1 run-time and the 14 MB VISA run-time separately. It would have been even smaller if I would have uncheck some of the items that I wasn't using.
-Josh
Attachments:
advanced.JPG ‏31 KB

Using a PS/2 keyboard on a Sparc workstation through the serial port

We have recently migrated an application that used to run on a PC, to now run on a Sparc Workstation. This is a SunBlade 1500, running Solaris 8. The application is running in a dedicated console which has a fitted keyboard and trackerball that have PS/2 connectors and cannot be changed.
We need a way of connecting the PS/2 keyboards to the serial ports of the Sparc workstation. We already have a piece of software that will read ascii values from the serial port so we definately want to go through the serial ports.
Can someone please suggest what converters will be required to get the output of the keyboard and trackerball as ascii input to the serial port.

Actually, that's not a bit perverse, at all.
Jonathan's suggestion is a standard method of connecting to a server.
(null cable between the computer serial ports)
... see the Solaris man pages.
man tip
TeraTerm and Hyperterminal are customarily used on a PC running some dialect of Windows.
The 'tip' command is all that's necessary between Solaris systems.
PS/2 is not a serial connection, but is a keyboard/mouse interface 'invented' by IBM when they offered their XT-class PS/2 line of desktop systems, back in the 1980's.
I found this next link by using Google:
http://members.chello.at/theodor.lauppert/computer/ps2/
The smaller DIN ports were more compact than the AT-class keyboard ports and the mouse moved from a serial port to a dedicated mouse port.
Serial communication devices are not keyboards, per se,
and keyboards are not serial communication devices.
You need other hardware in between to translate what the human being sends, and another computer is a common method to accomplish that translation.
Having said all that ...
Since you cannot change the dedicated console hardware,
I suggest you go to the manufacturer of that console equipment
and have them suggest some sort of serial-to-serial interface lash-up.

Using a serial port under j9.. How?

I am trying out j9 on an ipaq. I am trying to get javax.comm to work.
When I call CommPortIdentifier.getIdentifiers ();
I get java.lang.string.NoSuchMethodError: java/lang/String.<init>([BIII)V
It would appear that the javax.comm package was implemented using a now deprecated String method, and that IBM has chosen not to implement deprecated methods in it's j9 vm (I get the same issue trying to run swing.)
One would think that what is needed is an updated javax.comm package. However, there doesn't appear to be a javax.comm package on Sun's site, let alone an updated one. Whats going on here? Can someone give me an idea of how Sun and/or the JCP thinks about developers who want to use serial ports?
Is there a workaround? A different way of talking to a serial port? Or should I abandon j9? I should add that I got my software running just fine on nsi.com's creme vm (javax.comm and swing too) and it worked without any hassles. It even understands jar files (is there a reason why IBM insists on having a link file?). However, the reason I persevered was that a) j9 is cheaper and more importantly b) nsi.com don't seem terribly keen on actually selling their product. I have lots of references to them selling their vm in bundles of 40 ($1000) which is a bit ouchy but hey I'm not paying for it. But, you'd think the nsi.com people would actually confirm this on their site?
So.. can it be done? And why, in the world of embedded systems (my field) and now lots of phones and pdas, is so little attention given to the humble serial port? It doesn't matter how fancy the protocol is, underneath it all is a UART. grumble
-Russel

Hi Russel,
I will probably soon be in the position you are in trying to get this to work. I found the following page which offers some promise.
http://www.intrinsyc.com/support/I-Linux/405-cube/misc/smf_serial_port_access_example.htm
Mike

Serial Port of Microsoft

Similar Messages

Maybe you are looking for