Support

If you have a problem or need to report a bug please email : support@dsprobotics.com

There are 3 sections to this support area:

DOWNLOADS: access to product manuals, support files and drivers

HELP & INFORMATION: tutorials and example files for learning or finding pre-made modules for your projects

USER FORUMS: meet with other users and exchange ideas, you can also get help and assistance here

Experience with Newport Omega UWTC temp transmitter?

Discuss Control Systems here

Experience with Newport Omega UWTC temp transmitter?

Postby jjanson » Thu Apr 12, 2012 3:33 pm

Hi does anyone have any expierences with Newport Omega UWTC REC3/N and UWTC-2 wifi sensor?
My attached scheme works that i can open and close the port.
But sending commands goes wrong and flowstone locks up. Like readout or password.
Via the webbrowser all works well and i can enter the server directly.

The manual of the device does not give me very much more details.

Any idea if the codes send should be binary or hex or just ascii ?

thanks for any help.

regards,
Jerry
Attachments
UWTC-client.fsm
(15.78 KiB) Downloaded 899 times
jjanson
 
Posts: 10
Joined: Wed Apr 11, 2012 12:05 pm

Re: Experience with Newport Omega UWTC temp transmitter?

Postby DSP » Sat May 19, 2012 5:23 am

Looks like it is ASCI to me, I found a manual here:

http://www.newportus.com/Pdf/M4620n.pdf

I think as you say you need a more complete data structure with unit ID and password etc.
DSP
 
Posts: 150
Joined: Fri May 14, 2010 10:55 pm

Re: Experience with Newport Omega UWTC temp transmitter?

Postby jjanson » Tue Jan 15, 2013 12:50 pm

It has been a while but finally it succeeded.
It is in the manual, but when reading it you might not notice.
For people who have such a device and like to experiment with it.
The commands to send to read out the sensor need a * in front of it:
*SRTC to read out degrees in celcius (*SRTF for fahrenheit)
*SRHb for pressure in mbar
*SRH2 for humidity in %
etcetera.
Then it won't give a time out. so simply use the network module, add the port 2000 and the ip nr you've programmed in the sensor/server and send the text command.
see picture

regards.
Attachments
Capture.JPG
read out omega newport sensor
Capture.JPG (81.34 KiB) Viewed 17110 times
jjanson
 
Posts: 10
Joined: Wed Apr 11, 2012 12:05 pm

Re: Experience with Newport Omega UWTC temp transmitter?

Postby jjanson » Tue Apr 23, 2013 2:26 pm

Hi, now after a while working with and bug finding i noticed a few things.
We have 2 of these envrionment readers, same type but different firmware 1.5 and 1.9.
The fault is that sometimes there is no network connection.
But when accessing via Internet explorer i can acces them both.
After a reset of the devices flowstone can reach them again.

So it seems not a firmware issue as they differ, unless the same fault is in both firmwares.
But with NO reset i CAN acces both via internet explorer.
So now it is a bit confusing were to find the fault, is it flowstone or is the devices.

My guess is that it is flowstone because i have the fault with both devices.

It is very simple connected just an ip adres and a port number, then there a commands send to the reader.

Anyone who had same issues with network setups?
jjanson
 
Posts: 10
Joined: Wed Apr 11, 2012 12:05 pm

Re: Experience with Newport Omega UWTC temp transmitter?

Postby jjanson » Mon Aug 05, 2013 7:26 am

The solution to network dropout was to change the port to 1001.
So it was not a fault of Flowstone.
But the sensor dropped the connection after a while.
jjanson
 
Posts: 10
Joined: Wed Apr 11, 2012 12:05 pm

Re: Experience with Newport Omega UWTC temp transmitter?

Postby jjanson » Thu Dec 05, 2013 8:19 am

Hello,

with the network client there must be some kind of bug.
Several times when accessing 1 of the environmental meters we have, we do not get access with the flowstone program.
We also have a separate (pc)servers which is logging the environmetal meters values continuesly thru the day which has always access. Also the server itself (which is built in the environmental meters) are always accessible via their own webpage/address.
The meters are setup to have multiple accesses from different users who can all use the same port on the ip address.
Strange thing is when ressting or repowering the Environmental readers, then Flowstone can suddenly access the readers ???
How can this happen? It seems not to be a failure from the readers itself because they are allways accessible via their own webpage and other used server software(c++/Java) but not always via the client network module in Flowstone.
The client is just simple setup with a IP adress and a port 01001. send a read command and then receive data.
Anyone any idea?
jjanson
 
Posts: 10
Joined: Wed Apr 11, 2012 12:05 pm


Return to Machine Control

Who is online

Users browsing this forum: No registered users and 2 guests