Jump to content

Envisalink 2DS


Recommended Posts

Posted

Hi all....

 

I recently purchased a Envisalink 2DS Internet/Ethernet module for my DCS alarm system. Although it has remote access capabilities I would still like to interface it with my 99i (like flashing all lights when intrusion is detected, arm / disarm thru 99i). That being said, and assuming I need to purchase the network interface module for the 99i, does anyone have a "clue" as to how I would do this. I am a jack-of-all-trades and master of none (I program PLC's and operator interfaces 'n stuff). I am not really "up" on opening up TCP ports, establishing connections etc. I did manage to find some documentation on the Envisalink TPI which does contain what I think is the rudimentary message structure (CMD, DATA, CHKSUM, CR/LF) and commands.

 

Ideally I would need to be able to send commands and recieve status messages from the unit.

 

If I'm barking up the "impossible tree" let me know. Hey....just point me down the right road and I may figure it out. Any comments are sincerely appreciated.

 

Cheers.....

:shock:

M.A.

Posted

Hi M.A.,

 

Thank you. I just got it and it seems that ISY has to maintain a persistent socket connection ... this is not something that ISY can currently do (unfortunately).

 

Have you checked out DSCLinc?

 

With kind regards,

Michel

Posted

Michel

 

Thanks for that....I just don't want to stick a PC in the middle of my "control network" to perform tasks. Being into industrial automation, I typicall don't like doing "controls" thru a PC.....but that's just my opinion

 

Anyways....I'll trudge along with the "web enabled" interface of the 2DS for now I guess.

 

Your efforts are none-the-less appreciated

 

Have a great day....

 

M.A. :shock:

Posted
Thanks for that....I just don't want to stick a PC in the middle of my "control network" to perform tasks. Being into industrial automation, I typicall don't like doing "controls" thru a PC.....but that's just my opinion

Marc,

I come from industrial automation as well and 10 years ago, I would have agreed - no computers.

In reality everything these days is a computer and there is device layer upon device layer talking to make a system work. Times are changing.

Take Siemens or AB for example... PLC is really an embedded computer (with firmware) talking to a drive (another computer and firmware) communicating via some other device (with firmware) via some protocol (such as Profi, DN, MB, OPC, etc) to an HMI, which is really just an outdated Windows embedded machine running some other software.

I've installed precision (0.5um accuracy) multi-axis tools into major fab plants that run completely custom .NET HMIs talking to QNX computers used as controllers.

 

Anyways, your choice. I have a 2DS arriving shortly and I'll be adding support to DSCLink in case you change your mind.

Posted

I can certainly understand people's hesitation for running a 24-7 PC.

For me, it just makes sense. I run a HTPC machine 24-7 anyway, and having the machine running allows me run about a dozen various "Link" programs to connect my home.

I use a low power PC that only pulls about 25W on idle. An Atom based PC would be even less.

  • 1 year later...
Posted

Gelecek HMI Components

http://www.geleceksoftware.com

There was a userfriendly OPC client.

http://geleceksoftware.com

 

I have seen a new HMI components company. All components are OPC Client too.

I mean you can write read bind to OPC Item (PLC address) via these components.

I integrated to Visual Studio easily that components and I did not write any code..

That company(Gelecek Software) made some videos about usage and demo version of components.

You can try easily. Any way give you some screen of my project..

 

2eyxu2e.jpg

Guest
This topic is now closed to further replies.

  • Recently Browsing

    • No registered users viewing this page.
  • Forum Statistics

    • Total Topics
      37k
    • Total Posts
      371.5k
×
×
  • Create New...