PCI -FBUS

We purchase the ITK from FF attached with a NI PCI-FBUS card,The PC became to Blue Screen of Death when we use NI's monitor software after the two port of FBUS board configured to bus-Monitor mode,But there is no problem when the two port of FBUS board configured to NI-FBUS mode. My computer is DELL with XP systerm. FF let me refer to NI for help,So i hope you can help me solve this problem,We want to use the monitor software for capturing package.Besides, If you have a PCI-FBUS card manual, Can you give me it to consult.
Best regards
Bob peng.

I'd recommend you to call NI office in your country. You may find its number from http://www.ni.com/niglobal/

Similar Messages

How many PCI-FBUS/2 cards can be used in a PC to connect to various Fielbus networks?

How many PCI-FBUS/2 cards can be used in a PC to connect to various Fielbus networks? Are there limitations with the Communications Manager and Configurator?
I currently have 1 PC with a PCI-FBUS/2 card interfaced to 2 Fieldbusses. Can I place any PCI-FBUS/2 card into the PC and run 2 additional Fieldbusses?

Hi hhsatBeck,
The limitations of CM and Configurator is,
Configurator supports maximum 4 FF online segments, including H1 and HSE. For more than 4 segments, extra upgrade package should be purchased.
CM supports maximum 16 FF segments, including both online and offline.
So, you can use at most two PCI-FBUS/2 card (4 segments) on one PC.
Feilian (Vince) Shen

PCI-FBUS/2

I have a PCI-FBUS/2 card that causes the machine to lock up. I want to exchange it or get it repaired. What are my options?

I'd recommend you to call NI office in your country. You may find its number from http://www.ni.com/niglobal/

PCI-FBUS -- Dell Optiplex 760, no video after installing the NI PCI-Fbus card

I am just beginning the process of upgrading my 30+ production assembly stations currently using NI PCI-FBUS cards with new computers. (our current PCs are HP dc5100)
I want to utilize our new desktop standard PC system the Dell Optiplex 760.
When I install our existing NI PCI-FBUS cards pulled from functional old PCs and place into this new Dell PCs the PC displays no video signa during the boot process.
I have tried both of the PCI slots on the motherboard, I have upgraded the integrated Intel NIC driver. I have removed the optional dual head video card from the PCI-E slot and am now using the on-board video.
I have run out of things to swap/disable with out correcting the no video issue.
This is the first problem I have had with the new PCI-FBUS cards. They have always seem to plug and play until this new PC model.

Update . ... after swapping the NI PCI-FBUS card with several other PCs, I have determined that card to be defective. It will not start in the new PCs, the other cards I have tested will. I think this is isolated to this card only, so I will be contacting NI about repair/replacement of it.

I have a PCI-FBUS card (dual port), can't connect over 60 devices to it?

I connect to various Fieldbus devices (all from the same manufacturer and same type as we are an OEM) that I am testing (I have 80 in my test system). I have the dual port PCI Fieldbus card and am running communication manager 3.2 on Windows XP with service pack 2. As part of my pretest (getting the devices on the bus and assigning them a unique address) I connect to a device and change its address to 20 and power off the device to have it drop off the bus then relay in the next device and connect to it and change the address to 21 etc etc---this process makes it easiest for me as then all I have to do is connect to the only device on the bus and know that it is the device I am interested in assigning to it a new unique address as the others are not on the bus. I am able to get 30 devices per port (60 devices total since I have a dual port card). After the 30th device is connected, albeit no devices show up on the bus since they are all powered off, I relay in my 31st device but I can't connect to it on a given port (at this point I have 30 devices that were connected to each port but are now powered off). I have the card configured to operate within the address range of 16-102 for both ports.
What is the limit of the number of devices that can be connected to a given port? What would be the recommended way of connected say 80 devices to a PCI card (40 per port). For my application, after the so called pretest is complete, I do have to have up to 8 devices powered on at the same time (4 per port) so that is why I want to keep the addresses unique per device. By the way I know this is not a physical connection issue with my station as I can connect to all devices when I limit my test to 60 devices (i.e. I can do the first 60 or the last 60 so the wiring etc is good as well as my assigned address space/parameters for the NI card).
Some of My NI card parameters are,
Dlme Link Master Info,
Dlme Scheduling Overhead 4
Def Min Token Deleg Time 84
Def Token Hold Time 700
Target Token Rot Time 4096
Link Maint Tok Hold Time 0x0
Time Distribution Period 5000
Max Inactivity to claim Las Delav 100
Las DB Spdu Distri Period 200
System Management Info,
Primary Time Master 0x10
T1 0x75300
T2 0x2bf200
T3 0x15f900
Clock Sync Interval 10
Dlme Basic Info,
slot time 8
Slpdu Phl Overhead 0
Max Response Delay 10
First Unpolled Node 0x66
Number of Unpolled Node 0x79
This link 0
Min Inter-Pdu Delay 16
Preamble Extension 0
Post Trans Gap Extension 0
Max Inter Chan Signal Skew 0
Time Sync Class 1ms
Thanks
Jim

Hello Jim,
In NI-FBUS, the max number of devices that can be connected to a segment (port) at one same time is 32. This value is defined by FF specification.
Please try the following method.
After connecting the 30th device, restart NI-FBUS Communications Manager (CM), then connect the 31th device. Check whether the problem still occurs.
Regards
Feilian (Vince) Shen

OPC Comm. with a NI PCI-FBUS/2

I lose communications intermittenly between my VB.net program and the NI-OPC Server. (Once per week)
It occurs after a long period of no use by the operator, usually overnight. The program and network is always active 24 hours a day. Only a screen saver is used during periods of no use.
I use the auto update feature in the OPC Client. I changed my program to force a read of the OPC Group that communicates with network #2 every 10 min., and the problem reduced in frequency from once per week to once per two months.
It happens always on network #2, which consists of three 3051S Rosemount Pressure Transmitters.
It recovers by simply opening the NI Configurator and viewing my FF configuration.
Something seems to be falling asleep, I assume it is the OPC Server, and the configurator wakes it up.
Other than that everything has been excellent.

Are you using NI-FBUS CM 3.1 (or later) version? If so, the NI-FBUS OPC server should be OK. But the continuous auto updating with long time might result communication failures sometime during a heavy network traffic period. And continuous failures might cause OPC server stop to respond. But the Configurator has better recovery mechanism to deal with communication failures. I guess that's why launching Configurator helps on your problem.
It's good to have NI-FBUS Monitor running in the H1 network during the problem occured, which helps to judge whether it is causd by communication failure.
You can also send e-mail to [email protected] with detailed description about your problem, maybe there is other solution on your problem.

NI Fbus Configurator and Windows 7 Compatibility

Will NI FBUS Configurator 3.2.0 works with Windows 7? If not, is there an upgrade path? We are using a NI PCI FBUS card.
If an upgrade is required, is it software or hardware or both that is upgraded? What is the cost to upgrade?
Solved!
Go to Solution.

Configurator 3.2.x does not support Windows 7. You can upgrade to Configurator 4.0.1. Only the software needs to upgraded.
The cost of the upgrading is much lower than purchasing a new license. Please contact your local NI sales representative for more information.
Feilian (Vince) Shen

NI-FBUS Process Startup: Fatal Error

I installed PCI-FBUS card, NI-FBUS COMM SW for Windows v 3.2.1 (CM and Configurator) on my Windows XP, activated the licenses and enabled the PCI-FBUS board through Configuration Utility. When I started NI-FBUS Communication Manager, I got the following error:
"NI-FBUS Process Startup: Fatal Error
Initialize request to Board 0 timed out, NI-FBUS may not be receiving interrupts from board. Check your board IRQ settings with the NI-FBUS interface configuration utility. NI-FBUS will not Exit."
All the settings in the Configuration Utility were set to default. The NI-FBUS Communication Manager will only run successful if H1 interface board properties is set to "Polled Mode." How do I fix this issue?

Hi, I asked the guy who developed NI-FBUS 3.2. They told me this is a history problem, when Windows OS is upgraded to XP or above, the IRQ mode is not suggested to use any more. So from the NI-FBUS 4.0, they removed IRQ mode supporting. It is strongly recommended using poll mode in NI-FBUS software.

Dell optiplex 755 won't boot with NI PCI Fieldbus card installed

After installing NI Configurator 3.1.0 on new Dell optiplex 755 and then installing the NI PCI Fieldbus card the pc won't boot up.
This card works fine 745 and older dell pc's.
Anybody else having this problem?

Hi,
In which step does the boot process fail? Is there any error message?
After installing NI-FBUS 3.1, please go to Windows Device Manager, check whether the driver of PCI-FBUS is correctly installed. There should be no any error in Device Manager.
You can try the following methods.
1. Change to another PCI slot.
2. Use Windows XP. NI-FBUS 3.1 does not support Windows Vista.
3. If there exist other PCI devices in the system, remove them and try using PCI-FBUS only.
4. Update the drivers of Dell Optiplex 755 if there are new versions, including video card, ethernet card, etc.
Feilian (Vince) Shen

Activation process will not recognize s/n as correct

I have installed the software but when I try to retrieve the activation code, an error comes back that the serial number does not match the product. I have the serial number right on the certificate of ownership, and all of the information pre-populated so I don't know what is going on.
I really need to get this card working.... frustrating!

Hi,
The activation request is only for NI-FBUS Configurator. Please check which software your serial number belongs to on the certificate of ownership,
If the software is NI-FBUS COMM SW (Communications Manager), please ignore the activation request. NI-FBUS Communications Manager is free and does NOT need activation. It provides drivers for interface card (PCI-FBUS and PCMCIA-FBUS) and APIs for accessing FF network.
If the software is NI-FBUS CONFIGURATOR, please send your serial number to [email protected] We can help you check the activation problem.
NI-FBUS Configurator needs extra purchasing and activation. You can use evaluate version if you did not purchase Configurator. Configuator evaluate version only supports offline configuration.
Feilian (Vince) Shen

Offline Interface

I have updated the NI FBUS Configurator from version 3.1 to version 4.1.1 and now there is no offline interface available anymore.
Is there a way to activate it in "Interface Configuration Utility"? I am using the PCI FBUS/2 Card.

Hi,
"Add Interface wizard" is a legacy tool, which is also included in version 4.1.1
"ICU" is the new tool to do the trick.
If you have upgraded from 3.1 to 4.1.1, you should see "Interface Configuration Utility"(ICU) in the Utilities folder. (see attached screenshot)
Attachments:
icu.png ‏12 KB

What does label mean on step 3 of 1-click?

When in 1-Click for orderinng photos, what does label mean for step 3 under shippingg address?

Hi DougS,
You are right, it is "LM", which stands for Link Master device. On the other hand, you can also change the device type to Basic Device by choosing right-click menu item "Change Device Type" in NI-FBUS Configurator 3.1 version.
To answer your last question: Yes, National Instruments has been supporting this product all along; in fact, the latest version of NI-FBUS Configurator is 3.1, which supports off-line configuration and supports many new interfaces like PCI-FBUS, PCMCIA-FBUS S2 and HSE/H1 linking device.
Please feel free to contact us if you have any question on NI fieldbus products. You can just send e-mail to "[email protected]", we'll be happy to help you out.
-- NI Fieldbus Support Team

Bus Down while accessing FF Bus using NIFBus Configurator

The following configuration applies to the control system in my plant
DCS Controller - ABB AC800M
Foundation Feildbus Card - CI852
Fieldbus devices on the bus - Emerson pressure Transmitter (2 Nos), Temperature Transmitters (2 Nos) and Siemens Sipart PS2 FF actuators (2 Nos)
While plugging and starting the NIFbus with the bus plugged in the port, All the devices go out of scheduling and report fault on the DCS controller(they actually go to OOS mode), however if one waits (for 2-3 minutes) the devices sometimes come back on the bus with auto mode. The above situation happens when the fieldbus is plugged out or NIFBus stopped.
This causes undesirable delay in the process as the due to OOS mode the DCS is unable extract data and stops the process (correctly so)
What can be the possible cause of the problem and what is the remedial solution.

The problem has to be restated as : The fault situation in DCS i.e DCS (ABB ACS800M PM864A processor with CI852 FF card) reporting that it is unable to see any FF Devices on its network (error as in DCS 'Device not found') happens when the comm manager is started/stopped or when the FFBus cable is plugged / unplugged on port 0/1 with the comm manager running. It does NOT happen with NIFbus start/restart as stated earlier.
Sorry for the goof - up
The card in use is NI's PCI-FBUS and typically when the situation as stated above happens the DCS is unable to see any devices for 1-2 Minutes and after the time some device come back on the network and some devices do not (typically SIPART PS2 FF - it will never come back on its own having lost comm with DCS). To bring back the device on the network, original state has to be restored, i.e. if the cable was unplugged then the cable has to be plugged back and the comm manager has to be restarted again, or if the comm manager was stopped it has to be started again and etc.
The MODE_BCK.TARGET = Auto is always true, the actual state is not known at that point of time as NIFBus is updating itself ( comm manager is started by starting the NIFBus).
ABB was reported with the problem, and they apparently found nothing wrong at thier end
Attached are the bitmaps of the NIFBus tree, with devices , (P = Pressure Tx, T= Temp Tx)
At the end while discussing the same among colleagues it was felt that the behaviour is due the fact that the PCI-FBUS is configured as LAS, however changing the same to simple device (from 'configuration utility') did not help. Actually NIFbus did not start since the comm manager did not start - just a raw discussion, you may ignore this
Thanks and regards
Amar
Attachments:
ni.com.zip ‏131 KB

Has anyone gotten the FBUS PCMCIA card to work on a PCI to PCMCIA adapter board?

I have lots of success with the PCMCIA card in laptop PCMCIA slots, but no luck with the PCMCIA card in a desktop PC with a Quatech PCD-B/PCI-E PCI adapter for PCMCIA boards. I am thinking that my problem resides with the adapter board but I would like to know if anyone has had success with the FBUS series 2 PCMCIA card with a PCI to PCMCIA adapter. I got a WinXP SP2 IBM ThinkCentre desktop. Thanks

We have ever used some PCMCIA to PCI adaptors, they are working properly with NI PCMCIA-FBUS card as well as NI-FBUS software.
I'd like to recommend the single CardBus PCMCIA slot adaptor from Elan Digital System:
http://www.elandigitalsystems.com/adapter/pci.php
We have used the adaptor in a Dell Dimension desktop, running XP SP2, and NI-FBUS Configurator 3.1.1 runs well.
Another adaptor is a long card, which is Gigabyte GA-MPCI, it works well with some old desktops, but the length of the card is about twice of the card of Elan Digital System; it might not fit your requirement.
Hope it helps.

PCMCIA-FBus Series 2 is not recognized under Windows XP

I'm trying to get a PCMCIA-FBus Series 2 card work under Windows XP Professional SP2 toghether with an Elan P111 PCI to PCMCIA Adapter, but when I plug in the card Windows does not recognize it - I only get a "pcmcia unknown_manufacturer" message and no driver is installed.
I've tried to install the driver manually, but then I get an error code 10, Device could not be started.
The Computer is a Dell Optiplx 740, AMP Athlon 64 X2 3800+. NI-Configurator v3.1, v3.1.1 and v3.2.1 have been tested. The Elan P111 driver is PSeries v5.07.08.

Hi,
I am not sure whether this PCI-PCMCIA adapter works well with Windows XP SP2. I suggest that you also contact the adapter manufacturer for the compatibility issue.
We did do some test on Elan PCI-PCMCIA adapter, but I am sorry that we are unable to make verifications on all kinds of hardware and software combination. There exists the possibilities that the adapter does not work on some PC's.
Another suggestion that you can try is to install the PCI-PCMCIA adapter driver on a clean Dell Optiplx 740 (Windows XP SP2 without Microsoft hotfix ). I think this can help you identify whether there are compatibility problems between the adapter and system.
Regards
Feilian (Vince) Shen

PCI -FBUS

Similar Messages

Maybe you are looking for