Problems accessing the parallel port

Dear All,
I'm having problems to access to the parallel port using the VI write /
read to the serial port, it returns the error code 37. As far as I've
seen in the documentation this error code is for UNIX systems and we're
using Windows 95.
Anybody know what's going on?
Cheers,
Ernest
Ernest Mendoza
Institut de Ciencia de Materials de Barcelona
Consejo Superior de Investigaciones Cientificas
Campus de la UAB. E-08193 Bellaterra (Barcelona)
Tel- 34- 93 580 18 53
Fax- 34- 93 580 57 29
http://www.icmab.es/dmag/new/index.html

This is the device not found error. It is platform independant. It means
that you are addressing a serial port that LabVIEW cannot find. This is
becuase the port is not there or LabVIEW cannot access it. Make sure the
serial port you are addressing is configured in Windows device manager and
then make sure you have the file serpdrv in your LabVIEW (or compiled executable)
directory.
-Jim
Ernest Mendoza wrote:
>Dear All,>>I'm having problems to access to the parallel port using the
VI write />read to the serial port, it returns the error code 37. As far
as I've>seen in the documentation this error code is for UNIX systems and
we're>using Windows 95.>>Anybody know what's going on?>>Cheers,>>Ernest>>>-->____________________________________________
_______>>Ernest
Mendoza>Institut de Ciencia de Materials de Barcelona>Consejo Superior de
Investigaciones Cientificas>Campus de la UAB. E-08193 Bellaterra (Barcelona)>Tel-
34- 93 580 18 53>Fax- 34- 93 580 57 29>http://www.icmab.es/dmag/new/index.html>___________________________________________________>>

Similar Messages

Problems Reading/Writing Parallel Port Data, Status & control Registers Using In Port.vi and Out port.vi

Hi,
Can anyone there help me Please with the problem. I am trying to
communicate with the parallel port using my program which i have
attached to the message. I am running LabVIEW 7.0 Professional with
application builder. All the program does is reads and writes to the
three parallel port registers. It runs FINE!!! in my computer. But when
i built an executable (see attached) and tried running on a different
computer (with LabVIEW Runtime engine 7.0 installed) the program does
not read/write to the registers. The target PC had the parallel port in
SPP mode just like mine. I can't seem to understand whats going wrong?
Can anyone please help me if you know the right answer.
Thanks
Attachments:
Programs.zip ‏119 KB

Hi Guys,
I too have a problem using "Out Port.vi", but of a diferent kind. I use this VI to control the Parallel Port which in turn controls a small circuit. I use only two data pins, DP-2 and DP-4 for this purpouse. I use LV 7.1 Professional Development version in a Windows 2000 operating system. Now, my main problem is that my code runs fine (both is development and .exe forms) in my development computer, but when I try to run the .exe version in other computers (Windows XP operating system), it asks for a "protocol file" while starting (look at the attached picture).
Now, I really have no idea what kind of a protocol file it asks for and just click "ok" and proceed to work, the most interesting part is that the code works well as I expected. So, my only problem is that it asks for a protocl file which I want to avoid. As with the application building, I do all that is required like including the sub VIs (self developed), creating an installer, enabling the port access, and creating a proper .ini fine. I also use the Out Port.vi from the AccessHW library.
I have my doubts on two fronts,
1) With the version conflict, since my development computer runs with Windows 2000 and my target computers all run with Windows XP
2) With the Out Port.vi which further contains a small VI "Output Word to Port.vi" in it and that further contains Call Library Function Node, which might call soem external files, like what my problem is.(look at the attached picture)
I don't have answers to these questions and may be my problem is in different place, but I would like to hear from anyone who could give me a helping hand. I am in a situation where I could not disclose my code.
Thanks in advance,
mohan
Attachments:
protocol file.zip ‏153 KB

Is it possible to get direct access to parallel port pins under Windows NT? What can I do

to get such an access under NT? I found Write to Parallel Port.vi but I can`t open it. The error that occurs is:
resource not found, error occured while loading the vi, labview load error code 8: could not load vi ressources.
This vi is from 1994. Maybe the source of trouble is that I`m using version 5.1.1 or it is a problem with NT. What do you think?

Parallel Port.vi can only be used in DOS-Systems (like Win9x, WinME ;-). NT does not allow writing to parallel port with low level routines. It is more useful to use the digital port that is on most of the DAQ cards.
Some more informations on parallel ports: http://www.lvr.com/parport.htm
In general it seems to be possible. Somebody told me just to use the write port command with the address of the parallel port. Another way seems to be to tell NT to allow direct port access - but I don't know how.
Andreas

How can I write to the parallel port using LabVIEW 6.0.2

I have tried updating the labview.ini file and also using the parallel.llb available on the site. When I execute the program it gives me error 37 saying,"device not found". I am running this code on windows 98. I tried to use VISA write,serial port write (using port 10) but nothing seems to work. I also tried to develop a sample code using inPort and outPort, but no success, it is not able to read the data back from the parallel port, even if it seems (????i don't know any way to cross-check it though????) to write.
Does anybody know the problem here?
THanks.
Pari.

Thanks Brian.
Well here is the next problem. I got a VI (attatched) off ni.com and it works fine on a windows98 platform. But quits working on NT.
I can write perfectly (which i checked by hooking an LED display unit at the other end of the parallel port cable). I observed that the LEDs respond to the toggling of individual bits (data bits). But the error occures at the "out port.vi", when I try to run it on a NT machine (where I actually wanna use it). Are you aware of any changes to be made in order to run a VI on NT that works on 98?
Thanks again.
Pari.
Attachments:
parallelPortSwitcher.vi ‏124 KB

Why does this loop used to write values to the parallel port keep going forever?

Have a look at this VI guys. I'm trying to send a sequence of bits (used to trigger an IC). I'm interested in the last bit of the data port (D0). so I'm sending either 0 or 1 to that pin to trigger the IC. it works, but the problem is that the loop keeps going forever and i cant control it. if i send 3 to the loop count, I'm expecting to get: 1 0 1 0 1 0, but it doesnt stop and keeps going forever.
It seems that the problem is not with the loop. because i deleted the loop and just left the flat sequence so that it executes only once, but still it keeps repeating. How can i make the flat sequence execute only once?
I'm using a parallel port monitor (parmon.exe) and a LED connected to D0 of the parallel port to check.
If anybody has an alternative or better method to send the bits to the parallel port, I'd be very thankful.Message Edited by krayzie on 05-14-2005 04:33 PM
Attachments:
pport.vi ‏24 KB

It works just fine here. Place an indicator to the iteration terminal [i] to watch how things progress. Do the number ever increase above N-1 to what you wire to N? I don't think so!
Also make sure you don't run the VI with the "Continuous run" button. In this case the VI would immediately restart whenever it is finished. use the "Run" button.
LabVIEW Champion . Do more with less code and in less time .

Problems with the USB Ports

Hi there,
I writing this because I'm having some really big problems with my USB ports.
A few days ago I plugged in an USB-Hub that was quite cheap. Suddenly a window popped up saying that a USB device was deactivated because it "needed" to much power. Since this happening, two of those windows keep popping up everytime I boot the MacBook. I called Apple and got some help: I had to delete some .plist files and clear some caches. The man who helped was able to find the error and deactivate the notification, he also told me to make a PRAM- and a SMC-reset. The man said that it's just a software problem and that I have to reinstall the system if we don't find a solution. So, one day later I reinstalled the system (Lion) and not only didn't it help, the two notification windows were popping up again...everytime I booted the Mac. So I decided to formate the whole hard drive and install Snow Leopard -> still the problem with the USB ports. After that I installed Lion -> still the problem with the USB ports. I even tried to extract the .kext files that are important for the USB functionality from an earlier Combo Update, but it didn't help either. The point is, that the Mac doesn't recognize my external hard drive or any of my iDevices. Sometimes it recognizes USB sticks, but only after 20 seconds. The data transfer on both USB ports is also very slow. If I'm lucky and Mac recognizes one of my USB sticks, it takes like an hour for 1GB to be transfered on the USB stick or from the USB sticks to the Mac.
I really don't know what to do and need help, especially because my backup data is on my external hard drive which I can't access because of this problem.
I really hope that someone can help me, I'm very thankful for every answer that could help me!
PS: Sorry for my bad English, I hope that everyone understands what I mean, please tell me if you don't get what I'm trying to explain in the text above.
Sincerely,
iLoud
[UPDATE] I downloaded "USB Prober" and copied the Output file, maybe it helps:
Timestamp Lvl            Message
    0.698 [3]          AppleUSBHub[0x5076c00]::DecrementOutstandingIO(7316), outstandingIO(0), _interruptReadPending(false) - rearming read
    0.698 [3]          AppleUSBUHCI[0x4f97000]::UIMCreateInterruptTransfer - root hub interrupt transfer - clearing unneeded memDesc (0x5073080) from dmaCommand (0x506a100)
    0.735 [3]          AppleUSBUHCI[0x4f97000]::UIMAbortEndpoint - endpoint 1:1,1
    0.735 [3]          AppleUSBUHCI[0x4f97000]::RHAbortEndpoint - Interrupt pipe - noting status change
    0.735 [3]          AppleUSBHub[0x5076c00]::InterruptReadHandler error kIOReturnAborted (expected)
    0.739 [2]          AppleUSBUHCI[0x4f97000]::HandleInterrupt - Host controller resume detected - calling EnsureUsability
    0.739 [2]          AppleUSBUHCI[0x4f97000]::HandleInterrupt - deferring further processing until we are running again
    0.761 [3]          AppleUSBHub[0x5076c00]::DecrementOutstandingIO(7320), outstandingIO(0), _interruptReadPending(false) - rearming read
    0.761 [3]          AppleUSBUHCI[0x4f97000]::UIMCreateInterruptTransfer - root hub interrupt transfer - clearing unneeded memDesc (0x5073080) from dmaCommand (0x506a100)
    0.798 [3]          AppleUSBUHCI[0x4f97000]::UIMAbortEndpoint - endpoint 1:1,1
    0.798 [3]          AppleUSBUHCI[0x4f97000]::RHAbortEndpoint - Interrupt pipe - noting status change
    0.798 [3]          AppleUSBHub[0x5076c00]::InterruptReadHandler error kIOReturnAborted (expected)
    0.801 [2]          AppleUSBUHCI[0x4f97000]::HandleInterrupt - Host controller resume detected - calling EnsureUsability
    0.801 [2]          AppleUSBUHCI[0x4f97000]::HandleInterrupt - deferring further processing until we are running again
    0.823 [3]          AppleUSBHub[0x5076c00]::DecrementOutstandingIO(7324), outstandingIO(0), _interruptReadPending(false) - rearming read
    0.823 [3]          AppleUSBUHCI[0x4f97000]::UIMCreateInterruptTransfer - root hub interrupt transfer - clearing unneeded memDesc (0x5073080) from dmaCommand (0x506a100)
    0.860 [3]          AppleUSBUHCI[0x4f97000]::UIMAbortEndpoint - endpoint 1:1,1
    0.860 [3]          AppleUSBUHCI[0x4f97000]::RHAbortEndpoint - Interrupt pipe - noting status change
    0.860 [3]          AppleUSBHub[0x5076c00]::InterruptReadHandler error kIOReturnAborted (expected)
    0.863 [2]          AppleUSBUHCI[0x4f97000]::HandleInterrupt - Host controller resume detected - calling EnsureUsability
    0.863 [2]          AppleUSBUHCI[0x4f97000]::HandleInterrupt - deferring further processing until we are running again
    0.885 [3]          AppleUSBHub[0x5076c00]::DecrementOutstandingIO(7328), outstandingIO(0), _interruptReadPending(false) - rearming read
    0.885 [3]          AppleUSBUHCI[0x4f97000]::UIMCreateInterruptTransfer - root hub interrupt transfer - clearing unneeded memDesc (0x5073080) from dmaCommand (0x506a100)
    0.922 [3]          AppleUSBUHCI[0x4f97000]::UIMAbortEndpoint - endpoint 1:1,1
    0.922 [3]          AppleUSBUHCI[0x4f97000]::RHAbortEndpoint - Interrupt pipe - noting status change
    0.922 [3]          AppleUSBHub[0x5076c00]::InterruptReadHandler error kIOReturnAborted (expected)
    0.926 [2]          AppleUSBUHCI[0x4f97000]::HandleInterrupt - Host controller resume detected - calling EnsureUsability
    0.926 [2]          AppleUSBUHCI[0x4f97000]::HandleInterrupt - deferring further processing until we are running again
    0.947 [3]          AppleUSBHub[0x5076c00]::DecrementOutstandingIO(7332), outstandingIO(0), _interruptReadPending(false) - rearming read
    0.947 [3]          AppleUSBUHCI[0x4f97000]::UIMCreateInterruptTransfer - root hub interrupt transfer - clearing unneeded memDesc (0x5073080) from dmaCommand (0x506a100)
    0.984 [3]          AppleUSBUHCI[0x4f97000]::UIMAbortEndpoint - endpoint 1:1,1
    0.984 [3]          AppleUSBUHCI[0x4f97000]::RHAbortEndpoint - Interrupt pipe - noting status change
    0.984 [3]          AppleUSBHub[0x5076c00]::InterruptReadHandler error kIOReturnAborted (expected)
    0.987 [2]          AppleUSBUHCI[0x4f97000]::HandleInterrupt - Host controller resume detected - calling EnsureUsability
    0.987 [2]          AppleUSBUHCI[0x4f97000]::HandleInterrupt - deferring further processing until we are running again
    1.009 [3]          AppleUSBHub[0x5076c00]::DecrementOutstandingIO(7336), outstandingIO(0), _interruptReadPending(false) - rearming read
    1.009 [3]          AppleUSBUHCI[0x4f97000]::UIMCreateInterruptTransfer - root hub interrupt transfer - clearing unneeded memDesc (0x5073080) from dmaCommand (0x506a100)
    1.045 [3]          AppleUSBUHCI[0x4f97000]::UIMAbortEndpoint - endpoint 1:1,1
    1.045 [3]          AppleUSBUHCI[0x4f97000]::RHAbortEndpoint - Interrupt pipe - noting status change
    1.045 [3]          AppleUSBHub[0x5076c00]::InterruptReadHandler error kIOReturnAborted (expected)
    1.049 [2]          AppleUSBUHCI[0x4f97000]::HandleInterrupt - Host controller resume detected - calling EnsureUsability
    1.049 [2]          AppleUSBUHCI[0x4f97000]::HandleInterrupt - deferring further processing until we are running again
    1.071 [3]          AppleUSBHub[0x5076c00]::DecrementOutstandingIO(7340), outstandingIO(0), _interruptReadPending(false) - rearming read

Oh, sorry, I meant "I'm writing this...".

Using stand alone executables to send data to the parallel port

I have a executable that uses the parallel port to activate an alarm. The program works well on the base machine which is running windows XP. However when I try to run the stand alone executable on a windows NT machine there is nothing sent to the parallel port. I have updated the Cvirt file on all machines. I don't get any error messages when running the stand alone executable.

I have the same situation using parallel port to control a hot swap PCI extender card and no error showed. I can turn on/off and read correct voltages from the card in base machine. After creating executables, I can turn on/off the card, but got wrong voltages in target machine.
I've installed AccessHW in both machines and copied AccessHW.dll and cvirte.dll to system32 folder and the folder same with executables. I also tried installer with port support and serial support checked.
Windows XP is in both machines and LV 7 in base machine. I use "Output Byte to Port.vi" and "Input Byte from Port.vi" in AccessHW lib.
One thing I observe is initiation. The card manufacturer provides a program with same functions. After running their program, the voltage readings from the executables become correct. The readings remain good after closing their program. I close the executables and run the executables again and still see good results unless restarting the target machine.
Any solution for the problem? Thanks in advance!

Read the parallel port

Hello,
I am working with LabView 7.0 and with Windows 98. I want to read the
parallel port, but I don't get it. I am using the I Saw In port.Vi but
I don´t read anything, but however with the function Out Port.vi if
that get
to write in the port. Is somebody able to throw a hand?
Thank you

Hi,
Hope this gives some light to your problem:
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/c80752c53094c296862565f3007ac765?O...
Regards,
Jaime Cabrera
Ni Applications Engineering Spain
Regards,
Jaime Cabrera
NI Applications Engineering Spain

How can i use the parallel port

I was wondering how to adress my PC´s
parallel port. I did'nt find a suitable
VI in the palettes.
Do I have to read/write somehow directly
to the port adress in memory 0378 ...?
If so, how can this be done ?
Thanks for any help,
Holsch

Use VISA to read/write to the parallel port just like you would read/write
to the serial port. I would staty away from the inport/outport stuff. I believe
there's some articles in the KnowledgeBase if you get stuck.
[email protected] (Helmut Hullen) wrote:
>Hallo, Holger,>>Du meintest am 29.07.00 zum Thema how can i use the parallel
port>> I was wondering how to adress my PC's>> parallel port. I did'nt
find a suitable>> VI in the palettes.>>Look at "in port" and "out port".>Under
Windows NT/Windows 2000 you need a special library for direct port >access,
look for "hwaccess" or "accesshw".>>Viele Gruesse!>Helmut>

Is anyone else experiencing problems with the thunderbolt port on their Mac Mini's regarding using it to connect a second monitor? I've got the Mini Display Port to DVI-D adapter along with a DVI-D cable and I can't get an image on the second monitor.

I had an dual display image / setup working twice for a few seconds, but then it cut out. I think there may be a problem with the thunderbolt port.

As far as I can tell you have only listed that you have a DVI monitor connected to the Mini Displayport socket (i.e. the Thunderbolt socket) via presumably the Apple Mini Displayport to DVI adapter and a DVI to DVI cable.
You don't appear to have listed what the second monitor is and how it is connected (even though not working). As such I cannot tell what may be wrong.

How to access the serial port in Java?

How can I initialise and access the serial port for writing and reading data from it? Are there any code examples available?

I tried that and I tried compiling and executing one of its examples, the one below:
import java.io.*;
import java.util.*;
import javax.comm.*;
public class SimpleWrite {
static Enumeration portList;
static CommPortIdentifier portId;
static String messageString = "Hello, world!\n";
static SerialPort serialPort;
static OutputStream outputStream;
public static void main(String[] args) {
portList = CommPortIdentifier.getPortIdentifiers();
while (portList.hasMoreElements()) {
portId = (CommPortIdentifier) portList.nextElement();
if (portId.getPortType() == CommPortIdentifier.PORT_SERIAL) {
if (portId.getName().equals("COM1")) {
//if (portId.getName().equals("/dev/term/a")) {
try {
serialPort = (SerialPort)
portId.open("SimpleWriteApp", 2000);
} catch (PortInUseException e) {}
try {
outputStream = serialPort.getOutputStream();
} catch (IOException e) {}
try {
serialPort.setSerialPortParams(9600,
SerialPort.DATABITS_8,
SerialPort.STOPBITS_1,
SerialPort.PARITY_NONE);
} catch (UnsupportedCommOperationException e) {}
try {
outputStream.write(messageString.getBytes());
} catch (IOException e) {}
But when I execute this I get the error:
Exception in thread "main" java.lang.NoClassDefFoundError: SimpleWrite
What is wrong with this example??

Exchange setup error: "There was a problem accessing the registry on this computer"

Hi,
i am trying to install Exchange 2007 SP1 in a Windows 2003 Server standard 32 bits version.
During the "Readiness checks" i received the next error in "Hub transport role prerequisites":
Error:
There was a problem accessing the registry on this computer. This may happen if the Remote Registry service is not running; it may also indicate a network problem.
Remote Registry service is running. I've searched for the error in google and in some topics appears that the error is due to the "Client for Microsoft Networks" and "File and Printer Sharing" is not installed in the LAN properties. The server has 2 network cards and in both of them is checked. One of the connections is disabled.
I dont know what more to do, any help will be appreciated.
Thanks

No, firewall is disabled.
Setup Logs says:
10:50:04.890: Starting Collecting Data phase.
10:50:04.921: No mapping between account names and security IDs was done
10:50:04.984: Error (Unexpected error [0x674CBB7E] while executing command '[Microsoft.Win32.RegistryKey]:penRemoteBaseKey([Microsoft.Win32.RegistryHive]::LocalMachine, [System.Net.Dns]::GetHostEntry([System.Net.Dns]::GetHostName()).HostName)'.) trying to process object [Microsoft.Win32.RegistryKey]:penRemoteBaseKey([Microsoft.Win32.RegistryHive]::LocalMachine, [System.Net.Dns]::GetHostEntry([System.Net.Dns]::GetHostName()).HostName), skipping object.
10:50:06.093: Completed Collecting Data phase.
10:50:06.125: Error (Rule name 'PreReq_fPassiveUninstallNoCMSPresentKey' referenced by rule 'PreReq_fPassiveUninstallNoCMSPresent' in input file is not defined) in format of rules in configuration file.
10:50:06.171: Starting Postprocessing Rules phase.
10:50:06.187: Completed Postprocessing Rules phase.
Thanks for your help!

How can i us the parallel port of the printer to control a frequenz-generator?

Hello all !
I like to control with LabVIEW 8 student-version, the Frequenz-generator gadget . For this challenge i like to us the parallel port of the printer. I need for data flow only 2 cable. The frequenz-generator gadget need two signal : Low and High.How can i us the parallel port of the printer to control a frequenz-generator gadget? I have us the VIs-Visa (Visa-Serial, write, Close ), but i dont no what command i have to write on the Visa-Write so that the Signal can be in the low or high position.
Thanks

Hi Jeanjac,
first, look here:
http://en.wikipedia.org/wiki/Parallel_port
to get the port numbering. also, be sure not to leave pin unconected, sometimes you might get an error message otherwise (i remember pin11 has to be always connected or so for windows...)
second, just run the test panel in MAX and write something to your device to check if it works.
then in LV, you have to decide to which pin is connected your instrument. in any case you have to address all 8 output pins together! this is a parallel...
if you prefere to use only one pin, then you can use the serial port, with just pin 2 and 3 connected. it would work easier for you, since you address only one bit.
Gabriel
... And here's where I keep assorted lengths of wires...

Errors with the parallel port

I am trying to communicate with a robotic arm which is attached to the parallel port.

and... ?
See:
http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RPAGEID=205&HUSERSHADE=0&HOID=5065000000110000006D070000&UCATEGORY_0=_49_%24_6_&UCATEGORY_S=0
2006 Ultimate LabVIEW G-eek.

How can I use the parallel port as an input channel to communicate with a SPECTROMETER?

Hello,
The sensing system we use is called: FieldSpec Pro from www.asdi.com.
The spectrometer has a LPT terminal. I'd like to use LabVIEW to acquire signals from the spectrometer for further analysis.
Thank you!

Dennis,
I appreciate your time.
I have asked the copmany for such infos, but it seems to be confidential.
Do I need an I/O DAQ-Card?
Dennis Knutson wrote:
About all that tells me is
that I'm located in the same town as the manufacturer. You'll need to
find some specification that describes the parallel port protocol.
Without that, you're just wasting your time. Even if the instrument is
constantly sending data, you'll need to know how to interpret the data
and there's nothing that says it has to be sending constantly. Maybe
you first have to write something to the port first. Talk to them and
tell them you want to replace their software with software of your own
and need to be able to read the data.

Problems accessing the parallel port

Similar Messages

Maybe you are looking for