Support Forums
Programming DT80 & 800

Hi Guys

I find myself in need of interfacing with the loggers directly in real time with my own system to read from and instruct the loggers and other hardware.
Based on readings from 1/2 a dozen sensors on the two data takers and some logic in my software I need to set the state of digital ports (which are driving relays) and control other non Datataker equipment and need to bring it all together and not have a hacked together solution. I am aware that your DEtransfer and DELogger expose DDE interfaces and I have been able to use this interface successfully in .net, with some difficulty however as DDE is very old / clunky / slow and depreciated. I have also somewhat successfully interfaced with the loggers via RS232 with a usb to serial port cable and perl on my linux machines however its not really what I had in mind either.

I would really like to connect to the loggers via tcp and was hoping that you have an API for .Net or any other architecture for that matter. I note that there was an OXC com interface for vb6, which is pretty much to old and depreciated as well, is that what the Delogger software was built on? I suppose that my main question is what is the list of interfaces available to us so that I can select the right method before continuing any further, and are there any up to date API's.

Cheers
Ben

Hi Guys I find myself in need of interfacing with the loggers directly in real time with my own system to read from and instruct the loggers and other hardware. Based on readings from 1/2 a dozen sensors on the two data takers and some logic in my software I need to set the state of digital ports (which are driving relays) and control other non Datataker equipment and need to bring it all together and not have a hacked together solution. I am aware that your DEtransfer and DELogger expose DDE interfaces and I have been able to use this interface successfully in .net, with some difficulty however as DDE is very old / clunky / slow and depreciated. I have also somewhat successfully interfaced with the loggers via RS232 with a usb to serial port cable and perl on my linux machines however its not really what I had in mind either. I would really like to connect to the loggers via tcp and was hoping that you have an API for .Net or any other architecture for that matter. I note that there was an OXC com interface for vb6, which is pretty much to old and depreciated as well, is that what the Delogger software was built on? I suppose that my main question is what is the list of interfaces available to us so that I can select the right method before continuing any further, and are there any up to date API's. Cheers Ben

Good morning Ben,

DeLogger is now a discontinued product having been replaced by or web based interface dEX.
Web based applications free us from the restrictions of WindowsAPI's and allows any user with a web browser to interface to our equipment.

We do have LabVIEW drivers available for those who want to do their own application.
You can also use the DT80 Modbus capabilities and a SCADA package to talk to the DT80 and other Modbus devices.

Cheers,
Roger

Good morning Ben, DeLogger is now a discontinued product having been replaced by or web based interface dEX. Web based applications free us from the restrictions of WindowsAPI's and allows any user with a web browser to interface to our equipment. We do have LabVIEW drivers available for those who want to do their own application. You can also use the DT80 Modbus capabilities and a SCADA package to talk to the DT80 and other Modbus devices. Cheers, Roger

Great, Ill look into the Modbus and Labview options.
Does your DEX system expose some kind of streaming output that can be monitored?

Cheers

Great, Ill look into the Modbus and Labview options. Does your DEX system expose some kind of streaming output that can be monitored? Cheers

Hi Ben,

The command port is a Telnet session available on Port 7700.
Modbus is on port 502

V9.08 firmware can also FTP and email data.

Cheers,
Roger

Hi Ben, The command port is a Telnet session available on Port 7700. Modbus is on port 502 V9.08 firmware can also FTP and email data. Cheers, Roger

Roger,

I have had a quick look at the MODBUS, I think it will be my ticket - Thanks.
I haven't checked out the LabView drivers yet but the MODBUS solution looks like the go an I will assume that you will be carrying this interface through your future products as well so this is where I will invest my time.
Thanks again for your great support and a fantastic product.

Ben Harper

Roger, I have had a quick look at the MODBUS, I think it will be my ticket - Thanks. I haven't checked out the LabView drivers yet but the MODBUS solution looks like the go an I will assume that you will be carrying this interface through your future products as well so this is where I will invest my time. Thanks again for your great support and a fantastic product. Ben Harper

Hi Ben,

Thought it might do the trick.
Drop me an email to the Australian support email address and I'll send you a couple of documents on using MODBUS master and slave.

Cheers,
Roger

Hi Ben, Thought it might do the trick. Drop me an email to the Australian support email address and I'll send you a couple of documents on using MODBUS master and slave. Cheers, Roger
65
5
2
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft