Michael,
Thank you for your reply. Straight forward project? I don't think so! I would hate to see what you consider difficult! I AM the person who took the project from schematic to working prototype, nine years ago! You forget a great deal in nine years. On top of that, I am not and never have been or never considered myself a programmer. I did develop some of the code, but not the working GWBASIC program 1UMAIN.ASC nor the overlays. As you may know, GWBASIC is not supportable any longer so I am forced to "port" the code to another program. I am not proud, or have a problem with "Not Invented Here". Feel free to dive right in and give me some pointers on how to structure and write the Labview code. I took a shot at it the last few days, and you will find that work attached. See if that makes any sense to you and give pointers. The hardware interfaces are another matter entirely. I was thinking of adding a USB to Serial port dongle as a way to talk to the serial ports. I used that method on a laptop to talk to a STB I recently purchased with a DB9 serial port and poor to no instructions. I have tried to communicate with the test set with a desktop and a laptop running Windows XP, desktop with serial port and null modem cable, laptop with USB to serial port dongle and null modem cable. Both units running Procomm Plus for Windows DIrect COnenct COM1 does "see" the test set, but there are other problems in that I do not get the proper response from the test set in the GWEBASIC software, so why would Labview be any different? I have to figure why that is the way it is later this month when another person takes a looka t my lab setup, maybe I have some hardware conencted improperly. I could definitely use the help. This is an unpaid lab learning project and I want to learn Labview. Take a look at my attachment and see where I could start writing Labview code equivalent to the GWBASIC code. Thanks for the help. I need to learn Labview for a potential new job anyway.
railman99
Download File:post-5126-1149092287.txt