ATM Node in a cog
Todd Marshall
Posts: 89
I'm beginning to look at the feasibility of putting an ATM node in a COG. Then to put it into 2 COGS and have them communicate. Then into 7 COGS to form a mesh network. Then to multiple Prop 1s to expand the network. Then to add wireless (ZBEE? or more desirably UWB) to give flexibility to the network. Then to add GPS (or static location) information to the nodes to give more network flexibility. Then to add a WIZNET to give Layer 3. Then maybe to install my GLEE programming language (see WithGLEE.com) in a Cyclone V LPGA to give higher layer functionality.
Does anyone see a reason an ATM node cannot be put on a COG ... or even on a Prop1 or anticipated Prop 2? ATM brings up nothing when I do a search of the Parallax site.
If anyone else has interest in such an effort I welcome collaboration.
Does anyone see a reason an ATM node cannot be put on a COG ... or even on a Prop1 or anticipated Prop 2? ATM brings up nothing when I do a search of the Parallax site.
If anyone else has interest in such an effort I welcome collaboration.
Comments
https://en.wikipedia.org/wiki/Asynchronous_Transfer_Mode
ATM is a layer 2 (and 2.5 ... with the AAL versions) protocol. I was in the business when we lost our way.
Regardless, does anyone see a deficiency in a COG that precludes implementing an ATM node in one?
Many times I've considered Propeller for doing TDM (Time Domain Multiplexing) because it can do TDM ... except that the darn thing is too slow to produce an OC1 rate. This is one reason I asked for SERDES in the new chip. Without SERDES, even the new chip would not be able to do OC1.
So, while you can do some ATM cell communication and framing etc... with Propeller, where would it be applied given the speed restrictions?
ATM can hop at three or four orders of magnitude faster than IP and is naturally connection oriented (yielding security and efficiency benefits). The challenge is to keep thousands of nodes alive (or re-routable) in a "connection" for the length of the transmission. That's more difficult than keeping 20 alive ... but still possible. Heck, IP does it on a per packet basis.