Breaking News
Newest First | Oldest First | Threaded View
User Rank
Re: Proprietary protocols
Bert22306   5/16/2014 4:05:08 PM
That too, actually, or "almost." In our case, in 1999 or so, we had to develop an actively redundant link layer protocol, for high speed, high survivability networks. Lo and behold, in 2010, IEC 62439-3 is created: Parallel Redundancy Protocol. It's not identical to ours, and I much prefer our approach for a couple of reasons (nothing like developing your own to understand the advantages and disadvantages of other approaches you had to explore in the process), however overall, the way it works is the same. The differences are in flexibility of the link layer topology and in maximum speed the protocol can support.

User Rank
Re: Proprietary protocols
antedeluvian   5/16/2014 8:47:52 AM

Thanks for your input.

The fun part of the job is to keep track of the ongoing standards efforts, and then adopt (and adapt) the successful ones when it makes sense to do so, while still retaining compatibility

the thought occurs to me that on rare occasions this goes the other way, when a proprietary bus is standardised. I'll bet every standard of early serial bus started that way. GIven the structure of Modbus, you can just feel the evolution from a single purpose idea into the general purpose standard.


Anybody out there had their bus/protocol become a standard?

User Rank
Proprietary protocols
Bert22306   5/14/2014 4:36:32 PM
Absolutely! This topic of rolling your own, vs. using an existing standard, came up in a recent article by Junko Yoshida as well.

We very much created our own protocols, and entire digital networks, before standard ones were good enough to do what we were building. The fun part of the job is to keep track of the ongoing standards efforts, and then adopt (and adapt) the successful ones when it makes sense to do so, while still retaining compatibility with the proprietary protocols that came before.

Ultimately, for our work, adopting standards allows you to improve the products more rapidly. Because you're leveraging off the work of thousands of smart designers all over the world. However that wasn't the situation at the beginning. For my work, this has been true for protocols and also for hardware. Parts Search

185 million searchable parts
(please enter a part number or hit search to begin)

What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.

Brought to you by:

Most Recent Comments
David Ashton
David Ashton
Kevin Neilson
David Ashton
Like Us on Facebook
Special Video Section
The LTC2380-24 is a versatile 24-bit SAR ADC that combines ...
In this short video we show an LED light demo to ...
Wireless Power enables applications where it is difficult ...
LEDs are being used in current luxury model automotive ...
With design sizes expected to increase by 5X through 2020, ...
Linear Technology’s LT8330 and LT8331, two Low Quiescent ...
The quality and reliability of Mill-Max's two-piece ...
LED lighting is an important feature in today’s and future ...
The LT8602 has two high voltage buck regulators with an ...
Silego Technology’s highly versatile Mixed-signal GreenPAK ...
The quality and reliability of Mill-Max's two-piece ...
Why the multicopter? It has every thing in it. 58 of ...
Security is important in all parts of the IoT chain, ...
Infineon explains their philosophy and why the multicopter ...
The LTC4282 Hot SwapTM controller allows a board to be ...
This video highlights the Zynq® UltraScale+™ MPSoC, and sho...
Homeowners may soon be able to store the energy generated ...
The LTC®6363 is a low power, low noise, fully differential ...
See the Virtex® UltraScale+™ FPGA with 32.75G backplane ...
Vincent Ching, applications engineer at Avago Technologies, ...