BridgeView and Lookout Protocol Drivers

I can't find Lookout Protocol Drivres on my CD's. WHAT is Lookout Protocol
Drivers? I have BridgeView 2.1.1 Full Developement System and also Lookout
4.0.1 Developement System. Where should I search fot Lookout Protocol Drivers?

Hi,
If you have the Full Development version of BridgeVIEW 2.1.1, then you should
have got an additional CD called Industrial Automation Servers 4.0. This
CD has the Lookout Protocol drivers on it.
Khalid
"Vlad Dragomir" wrote:
>>I can't find Lookout Protocol Drivres on my CD's. WHAT is Lookout Protocol>Drivers?
I have BridgeView 2.1.1 Full Developement System and also Lookout>4.0.1 Developement
System. Where should I search fot Lookout Protocol Drivers?>>

Similar Messages

Bridgeview and Lookout Protocol Driver

I am a Bridgeview 2.1.1 Full Dev. System user - was shipped an upgrade disk
w/out the IA Server disk (4.0?). Now as I wait for it, I was trying to look
for the driver set I had on my previous set of dsiks (Bridgeview 2.1 and
IA Server 2.1) - and I cant find it, although I have installed it from my
previous set before. What am I doing wrong here? Thanks.
Sudhi

Sudhi,
I assume finally you got the the National Instruments IA Server CD. If not, you might contact your N.I. sales representative.
Actually, the IA Servers (aka IAK Servers based on the configuration through NI Server Explorer) is not available anymore and is an obolete NI product. However, if you want to communicate with PLC and other 3rd party hardware, I would recommend to get an OPC server from the manufacturer of the hardware. Another option would be to get the Lookout Protocol Drivers from National Instruments which allows you to communicate through the OPC interface to different PLCs (P/N: 777616-01, Industrial Automation Servers with OPC Interface, Win NT/98/95,CD). Those drivers are included in the Control Edtion Packages for LabVIEW. Check it out: ht
tp://amp.ni.com/niwc/suite/control.jsp?node=10418
National Instruments has as well hardware with FREE drivers and OPC servers to make the communication between LabVIEW and the hardware very easy. E.g. the widley known distributed Fieldpoint devices and the well-known DAQ/SCXI systems will come with OPC servers.
Please check it out: www.ni.com/opc
Hope this helps
Roland

What is minimum poll rate for lookout protocol drivers using modbus ethernet

When configuring the device in lookout protocol drivers as modbus ethernet, what is the fastest update rate that can be used. The default value is 1 second and if I try to enter 0:00:500 the computer beeps and will not accept the value

It's possible to enter poll rates smaller than 1 second. Just don't use a colon but a dot as a decimal seperator for the seconds. That means, don't enter "0:00:500" but e. g. "0:00.5". Entering simply ".5" would do it, too.
Regards,
Jochen Klier
Application Engineering Group Leader
NI Germany

Can Labview v7.0 talk to a Micrologix 1100 PLC via Lookout Protocol Drivers OPC Server v4.5?

Micrologix 1100 <-> Lookout Protocol Drivers v4.5 <-> Labview v7.0
Hello all,
I am helping a local company to use their existing seat of Labview v7.0 to talk over Ethernet with a new Micrologix 1100 PLC. We were hoping to use their existing OPC server that came with Labview (circa 2000) so that they do not have to purchase a new OPC server. Their Labview package is the "NI Developer Suite Professional v7.0 Control Edition" which comes with a "DSC Module" which contains an OPC server called "Lookout Protocol Drivers OPC Server v4.5 (build7)". This software came out several years before the Micrologix 1100 was born, but OPC is supposed to be a cross-platform, cross-generation standard isnt it?
So, when I set-up the OPC server, it asks me which type of PLC I have and the only choices are AB_Logix (Micrologix 1500), AB_PLC2, AB_PLC5 (15 different flavors), and AB_SLC500 (5 different flavors). Can I use one of these that might be similar to the ML1100? I definitely want to use ethernet, not serial.
My application is just reading and writing a couple of variables from/to the Binary, Integer and Float data storage locations approx once per second.
Does anyone see a problem doing this without having to upgrade the OPC server to something that "officially supports" the ML1100 (Like Kepware)?
Thank you very much!!
frenchy

Hi Frency,
You can always just try the 1500 and cross your fingers! We could try to speculate on the forum, but a quick test would certainly be a better use of time. However, I do recommend that if you can upgrade the OPC server to one that supports the 1100 driver you should do so. Kepware and NI-OPC Servers both support this device.
Cheers,
Brian A.
National Instruments
Applications Engineer

BridgeVIEW engine not launching Lookout Protocol Driver

I am upgrading my Windows NT system to Windows 2000. I installed all the required software, including BridgeVIEW 2.1.1 and the Lookout Protocol Drivers. I use only Modbus to communicate with my PLC.
After finishing the software tuneup and having the system working fine under the "Administrator" account, I created an "operator" account (users group) and started the system and BV under this new user.
The surprise is that apparently the BridgeVIEW engine is not starting the Lookout Protocol Drivers. Actually, it looks as if BridgeVIEW does not want to use it at all, because even when I start the Lookout Protocol Drivers manually, BridgeVIEW can not see it, and does not use it to communicate with the PLC.
If I us
e the Server Explorer, I can communicate with the PLC even under the "operator" account.
I tried giving the "operator" account administrative rights, but that did not change a thing.

If that is the case I would check your DCOM settings.
Here are the basic steps for DCOM. The administrator has access by default by other users may not.
Server computer (NT/2000/XP):
Select Start>>Run and enter dcomcnfg.
Go to the Default Properties tab. Make sure Enable Distributed COM on this computer is checked. Use the following combinations of Authentication and Impersonation options depending on the level of security that you desire:
(None) + Anonymous (no security checking)
Connect + Identify (verification only on the initial connection)
Call + Identify (security check on every call during connection)
(For a better understanding of these different options, use the Help button located on the top right corner of the dcomcnfg window).
Click the Apply button to save these changes.
Go to the Default Security tab. You must make sure that the user who will log on to the client computer has all the necessary permissions. Click on Edit Default in each of the three permission options and grant the specific user the Allow access, Allow Launch and Full Control permissions.
Note 1: If you choose Everyone in each of the three default permissions, a minimal level of security is provided and the remote OPC server will be accessible to all users on your network.
Note 2: Because Default Security applies to all applications, the user gains control over all of them. If you want to grant the user permission for a specific application only, don't modify the Default Security. Instead, use application-level security discussed in the next steps.
Click the Apply button to save these changes.
In the above steps you have specified default settings for all applications. Now go to the Applications tab. Select the remote OPC server which you wish to launch. Click on the Properties button:
a) On the General tab select Default for authentication level, discussed in step 2 above (choose a different authentication level if you want a different authentication level specifically for this application).
b) On the Location tab check Run application on this computer.
c) On the Security tab check Use default permissions for all three permission options. Select custom permissions only if you want to set specific permission options for the particular application you have chosen (see Note 2 above).
d) On the Identity tab you can specify which user�s security context will be used to run the application. The interactive user refers to the user who has logged on to the server computer. The launching user refers to the user who has logged on to the client computer.
e) Click the Apply button to save these changes. Then click the OK button.
Click the OK button to close dcomcnfg.
Reboot your computer so that the new DCOM settings take effect.
Verify User Access Permissions. See below link Setting Proper Access for Remote OPC Server When Using National Instruments OPC Clients.
Also here something for Remote OPC and BridgeVEIW.
http://zone.ni.com/devzone/conceptd.nsf/webmain/64E0E00F7A48D15C8625680800692078?OpenDocument
Joji

Necesito conseguir Loockout Protocol drivers OPC Server

Hola,necesito comunicarme con el PID de un horno que utiliza protocolo MODBUS.Para ello necesito Loockout Protocol drivers OPC SERVER,¿De donde me lo bajo?
Gracias

PID,
Lookout Protocol Drivers no es un programa gratuito. Ud. puede conseguirlo por medio de NI:
http://sine.ni.com/apps/we/nioc.vp?cid=11127〈=US
Saludos,
Gerardo Garcia
National Instruments
Applications Engineering

How can I solve the problem, which is shown as Modbus exception response 2 (illegal data address) in lookout protocol driver?

I have a Dynisco UPR700 instrument that has a modbus communication protocol, I use the lookout protocol driver modbus to communicate with it, but the lookout protocol driver gave me the information about "modbus exception response 2 (illegal data address)", how can I solve this problem? where can I set the right data address? Thanks!

Most likely you are trying to access a datamember address that is either not supported or non-existant on the UPR700.
Double check the address that you are writing/reading and make sure that it is supported.
Regards,
Chad Evans

Bridgeview v Lookout

Hi,
Does anybody have any views on which is the best package, Bridgeview or
Lookout?
I basically need to install a plant monitoring system for which I thouight
Fieldpoint modules would be ideal as they could be placed in different
locations around the factory. I need the software to page the duty manager
if certain alarm events happen. It would also be nice to either email a copy
of the offending alarms to the duty manager or publish the panel on the web
so it can be viewed.
Cheers
Andy

Andy Pett wrote:
>
> Hi,
>
> Does anybody have any views on which is the best package, Bridgeview or
> Lookout?
>
> I basically need to install a plant monitoring system for which I thouight
> Fieldpoint modules would be ideal as they could be placed in different
> locations around the factory. I need the software to page the duty manager
> if certain alarm events happen. It would also be nice to either email a copy
> of the offending alarms to the duty manager or publish the panel on the web
> so it can be viewed.
>
> Cheers
>
> Andy
Andy,
Sure, that BridgeVIEW will do the all you want. I prefer BV because of
visibility of program structure and more freedom to developing anything
I want. Lookout is very good configurable traditional-like SCADA, but in
you
r case I'd prefer and using BV.
Good luck,
Sergey Krasnishov,
Automated Control Systems
National Instruments Alliance Member
Moscow, Russia
[email protected]

Color laserwriter 12/600 and 12/660 drivers for OSX

Hello
Where can you download the old Apple colour laserwriter 12/600 and 12/660 drivers.
I just had to reinstall my system from a time capsule back-up and it didn't restore my printer.
(yes a Do know its a really old printer but it still keeps working for me:))
Hope someone can help me out.
This is the list apple use to have, but where can I get it now
Apple software
Model
Version
Print
Scan
Fax
Apple Color LaserWriter 12/600 PS v2014.108
4.1
P
Apple Color LaserWriter 12/600 PS-J v2014.108
4.1
P
Apple Color LaserWriter 12/660 PS v2014.108
1.1
P
Many thanks
Andrew

I haven't found a source for the specific Apple Laserwriter PPDs yet. PPDs are all that's needed to print to postscript printers.
You should be able to use "Generic Postscript Printer" driver choice to print.
I don't have one of those - is the comm protocol you used to add it the "IP > LPD" protocol? IP > IPP won't be appropriate, because the printers were made before IPP was conceived.
By the way, if you can locate the PPD files from an old backup, that should work. PPDs for an already-added printer are found in /etc/cups/ppd (using Finder's Go menu -- Go To Folder for the boot drive, and drill down in the /etc folder on a backup drive).

What is difference between transport protocol and message protocol

what is difference between transport protocol and message protocol
please give definition and small explanation

Hi,
Transport protocol gives information about outside of message details, kind of system, security details.
A transport protocol is a network protocol that has the capability of transferring some payload from one node to another, thus providing some level of transparency from the underlying network.
Transport protocols are used as a mechanism to move payloads around a network. Typically, a payload will have a transport binding associated with it. For example, SOAP (acting as a payload) has a predetermined binding for HTTP (a transport protocol).
Some common transport protocols include: HTTP, HTTP-R, SMTP and BEEP.
Message protocol gives you an idea of message type XI payload
http://help.sap.com/saphelp_nw04/helpdata/en/b6/0b733cb7d61952e10000000a11405a/content.htm

Is it possible to create a configuration profile that will install multiple network printers and their associated drivers

Is it possible to create a configuration profile that will install multiple network printers and their associated drivers?
I was not able to find profile manager on my employer's installation of 10.6 Server. Is this only a feature of 10.7/10.8 server?

10.6 server does not have profile manager, profile manager is only available in 10/7 and 10.8 server
for 10.6 server you'll need to use wgm and server admin
printer management with 10.6, I recommend you read the relevant server manuals regarding
print server and user management, printer management

Http and ftp protocol extremely slow (pop working well though)

Hello. Starting today, on one of my macs, http and ftp protocol are extremely slow (page load 90 sec. instead of 2) (pop working well though). Provider finds nothing, on second mac all is fine (same cable, same settings … ). Cable connection, checked both sockets, changed cable, no change. Since pop3 protocol seems to work fine, this does look like a software problem to me. (Repaired permissions, no other tests or means. All used software up to date (OSX10.6.8 etc.))
I'd be thankful for any idea.

Not at all. Then I turned on NetBarrier, for testing and to avoid any damage (piece of software I don't employ in vain), and all slowed down again, but not quite as badly as before. Restarted, and now it seems back to normal with all extensions loaded. (I had done that before, obviously, and with no outcome, so it can't very well have been just that. But what?)
I'll watch and learn, and report back; unless you have any further suggestions for the moment. Either way, thankyou very much so far.

I just buy a imac 27inch when after intalling everthing for windows 7 and all the drivers i need and goes to the restard part my imac just goes to a black screen with a blinking cursel and it just wont proceed anyone can help me with this?

i just buy a imac 27inch when after intalling everthing for windows 7 and all the drivers i need and goes to the restard part my imac just goes to a black screen with a blinking cursel and it just wont proceed anyone can help me with this?

Support articles for things like this would be here:
http://www.apple.com/support/bootcamp

Can SQL 2000 and SQL 2005 drivers co-exist in PI?

Hi,
Currently in our PI environment, we have JDBC Adapter connections to SQL 2000 database servers for which the Driver has already been installed.
For connecting to new SQL 2005 database servers, I understand that we have to install the SQL 2005 drivers. I also came to know that SQL 2005 Driver is backward compatible and supports JDBC connection to SQL 2000 server.
But the question I have is whether both the SQL 2000 and SQL 2005 drivers can be installed together in a way that connection to SQL 2000 use the 2000 driver and the connection to 2005 uses 2005 Driver.
(They have different connection strings)
Many thanks in advance,
Regards,
Rosie Sasidharan

The SQL Server 2005 JDBC driver is far better than the SQL Server 2000 JDBC driver. The 2005 JDBC driver primarily consists for one file, sqljdbc.jar. ( if you want to use windows authentication there is another file you would need based on your platform x64 vs x86 called sqljdbc_auth.dll. If in the connect string you list ;integratedSecurity=true which means integrated security would be used and this second file would be required. The 2000 driver did not support integrated security.
The SQL 2000 JDBC driver was made up of the 3 jar files:
msbase.jar,mssqlserver.jar and msutil.jar.
If you want to use a Microsoft JDBC driver to connect to SQL Server 2005, than you should use the 2005 driver, sqljdbc.jar.
Follow the instructions in point 1 of the note #831162 - FAQ: XI 3.0 / PI 7.0 / PI 7.1 JDBC Adapter questions 1 and 13.
Since the jar are different I assume you can use the both drivers, but it doesnt make sense.

Find the difference between loading and registering the drivers..

Dear Sir..
Could you please help me to find the difference between two activities..
1.Loading the drivers
2.Registering the drivers
What's the difference between loading and registeing the drivers and what activities take place by the JVM to do it all.

Dear Sir..
Could you please help me to find the difference
between two activities..
1.Loading the drivers
2.Registering the drivers
What's the difference between loading and registeing
the drivers and what activities take place by the JVM
to do it all.You load a class - it isn't specific to a driver.
That is part of java - not JDBC.
Normally JDBC drivers register themselves when the class is loaded. This is specific to the driver and has nothing to do with a user of the driver. It is only a concern to someone who must implement a driver.

BridgeView and Lookout Protocol Drivers

Similar Messages

Maybe you are looking for