York ISN Driver

[kcrabill]

I am looking into the possibility of using a driver to connect york linc devices to Tridium which I believe is their ISN protocol version 4.0. Has anyone been able to intregrate tridium and their Linc devices. Here is one of the packets that I scanned out.

02 80 BE 80 84 D7 81 FF 50 30 31 20 54 45 4D 50 30 20 20 20 20 20 20 20 20 20 20 36 39 2E 37 44 45 47 0D 97 03

Kevin

[botech]

Botech has a gateway for it
www.botech.se

[b-man]

kcrabill

Asked this same question in a thread a couple of months ago. I was already aware of a company, I think in England, that had some interfaces that Tridium might be able to see . Unfortunately they weren't for the revs I have. Give them a try.
http://www.northbt.com/driver/YorkISN
What are you trying to talk to? Post a reply if you have any luck.

b-man

[kcrabill]

The device I am trying to talk to is central linc unit that is connected to a computer that has a software on it called york facility manager. The version on the central linc says it is 4.1A. We talked to york and it says it was made between 93 and 94 and that they don't have any more for purchase since they stopped making them. The thing I have noticed is that I can read the messages from the computer when the wires are negative to negative and positive to positive. To read the messages from the device I have to do negative to ground and the positive to negative on the serial cables. I have an example of the newer ISN protocols through Tridium R2 integrations but the older version acts a little different.

[whatusi]

the york linc central is a gateway device that does just that lincs you to another cpu like a 1095 board or a 1065 board what is the linc attached too :cool:on the 485 side

[b-man]

Actually, I believe the Linc Central is the linc between the York ISN Protocol 485 network and the 232 port of a computer workstation. krabill, you said you already have examples of integrations to Tridium R2. What protocol or rev controller were you going to? Was it Bacnet, or just a later version of ISN?
b-man

[kcrabill]

The R2 integration was using a later version of ISN, because the packets are very close in nature but slightly different. The unit is a central link unit. The issue I am having is that the unit is receiving packets but the receive lights are not lighting up when using the driver. yesterday, I tried using a different rs232 to rs485 adapter on the PC and got slightly different results. The data on the PC doesn't update but the central linc still has all four lights firing.

[YorkieUser]

Kcrabill

Maybe too late, but for what it's worth...
as you say, the Linc Central uses the earlier V4 comms on both ports.
The Linc UCS 232 has the ability to switch the network protocol between 19k2 (V4) and 50k (later UCS protocol) however, the RS232 side is fixed as the later protocol, re-formatting the messages if needed, and will probably work with your previous driver.

[oldertech]

My knowlege of Conrols is limited but I may be able to help. York's internal language is modbus. There is free software for connecting through the RS485 connections using a converter to RS232. The free software is intended for initial programming and is called Simplicity PC. It can be downloaded here: http://www.yorkupg.com/software.asp York used to sell modlic for connecting to backnet and now has their own board called yorklinc.
I should say this all applies to today's unitary products.

[YorkieUser]

Oldertech

As regards the modbus protocol - this only resides in the ISN controllers from UCS onwards and then only on the RS232 port.
If I am reading kcrabill correctly, he already has a RS485 network system using a 4.1 version Linc Central.
This means that the protocol on the RS485 network is Version 4 communications and that his controllers would be Release 4 or possibly Release 6.
The protocols for the LAN in these releases are entirely proprietary.

The Facility Manager connects via RS232 to the Linc and uses either R4 or UCS protocol to speak to it depending on the version of Linc used.

The main problem is that the Linc 4.1 (R4 protocol) does not understand the messages received from the driver (R2 implementation so should be based on UCS protocol) as the headers and checksums are different in the two protocols.

Using a UCS Linc set to 19k2 for the network sets the RS485 comms to R4 but still uses UCS on the RS232 side.

[BACnet]

I am looking into the possibility of using a driver to connect york linc devices to Tridium which I believe is their ISN protocol version 4.0. Has anyone been able to intregrate tridium and their Linc devices. Here is one of the packets that I scanned out.

02 80 BE 80 84 D7 81 FF 50 30 31 20 54 45 4D 50 30 20 20 20 20 20 20 20 20 20 20 36 39 2E 37 44 45 47 0D 97 03

Kevin

I don't think that one datagram is enough to decrypt this version of the protocol but on the surface it looks pretty damn simple.

That datagram is referring to "point 01" and is says that at present, it is registering 69.7°.