<?xml-stylesheet type="text/xsl" href="https://community.element14.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Safe &amp;amp; Sound - Safety Jacket for the Tolling Industry #5: Writing your own protocol</title><link>/challenges-projects/design-challenges/texas-instruments-safe-sound-wearables-design-challenge/b/blog/posts/safe-sound---safety-jacket-for-the-tolling-industry-5-writing-your-own-protocol</link><description>I have been working with industrial control for more than a decade and have come up with my own &amp;#39;hacks&amp;#39; to create a working system. This is my input for those who want to understand the process of writing a protocol stack.. at least my process anyway</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: Safe &amp;amp; Sound - Safety Jacket for the Tolling Industry #5: Writing your own protocol</title><link>https://community.element14.com/challenges-projects/design-challenges/texas-instruments-safe-sound-wearables-design-challenge/b/blog/posts/safe-sound---safety-jacket-for-the-tolling-industry-5-writing-your-own-protocol</link><pubDate>Wed, 22 Mar 2017 18:26:41 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:59d75017-8293-44d7-918d-fad11d912493</guid><dc:creator>ipv1</dc:creator><slash:comments>0</slash:comments><description>&lt;p&gt;Hi &lt;/p&gt;&lt;p&gt;&lt;span&gt;[mention:8fb233e8974445138ef0af2b63b49f94:e9ed411860ed4f2ba0265705b8793d05]&lt;/span&gt; sir, &lt;/p&gt;&lt;p&gt;As a generalisation the term protocol could be used for, &amp;quot;a set of rules that govern the successful communication between two or more entities using the same media&amp;quot;. In this experiment, the ability to &amp;#39;address&amp;#39; nodes has been introduced to facilitate communications just as in I2C or ModBUS. I hope to add another layer on to allow more functionality based on the same principles used in the design of TCP/IP and it should reinforce the information provided.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;The Intel Galileo, Gen2, Edison do not have the a dedicated I2C Hardware block to by understanding. Their master functionality is executed in software in the drive layer of the Yocto Linux image and is more or less a bit bang scenario. The YUN with Linux is able to do I2C Slave since it uses an AVR and it&amp;#39;s I2C peripheral. I am currently looking at alternative methods but it seems adding a small microcontroller such as an MSP430 in slave mode I2C and Slave more SPI would be a good solution. Its on my todo list for next week where an MSP430G2553 will be demonstrated as an I2C SPI bridge operating at 3.3V and 5V TTL. I made a PCB with the controller and Voltage level converter that I need to test but it will solve a number of problems in the future. &lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Thanks again for the inputs.&lt;/p&gt;&lt;p&gt;Cheers,&lt;/p&gt;&lt;p&gt;IP&lt;/p&gt;&lt;img src="https://community.element14.com/aggbug?PostID=2692&amp;AppID=150&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item><item><title>RE: Safe &amp;amp; Sound - Safety Jacket for the Tolling Industry #5: Writing your own protocol</title><link>https://community.element14.com/challenges-projects/design-challenges/texas-instruments-safe-sound-wearables-design-challenge/b/blog/posts/safe-sound---safety-jacket-for-the-tolling-industry-5-writing-your-own-protocol</link><pubDate>Wed, 22 Mar 2017 10:15:57 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:59d75017-8293-44d7-918d-fad11d912493</guid><dc:creator>mcb1</dc:creator><slash:comments>2</slash:comments><description>&lt;p&gt;Personally I don&amp;#39;t tend to think of UART, SPI, I2C as a protocol.&lt;/p&gt;&lt;p&gt;IMO they are a transport mechanism or a means of sending the data.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Your code can be sent over any medium (SPI, I2C, Wireless, Ethernet) and as long as the far end can process it, then it can communicate.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;blockquote class="jive-quote"&gt;&lt;p&gt;Boards such as the Intel Galileo, Edison etc will not function as I2C slaves&lt;/p&gt;&lt;/blockquote&gt;&lt;p&gt;I couldn&amp;#39;t get the Edison to talk One Wire (using Arduino sketch), but I was able to make it drive the I2C display.&lt;/p&gt;&lt;p&gt;As I understand it is a timing issue, since it runs under the OS.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;I haven&amp;#39;t tried it as a slave, so maybe that should be an exercise for next week.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Cheers&lt;/p&gt;&lt;p&gt;Mark&lt;/p&gt;&lt;img src="https://community.element14.com/aggbug?PostID=2692&amp;AppID=150&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item><item><title>RE: Safe &amp;amp; Sound - Safety Jacket for the Tolling Industry #5: Writing your own protocol</title><link>https://community.element14.com/challenges-projects/design-challenges/texas-instruments-safe-sound-wearables-design-challenge/b/blog/posts/safe-sound---safety-jacket-for-the-tolling-industry-5-writing-your-own-protocol</link><pubDate>Fri, 17 Mar 2017 09:00:08 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:59d75017-8293-44d7-918d-fad11d912493</guid><dc:creator>COMPACT</dc:creator><slash:comments>1</slash:comments><description>&lt;p&gt;I see that you&amp;#39;ve got your Enumeration Gun out and are turning everything insignificant numbers!&lt;/p&gt;&lt;p&gt;Positive integers to be precise. &lt;span&gt;[View:/resized-image/__size/16x16/__key/commentfiles/f7d226abd59f475c9d224a79e3f0ec07-59d75017-8293-44d7-918d-fad11d912493/contentimage_5F00_4027.png:16:16]&lt;/span&gt;&lt;/p&gt;&lt;img src="https://community.element14.com/aggbug?PostID=2692&amp;AppID=150&amp;AppType=Weblog&amp;ContentType=0" width="1" height="1"&gt;</description></item></channel></rss>