Conversion of GWBASIC Code to labview 7.1 code

[railman99]

I am a newbie for Labview and need some help. I have an old prototype telephone line test set I designed and built 9 years ago which runs under GWBASIC and DOS 6.22 on a half-length ISA-Bus single board 386 legacy computer. The test set is designed using all discrete CMOS components, 8 bits, with no surface mount or PLD, FPGA, ASIC parts.

I have not touched the test set in 9 years, and my current task is to complete the prototype engineering on the test set. This includes writing the operational code in a supportable language (C++, C#, Labview, etc); adding USB and Ethernet interfaces to the test set (which currently only has DB25 RS-232 serial ports); and "prettying" up the external mechanical packaging. The test set operates either by a user locally connected through a VT-100 emulation craft terminal, Hyperterminal, or Procomm Plus; or through a Telnet session through the built-in Bell 212A 1200 Baud modem over a dial-up comm link.

The user sends out string commands to the serial port and the test set responds with string commands and test data returned to the local single board computer VGA/EGA monitor. The task is to write Labview code to operate and run the test set.

I attach the earlier GWBASIC 1UMAIN.TXT GWBASIC program with 4 overlays and string commands emnbedded at end of listing as reference. Please help.

railman99

Download File:post-5126-1148578833.txt

[Michael Aivaliotis]

This seems like a pretty straight forward project. The fact that you are the original designer should make things a lot easier. I could probably solve this problem for you and write all the software and design\build your hardware interfaces, but I assume you want to do all that yourself right? If that's the case then I would suggest you do some Googling around. There are some ethernet and usb "interfaces on a chip" that you could probably purchase that would do the trick. If you want to make it easier you could probably use a USB to serial dongle. As far as the LabVIEW, try opening up your examples. There are several serial examples that could get you started. I would suggest you try to communicate with your exisitng hardware through the rs232 first and make sure that works before you upgrade to USB or ethernet.

So... please try a few things out and if you get stuck come on over and we'll try and help you out.

[railman99]

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

[Michael Aivaliotis]

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.

There's not much I can do for you in regard to this. It's too bad you didn't leave better documentation.

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.

Hmm, this is new information, your original post didn't indicate that, in fact it sounded like it was all you. If you are not a programmer and cannot decifer the GWBASIC code then there lies the proble.

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.

Perhaps others can help, unfortunatly this is above and beyond where I draw the line on my help. If you are in the northern California area, you can contact my employer: http://jameskring.com and we can arrange an on-site visit.

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?

Again, new information not given before. If you can't communicate to the test set using Procomm then of course, LabVIEW will not either.

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.

I guess you better roll-up your sleeves, you gotta lot of work to do. I have no clue, without seeing your setup what might be the problem. It also sounds like there is little to no documentation. Again, I'm sorry I can't be more help but there are 4000 other registered board members that may have some idea.