I'm sorry. I was the one who jumped to the conclusion that it was Hart protocol.
You are using in USB/RS-232 converter. I assume you see this as another Com port on your computer. I've used these devices before without problems, those a few people on the forums have said that certain brands just haven't worked for them.
As I said before, double check all the baud and parity settings. Double check that you have the right cable, whether it need to be null modem or a straight through cable.
Check that you are actually sending out a CR character at the end of your string. Do you need to send a capital T or a lower case t. That actually messed me up for a few minutes recently on a device I was trying to communicate with. t<CR> should look like t\r if the constant you are writing is set to \codes display or 74 0D (lower case t) or 540D (upper case T).
Is the device set up to return a line feed in its response? Have you provide enough of a delay between the VISA write and read to give the instrument time to send the response?
Try things in hyperterminal. It is a simple place to start to see if you have basic communication there. If you do, then you can focus on the LabVIEW. If you don't, then you know the issue is with the wiring, device, or Windows driver or settings.
Are you using the basic LabVIEW VI's for Serial Read and Write or VI's that from somewhere else? You said "I'm wondering if LabView's VIs are feeding the newer information in the old format or something like that." LabVIEW is only going to send out whatever you tell it to send out.
Sorry it's a bunch of questions rather than answers, but hopefully it gets you looking in different areas that you may not have thought of.