LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Help with old Omega Temp logger

Hello,

I have a customer who has some Omega data loggers that are about 12-15
years old. These are serial interface. They each have 20 thermal
couple hook ups to them. I'm trying to interface to the serial port but
get nothing in response despite any efforts. They did work at one time
(maybe 6 months ago) so I assume its on my end. I'm using the visa
serial VIs, using LV7 and Windows XP.

Anybody out there have something similar that they could share some VIs
or tips with?




--
"Those who make peaceful revolution impossible
will make violent revolution inevitable."
--John F. Kennedy
0 Kudos
Message 1 of 6
(3,298 Views)
I hate answering with a question, but if it helps you find a quick solution, it should be okay, right? ;o)


Are you able to communicate with the Omega data logger using a standard serial communication software, such as "HyperTerminal"?

You may try with slower comm port settings, such as 2400 or 4800. I can't remember the speeds back then, but I do remember the data loggers. The problem may be a simple port setting. If you have the manuals, look up the speeds. I seem to remember that they were quite slow (900??? or 1200???). Check also the parity, data bits and stop bit settings. I can't remember what they were.

Good luck and hope you get them back up & running.
It brings back memories... 🐵

-JLV-
0 Kudos
Message 2 of 6
(3,298 Views)
Check out this link..

It may contain your answer:

http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RPAGEID=135&HOID=506500000008000000123B0000&UCATEGORY_0=_49_%24_6_&UCATEGORY_S=0&USEARCHCONTEXT_TIER_0=0&USEARCHCONTEXT_TIER_S=0&USEARCHCONTEXT_QUESTION_0=Omega&USEARCHCONTEXT_QUESTION_S=0

-JLV-
0 Kudos
Message 3 of 6
(3,298 Views)
JoeLabView wrote:
> I hate answering with a question, but if it helps you find a quick
> solution, it should be okay, right? ;o)
>
>
> Are you able to communicate with the Omega data logger using a
> standard serial communication software, such as "HyperTerminal"?
>
no
> You may try with slower comm port settings, such as 2400 or 4800. I
> can't remember the speeds back then, but I do remember the data
> loggers.
Here is what the quick basic program had:
OPEN "COM1:9600,N,8,1,LF" FOR RANDOM AS #1
PRINT #1, "TS0"
PRINT #1, CHR$(&H1B) + "T";
PRINT #1, "FM0,01,20"
LINE INPUT #1, D$

The problem may be a simple port setting. If you have the
> manuals, look up the speeds.
I seem to remember that they were quite
> slow (900??? or 1200???). Check als
o the parity, data bits and stop
> bit settings. I can't remember what they were.

so from the original program that worked (on a DOS 5 machine!) the baud
is 9600, No parity, data bits is 8, 1 stop bit. The LF is assumed to be
the terminator.

I use the serial port init for the open line leaving terminator unwired.

Then I use visa write and send using \ codes:
TSO\r\n\1BTFM0,01,20\r\n

read just times out 😞

Tried leaving out \r but no luck. even tried without \n but no luck.

BTW, model number is RD3750 (which google and the others return nothing
on. Omega site has nothing on this old sucker).

BTW also, I have two of these in the set up and neither is playing yet.
>
> Good luck and hope you get them back up & running.
> It brings back memories... 🐵

Anything else you could remember pass it on.

Thanks,
Jim
0 Kudos
Message 4 of 6
(3,298 Views)
JoeLabView wrote:

> Check out this link..
>
> It may contain your answer:
>
> http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RPAGEID=135&HOID=506500000008000000123B0000&UCATEGORY_0=_49_%24_6_&UCATEGORY_S=0&USEARCHCONTEXT_TIER_0=0&USEARCHCONTEXT_TIER_S=0&USEARCHCONTEXT_QUESTION_0=Omega&USEARCHCONTEXT_QUESTION_S=0
>
> -JLV-

Saw that one. Tried hex and \ codes so that isn't it. Did the
loopback test and all is ok. connected two serial ports together and
talked back and forth.

These omegas must be particular about something. I'll just keep banging
on them, hopefully I'll crack the secret code.

Thanks,

Jim
http://www.effectivetest.com
0 Kudos
Message 5 of 6
(3,298 Views)
Has anyone come up with a solution to this problem? It seems like I am having the same problem with DP40 temperature indicator. It works fine using an older version of Labview (4.x). But since we upgraded to 7.1, I have had the same problem as described in this thread. I can open up Labview 4, and communicate with the instrument, but when I open up labview 7 on the same computer, I get a parity error or a timeout error. Any Ideas?
Thanks
Dave
0 Kudos
Message 6 of 6
(3,298 Views)