¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

Crappy protocols


rickmcneely
 

Has anyone else been forced to work with the new Middle Atlantic RackLink systems? Where do people come up with these bizarre protocols?

1. Protocol is all hex.
2. You have to generate checksums on serial and over IP.
4. When connected via serial, the device will ping you and if you don't respond it will quit accepting commands.

They've got enough processing horsepower to run a webserver on the device, so I'm sure they could do better than a protocol from 1976.


Seth Olle
 

I heard once in 1976 they hired Tim(name made up) to do all the protocols for pretty much everyone.
Then never changed them again, when checksums and all that other stupid stuff was necessary.
I like simple POWERON for example. Makes sense.

It seems to be less and less, I can remember back in the day, all the time doing complex string parsing, for huge hex strings.
Not so much anymore.

From: rickmcneely <rickmcneely@...<mailto:rickmcneely@...>>
Reply-To: "Crestron@...<mailto:Crestron@...>" <Crestron@...<mailto:Crestron@...>>
Date: Thursday, May 2, 2013 2:22 PM
To: "Crestron@...<mailto:Crestron@...>" <Crestron@...<mailto:Crestron@...>>
Subject: [Crestron] Crappy protocols



Has anyone else been forced to work with the new Middle Atlantic RackLink systems? Where do people come up with these bizarre protocols?

1. Protocol is all hex.
2. You have to generate checksums on serial and over IP.
4. When connected via serial, the device will ping you and if you don't respond it will quit accepting commands.

They've got enough processing horsepower to run a webserver on the device, so I'm sure they could do better than a protocol from 1976.


 

You're complaining about fixed length delimited strings? How lazy are we getting! :)

--- In Crestron@..., Seth Olle <seth@...> wrote:

I heard once in 1976 they hired Tim(name made up) to do all the protocols for pretty much everyone.
Then never changed them again, when checksums and all that other stupid stuff was necessary.
I like simple POWERON for example. Makes sense.

It seems to be less and less, I can remember back in the day, all the time doing complex string parsing, for huge hex strings.
Not so much anymore.

From: rickmcneely <rickmcneely@...<mailto:rickmcneely@...>>
Reply-To: "Crestron@...<mailto:Crestron@...>" <Crestron@...<mailto:Crestron@...>>
Date: Thursday, May 2, 2013 2:22 PM
To: "Crestron@...<mailto:Crestron@...>" <Crestron@...<mailto:Crestron@...>>
Subject: [Crestron] Crappy protocols



Has anyone else been forced to work with the new Middle Atlantic RackLink systems? Where do people come up with these bizarre protocols?

1. Protocol is all hex.
2. You have to generate checksums on serial and over IP.
4. When connected via serial, the device will ping you and if you don't respond it will quit accepting commands.

They've got enough processing horsepower to run a webserver on the device, so I'm sure they could do better than a protocol from 1976.


Seth Olle
 

Fixed length what
OLD SCHOOL

From: matt_rasmussen_2000 <mjrtoo@...<mailto:mjrtoo@...>>
Reply-To: "Crestron@...<mailto:Crestron@...>" <Crestron@...<mailto:Crestron@...>>
Date: Thursday, May 2, 2013 2:34 PM
To: "Crestron@...<mailto:Crestron@...>" <Crestron@...<mailto:Crestron@...>>
Subject: [Crestron] Re: Crappy protocols



You're complaining about fixed length delimited strings? How lazy are we getting! :)

--- In Crestron@...<mailto:Crestron%40yahoogroups.com>, Seth Olle <seth@...> wrote:

I heard once in 1976 they hired Tim(name made up) to do all the protocols for pretty much everyone.
Then never changed them again, when checksums and all that other stupid stuff was necessary.
I like simple POWERON for example. Makes sense.

It seems to be less and less, I can remember back in the day, all the time doing complex string parsing, for huge hex strings.
Not so much anymore.

From: rickmcneely <rickmcneely@...<mailto:rickmcneely@...>>
Reply-To: "Crestron@...<mailto:Crestron%40yahoogroups.com><mailto:Crestron@...<mailto:Crestron%40yahoogroups.com>>" <Crestron@...<mailto:Crestron%40yahoogroups.com><mailto:Crestron@...<mailto:Crestron%40yahoogroups.com>>>
Date: Thursday, May 2, 2013 2:22 PM
To: "Crestron@...<mailto:Crestron%40yahoogroups.com><mailto:Crestron@...<mailto:Crestron%40yahoogroups.com>>" <Crestron@...<mailto:Crestron%40yahoogroups.com><mailto:Crestron@...<mailto:Crestron%40yahoogroups.com>>>
Subject: [Crestron] Crappy protocols



Has anyone else been forced to work with the new Middle Atlantic RackLink systems? Where do people come up with these bizarre protocols?

1. Protocol is all hex.
2. You have to generate checksums on serial and over IP.
4. When connected via serial, the device will ping you and if you don't respond it will quit accepting commands.

They've got enough processing horsepower to run a webserver on the device, so I'm sure they could do better than a protocol from 1976.


Chip
 

Have you tried the I2P module to see if it might save you some headaches? Some of 'em work, y'know? :)

- Chip

--- In Crestron@..., "rickmcneely" <rickmcneely@...> wrote:

Has anyone else been forced to work with the new Middle Atlantic RackLink systems? Where do people come up with these bizarre protocols?

1. Protocol is all hex.
2. You have to generate checksums on serial and over IP.
4. When connected via serial, the device will ping you and if you don't respond it will quit accepting commands.

They've got enough processing horsepower to run a webserver on the device, so I'm sure they could do better than a protocol from 1976.


 

Slackers, 20 years later and the laziness continues!

--- In Crestron@..., "matt_rasmussen_2000" <mjrtoo@...> wrote:

You're complaining about fixed length delimited strings? How lazy are we getting! :)

--- In Crestron@..., Seth Olle <seth@> wrote:

I heard once in 1976 they hired Tim(name made up) to do all the protocols for pretty much everyone.
Then never changed them again, when checksums and all that other stupid stuff was necessary.
I like simple POWERON for example. Makes sense.

It seems to be less and less, I can remember back in the day, all the time doing complex string parsing, for huge hex strings.
Not so much anymore.

From: rickmcneely <rickmcneely@<mailto:rickmcneely@>>
Reply-To: "Crestron@...<mailto:Crestron@...>" <Crestron@...<mailto:Crestron@...>>
Date: Thursday, May 2, 2013 2:22 PM
To: "Crestron@...<mailto:Crestron@...>" <Crestron@...<mailto:Crestron@...>>
Subject: [Crestron] Crappy protocols



Has anyone else been forced to work with the new Middle Atlantic RackLink systems? Where do people come up with these bizarre protocols?

1. Protocol is all hex.
2. You have to generate checksums on serial and over IP.
4. When connected via serial, the device will ping you and if you don't respond it will quit accepting commands.

They've got enough processing horsepower to run a webserver on the device, so I'm sure they could do better than a protocol from 1976.


rickmcneely
 

I wish! It's an AMX job. They have modules for it, but a firmware change on the RackLink broke that too. Another reason to dislike it.

--- In Crestron@..., "Chip" <cfm@...> wrote:


Have you tried the I2P module to see if it might save you some headaches? Some of 'em work, y'know? :)

- Chip


 

I call it, job security! : )

--
Sebastian Marszalek


rickmcneely
 

I suppose that is a good way to look at it. I'm just too crabby to adopt that view myself! :-)

--- In Crestron@..., sebastian marszalek <s.marszalek11@...> wrote:

I call it, job security! : )

--
Sebastian Marszalek


[Non-text portions of this message have been removed]