Printing Alarms On LPT

My client have purchased DEll T100 System.Unfortunately
This System Does not have any Parallel Port (LPT1).
I want to connect my EPSONLQ 300 Printer with Dell T100.
Printer Connection Via USB Port is not applicable for me
because I am Printing Alarm From Labview, NI Distributed System
MAnager , which Prints Alarms Only on Parallel or Serial Port
I googled for this Problem and
Net USE LPT1 \\COmputer_NAME\Share_Printer_name /Persistent:Yes
does not solve the Problems.
NI DIstributed System Manager Record following Error
Failed to open session to the Device LPT1:
NI VISA Error Code: -1073807343
Kindly help me, How to Emulate LPT1 Port on DELL T100 System or
How can I associate LPT1 with the USB port.
Regards

duplicate post, continue here!
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome

Similar Messages

Print alarm window

I can't get lookout to print alarms as they appear in the alarms window. I've changed the .ini file settings so that only the time, process, and description show up in the alarm window and they're logging to LPT1, but when it prints out it still prints out all the columns. How can I fix this?

You only change which columns to show in alarm window, but you cannot specify which columns to be sent to printer.
Ryan Shi
National Instruments

Crash when printing alarms

We are experiencing crashes when we print alarms.
Unfortunately we cannot find a way to reproduce systematicly the crash.
Does anybody have the same alarm printing problem?
Thank you your feedback.
Michael

Hi Michael,
You might consider giving National Instruments a call at (512) 795-8248. Depending on your version of Lookout this behavior may have been addressed recently.

Printing alarms to an Ink Jet printer?

In all the SCADA systems that I have ever done, I have always spec'ed a Dot matrix printer for Alarm Printing. Using a Dot matrix it is simple for the printer to do line by line printing and not form feed a whole sheet of paper.
With the price of Dot matrix printers going up and Ink/Bubble/Laser Jet printers going down. Has anyone been able to use one of these types of printers for alarm printing, and not have it form feed a sheet of paper for every alarm it prints?

Ollie,
For more information on this issue, please see "Lookout Alarm Printing"

Multiple users logged into one server, each users printer has a different name, application needs ONE name to print to.

Multiple users logged into one server, each users printer has a different name, application needs ONE name to print to.
I'm NOT in any way a Terminal Services expert and I need help trying to get an application program working in a multi-user environment.
The issue is that the printer changes for every user that is logged in. The application needs to print NOT to the default printer, but to a "special" printer which is selected in the application... let's call it a label printer to simplify the explanation.
You have your default regular printer, easy for the application to find that one, and then you have a special printer that labels get printed onto. The application needs to know what printer is the label printer. So we allow the user to select that in the
application and the selection is stored in a config file in
C:\ProgramData\mfgr\prog\setting files
I don't have access to the application so I can't change how this works.
In the "regular" world, selecting the label printer driver to use should be per machine, NOT per user. When a new user logs into a machine, the physical printer doesn't go "poof" and a new printer suddenly appear. Same printer for all
users.
Yet in terminal services, the physical machine is "merged" with the virtual machine on the server. And there can be many users logged in at the same time. So each users real machine (and real printer) is injected into the "fake" terminal
services machine. The name of the printers is made unique for each user. So the printers DO go "poof" and change names depending on the user logged into terminal services.
So user "A" logs in and sets up the application to print to "LabelPrinterForUserA" (or whatever the name of the printer happens to be), that setting is stored in the ProgramData subfolder, and all is well. Later, user "B" logs
in, and when they print, the application tries to print to "LabelPrinterForUserA" which doesn't exist for user B or is only accessible by user A. If user B re-configures, that breaks it for user A.
SOLUTION 1: The way that /should/ work (in my mind) is that you define one "generic" printer in Terminal Services... call it "Virtual Label printer" and when the user wants to print to it, the print job gets re-directed back to whatever
physical printer is actually connected to their local workstation. There is a map of virtual printer to actual printer depending on the current user. The application is told once to print to "Virtual Label Printer" for all users.
SOLUTION 2: Or... there should be some way to make the ProgramData sub folders separate per user. E.g. when user "A" tries to access:
C:\ProgramData\mfgr\prog\setting files
they actually get
C:\UserData\UserA\AppData\mfgr\prog\setting files
and user "B" gets
C:\UserData\UserB\AppData\mfgr\prog\setting files
So the question I have is: Does either of those solutions exist hidden somewhere in the setup of terminal server? Or is there another way around this issue that I don't know?

I don't really have a "for sure" answer to this, but because people here can't seem to deal with a question that hasn't been answered I'll provide the best answer I did receive from ServerFault.com user Nathan:
I can feel your pain with using old software on terminal servers ...the solution I've come up with definitely won't scale as it requires some manual configuration, but I've gotten this method to work with our label printers (which require to be
printed to an LPT port...yep, that old).
Share your USB-connected printers to the network on each machine. Then, have the user log in on aunique session for each of them
(a TS account cannot be shared among computers for this to work) and install a network printer pointing to the USB one they shared. Try to use a DNS name to account for possible DHCP movements.
After, it should work. Each user can do this since display names can be identical as long as the ports are different (which they are).
This was clarified by the following series of comments:
I think you are on to something here, and I originally advised the admin to do this. The problem he ran into is that it setup the printer names in the TS as "printer on usersworkstation"
and he could not rename it except to change the "printer" to whatever. E.g. the "on userworkstation" remained. I believe there is another way of installing the printer which avoids this, but I can't find it. Ages ago, one used to do NET
USE LPT2 \\computer\printer password /USER:domain\user /PERSISTENT:YES and then tell the driver to print to LPT2 –  James
Newton Mar
17 at 16:21
@JamesNewton That's actually the exact method we used. The way around the "network printer" part is to install it as local printer and map it to a TCP/IP port that way. –  Nathan
C Mar
17 at 16:28
You mean in the case where the printers are TCP/IP connected and not local USB / LPT to the users workstation? That makes sense. Wonder if this will work for USB connected printers... –  James
NewtonMar
17 at 16:35
@JamesNewton You'd share the local printer on the client's PC then on the server connect via TCP/IP to it. You'd need static addresses or use DNS names if DHCP, though. –  Nathan
C Mar
17 at 16:51
Ah. Yes. I see. Looks like the LPT thing should work even with a USB connected printer:superuser.com/questions/182655/… –  James
Newton Mar
17 at 17:09

Windows 2008 R2 Terminal Server clients lose remote printer queues after logoff

There are similar issues to this already on the forums but not precisely like this as far as I can tell, and I have tried all the fixes mentioned in those other threads.
Windows 2008R2 terminal server connecting to a 2008R2 print server. A script maps a connection to the print server on login. Users can browse the print server, connect to print queues to add them, and the queues work OK at first. As soon as they logoff/login
again, the queues still appear in their list of printers but cannot be selected for printing ('Print' button is greyed out).
Domain administrator users can print OK always; this is only affecting regular-user accounts, so it is probably a security/permissions issue. Print queues configured on the terminal server itself are OK, this only affects the queues on the
print server.
No errors are generated in the Event Logs. No failures seen for the print spooler or anything else.
I have added Everyone with Full Control to C:\windows\system32\spool on the terminal server. Tried giving full permissions to all in the printer properties. Cleaned out all registry keys in Client Side Rendering Print Provider as mentioned in some other
threads. In group policy, client printer redirection and LPT port redirection is allowed, use Easy Print driver first, and the print server is in the Intranet zone for low security. The issue happens for all print queues on the print server with a variety
of drivers so I don't think it is driver-related.

A bad GPO being applied ??
If you isolate a user, remove all GPO (even loopback's one), connect manually to a printqueue to make him install's one. Logoff and reconnect and check again if the printqueue work good. The only right that could block you is the driver's installation, but
I really sure that you don't have that issue (as it would be logged anyway)
The admin. account often have less GPO that apply to him.
MCP | MCTS 70-236: Exchange Server 2007, Configuring
Want to follow me ? | Blog:
http://www.jabea.net | http://blogs.technet.com/b/wikininjas/

Lookout 6.02 stops putting alarms in the alarm window after running awhile

This system has worked fine for a couple of years (well except for not being able to print alarms -but we will tackle that later)
What appears to be happening is that on restart everything looks good and we have alarms visable in the alarms window. But, after awhile say an hour or so, the alarms stop showing up in the window.
I believe this has slowly crept up to this point as the Customer has on occassion stated that an alarm was not in in the window even though you could see it on the main system screen.
Running Windows Xp Pro.

After an hour or so, do all alarms stop showing up in Alarm Window?
Could you let the customer check the alarm database by MAX? Create an Alarm Viewer and check if the missing alarm is in the database.
The customer can also follow this KB to check the settings.
http://digital.ni.com/public.nsf/allkb/A4F007F96AB1EB1E862569C30080C731?OpenDocument
Ryan Shi
National Instruments

Re:"Alarm Clock" message

hi,
I got the similiar problem as mentioned in "Alarm Clock" message.
Can anyone be so kind tell me how it comes and how to deal with it?
Thanks,
char
i m writing a program using kstat library for
monitoring purpose.
when i run the program it runs perfectly but after
some time it prints
"Alarm Clock"
and ends.
The program doesnt crash or throw any exception.
It is a java program which uses jni to load a C++
library written by me which uses the kstat for
monitoring.
I hope the message is from the system.
Because i m not printing it anywhere in my program.
It is a threaded program which uses pthread library in
C++ layer.
can anyone tell me what could be the reason.
mohan

hi
this is a kind of signal from the system. One way is to mask it using signal handling and then you won't get it. You will get it in applications which are heavly multithreaded and/or running like a server.
I used to mask it like this
signal(SIGALRM, alarmClockSigHandler);
Where in the method alarmClockSigHandler, I simply print out a message.
It is declared in signal_iso.h in /usr/include/sys/iso directory.
Riaz
hi,
I got the similiar problem as mentioned in "Alarm
Clock" message.
Can anyone be so kind tell me how it comes and how to
deal with it?
Thanks,
char
i m writing a program using kstat library for
monitoring purpose.
when i run the program it runs perfectly but after
some time it prints
"Alarm Clock"
and ends.
The program doesnt crash or throw any exception.
It is a java program which uses jni to load a C++
library written by me which uses the kstat for
monitoring.
I hope the message is from the system.
Because i m not printing it anywhere in my program.
It is a threaded program which uses pthread libraryin
C++ layer.
can anyone tell me what could be the reason.
mohan

Changing the alarm window printout (Set!)

When an alarm comes in I need it to only print the alarm and not the (reset) and (acknowledge) or better yet a way to add 3 unique characters after the Set! In the printout. This is for an external dialer to be about to distinguish between alarms and a reset. Thanks Kevin

Vineet A. wrote:
Hello Kevin,
I don't think there's a way to edit which Alarms are printed in Lookout. You can filter out events, or even certain columns that are printed, but to only print some alarms isn't an option. There's also no way to add characters to the printout of the Alarm.
Are you printing directly to the printer as Alarms and Events occur? What do you mean by an external dialer?
Regards,
Vineet A.
Vineet
Yes we are printing alarms only to a Zetron 1570 dialer, this device looks at the ASCII text stream and when it detects a pre-selected string it will start dialing on the call list for that alarm. The problem that I have is that (Set!) is the only part of the alarm that indicates a new alarm. So I need to use (Set!) as the search string then the description can be used for the type of alarm. By only being able to use one indication of a new alarm, limits this dialer's ability to use more then one call list. If we only used the description of the alarm, this would allow us more than one call list. But when the alarm is (Reset) and (acknowledged), Lookout sends the string out again so the dialer thinks it is a new alarm and starts the dialing all over again. This is the reason for the need to be able to add more characters to (Set!) or eliminate the reset and acknowledge printout.
Thanks Kevin

Send a txt file to the printer with java

Hello,
I want to sent a txt file to the printer in java. I' am using the USB port. I can try to setup a dos command (print c:\test.txt), but I don't know the exactly command.
There is also another solution in java I thing but I don't know the code!
Can somebody give me the exact command for DOS and/or the code I have to write in java?
THANX!!!!

in dos imo you are not able to use usb-port. if your printer would be on lpt you could use javacomm ( http://java.sun.com/products/javacomm/index.html ). there is also another thread talking about this (print text to lpt). for your usb-problem i don't have a solution. but you could use JNI (java native interface). write code in c, compile to dll and use it in java.
tobias
ps: the other thread ( http://forum.java.sun.com/thread.jsp?forum=31&thread=224460 )

How to change the computer name

I need to change the computer name but after this I cannot access to the historical data (printing alarms).
I have already changed the settings in Options->System and restarted the system.
With MAX 3.0 I can see that all the alarm records are stored with the old computer name \\computer name\process\....
How can I do to read the old alarms with the new computer name?
Thank you
Michael

Hi,
When you change the computer name in Options>>System, you are not changing the name of the computer. Rather, you are telling Lookout to log to either a remote or local system. Here are the specifics:
1. Computer Name: Name you want the traces to appear with (\\computer_name\process\...)
2. Default Computer: Computer you want to log to. If the name listed here is different than your computer's name (as seen by Windows), then it will attempt to log directly to that remote machine.
3. Default Path: Directory on either your local or remote machine that you want to log to.
To change the name of your local computer, you will need to do that in Windows. If you have WinXP, you can do this by right-clicking on My Computer and selecting Computer Name.
Go
od Luck
Mike

Problem with m1319f mfp on WIndows 7 and Server 2008

Hi there,
I just bought a m1319f mfp.
Plugged it in an old D-Link dp-300u print server.
The printer work fine on Windows XP.
Not working on Windows 7 and Windows server 2008.
I configured the port as in XP (adress, lp, queue name) and when i print from 7 or server 2008, there is a message on the printer saying "printing document". It stays there for a couple of minutes but no printing. No stuck document on the computer printing queue.
Every time i install the printer from 7 or server 2008, the print server have to be restarted (lights flashing).
The print server seems to fail when i'm on the Windows printer searching part (windows trying to find the printer when adding a new printer).
Maybe the dp-300u is too old?
I have another printer on it (LPT this time) and its working fine. Brother MFC7220 it is.
ANy idea?
Thank
Hope i have been clear, English is not my first language...

BUmp

Modbus Logical Data Member Status Not Logging

I am using several Modbus objects and have setup aliases for all of the Native Members that are being used. For each alias, I checked the "Log to historical database" box. None of the members/aliases that have not been setup as Alarm Conditions (i.e. checking "Generate logical alarm" box) seem to be logging to the database. When I print Alarms and Events ot Event only reports, none of the non alarm events, other than button presses and Edit Mode On/Off events are in the reports. What am I doing wrong?

There are 2 databases. Alarms & Events are logged to Alarm/Event database.
The Modbus objects that you "Log to historical database" are logged as traces and saved in the citadel database. As logical members they will be logged as 1's or 0's. This data can be viewed with Measurement and Automation (MAX) or within Lookout using hypertrend objects.
Regards

Method double execution

im trying to run my method.it works perfectly, but runs 2wice as much as i want it to. this cannot be fixed by didviding the number by two. I need one to execute the Method, maby im not calling it correctly, and one to execute in the loop
Here is my execution file:
import java.util.*;
import java.lang.*;
public class methodExecuter{
public static void main (String[] args){
    Scanner sc = new Scanner (System.in);
    //ALARM
   System.out.println ("Enter number:");
   int num=sc.nextInt();
   *System.out.print (Alarm.Alarmed(num));* //PROBLEM LINE
}And here is my method file:
import java.awt.*;
import java.lang.*;
public class Alarm
//class constructor - no info required
public Alarm ()
public static String Alarmed (int repeat){
   String alarm= "Alarm";
    if (repeat<1) {
      System.out.println ("Sorry, number has to be greater than one!");
    else {
      for (int i=0;i<=repeat;i++) {
*System.out.println (alarm);* //PROBLEM LINE
    return alarm;
}

1) don't call Alarm.alarmed within a System.out.println(..). Rather just call the method itself.
2) within the alarmed method, use a for loop, not a while loop since you know in advance how many times it should be repeated.

[845 Series] 845 Ultra - 9 beeps, does not POST

With my computer running I plugged in a NEC 870 printer into my LPT port. The printer was off and not connected to an outlet, but my system froze. I restarted the computer, it started beeping and didn't POST. I then did a hard reset and it POSTed but froze again when it was starting up XP. I then unplugged the printer from the LPT port but it didn't make a difference I can no longer get it to POST it just gives me 9 beeps .
It's an AMI Bios and I looked up the beep code and got this: ROM checksum error - bad BIOS
I've tried clearing the CMOS; reseated the battery; removed all my pci cards and my video card but still get the same problem.
Could plugging my printer to the LPT port with the computer running have fried my motherboard??
It there anything else I can try.
Thanks

Normally it wouldn't do any harm, but I suppose there was a short somewhere in the loop.
If you disconnected it and reset your CMOS there probably isn't much to do about it.
I would not plug that printer into any other computers before you try it on some ancient P200MMX or something like that that you don't care about.

Printing Alarms On LPT

Similar Messages

Maybe you are looking for