Fanuc 1553 card problems

[nowellj]

Hello,

     Has anyone worked with the GE Fanuc line of MIL-STD-1553 cards?  I'm working on a 1553 communication system and have encountered a problem where the card will repeat messages within a minor frame.  For example, my test program consists of a minor frame with only two messages in it, a BC to RT and an RT to BC.  The messages are supposed to alternate throughout the program execution.  However, sometimes a message will repeat itself.  I should be seeing something like this:

BC to RT

RT to BC

BC to RT

etc.

Instead, I see this (representative, not exact)

BC to RT

RT to BC

RT to BC

BC to RT

etc.

  I'm using the QCP-1553 card with the LV-1553 driver/VI package.  If anyone has an information I'd appreciate it. 

[Caleb_W]

Hi nowellj,

While I haven't specifically worked with this card before, are you getting any kind of error on the line when the message duplicates itself.  There may be an incorrect parity or non-printable characters that aren't transfering properly.  The device could be resending the data if an error is detected (even though the message appears to have transferred correctly)

[Clint Eastwood]

Can you provide any more info on 1553 using Labview?? I know NOTHING about 1553.  Where did you get the LV-1553 driver/VI package ??  I'm using the Data Device Corp         BU65569 card in a National Instruments PXI Chassis.  The only expierence I have is with RS422 and one of the VIs that ships with Labview to send and rec a simple string message. Sent on COM3 and RECV'd on COM4.  Do I need to get as low as Bus Controller ( whatever that is)??

 The manufact site was of no help.  Will MAX recognize the DDC Card in a National Chassis????

Thanks.

Clint

[Caleb_W]

Hi Clint,

National Instruments doesn't have an instrument driver for that device, but I found a fourm post on here that has a link to a third party driver.  It can be found here: http://forums.ni.com/ni/board/message?board.id=170&message.id=30574&view=by_date_ascending&page=1 Third party serial devices do not generally show up in MAX, but you can use the VISA Driver Development Wizard to use your card.  You can get more information here: http://digital.ni.com/public.nsf/allkb/7EC0237A162F1D17862568A1007B88DA?OpenDocument

[Clint Eastwood]

Thanks Caleb !

[nowellj]

Clint,

If you need more information about the 1553 protocol, there are several white papers on the Internet that give an excellent overview of how the protocol functions.  There is one on GE Fanuc's website that is very thorough.  As for the LV-1553 library, these are LabVIEW VI's that GE Fanuc has created for their cards and drivers.  They're essentially LabVIEW wrappers around the normal C API they provide.  I doubt it would work with the DDC cards that you have.  I believe DDC provides LabVIEW drivers for their cards, along with the corresponding VI's (I could be mistaken), but the VI's and the drivers are not LabVIEW RT compatible.  I hope this helps you.

[jakidd]

I am using the GE Fanuc QCP-1553 with LabView successfully, if you are still having problems with it let me know and I can help out.

[TANDERJASKA]

Josh,

Are you using the real-time OS for the GE fanuc 1553 card?  I have just purchased one and am a little apprehensive about how well it will work...I have not rcvd it yet

[nowellj]

I am using the Fancu 1553 card with the Real-Time OS.  So far, I haven't had any problems with the two.  Keep in mind, some functions of the API aren't going to work under the OS, as they wrap C-functions that use Windows specific calls.  Sadly, they're really useful ones too.  I think one of the functions that won't work is one that will print out the current memory contents.

[TANDERJASKA]

Thank you for you response. Is the real-time as deterministic as they suggest? GE Fanuc will not let me download their drivers until I purchase, would you happen to have any code you could share? I will have one PXI as a BC and another as a RT that will integrated with four RS422 ports. I would like to chat with you in the future, anyway I can contact you? Again thank you for your time