I am developing a RS485 multi-drop half duplex network (single pair) of smart seismic

[drum_yogi]

sensors and I am considering using Labview (along with bridgeview) to act as the host (master) for all network communications and data processing. However I not a Labview user and I am not sure how much work it would require to create the necessary driver
software to make it all happen. Currently my sensor software is operational and the host
software is on a QNX (RTOS) platform using a standard PC. I have designed a parallel port
based interface that uses a SCC2691 UART transceiver to interact with the network.Can Labview/Bridgeview provide a viable network communication to my
network and what hardware and/or software protocol requirements must I follow to a
dapt my
environment to labview. Is there a guide available to write a driver for such an application and does Labview come with all the necessary tools to do so?

[Doug C]

Hello,
NI uses C or Assembly or something real low level to write their low level drivers. For example to talk to a DAQ card they have a driver Ni-DAQ which is in the format of a .dll. Then they use LabVIEW to talk to the driver at a higher level. So, using LV as a low level register level programming langage I think that you will have a very hard time. If you write a register level driver and call the library with LV for a user interface then I think you will be happier. Here is a link to talking to external files in LabVIEW:
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/a6705fec7ea42300862567b70054206e?OpenDocument

Now LV has a feature built in called datasocket that will allow you to publish data out to a network and you can use LV to read
that data as well.
Doug