Talk:ARINC 429

message: There's some confusion between the two here. Talking about twisted-pair wires and Tx and Rx channels implies a bus. Talking about the meaning of bits in a word implies a protocol. If ARINC 429 specifies both (like, say RS232) this might warrant a mention. A bus spec would require at least a statement about voltages and such. A protocol might benefit from a statement how timing is enforced (on a bus that supports two different bit-rates and remains in a constant NULL state between words? Or is "NULL" a particular data word that can be synchronized against?)  —Preceding unsigned comment added by 137.78.180.229 (talk) 22:38, 22 April 2008 (UTC)
thread_title: Bus vs. protocol

message: * http://www.sandel.com/SN3308_EHSI_sup_documentation_garmin.php  —Preceding unsigned comment added by 82.82.248.8 (talk) 00:20, 31 March 2009 (UTC)
thread_title:  Additional Info 

message: The section stating that there is a controversy over the prohibition of certain devices at certain times during flight cites no references to support the existance of a controversy.  I'm unaware of one but believe I'd hear about it, as an FAA Safety Team Representative.  Without an authoritative reference that can support this assertion, this statement should be removed.  For the sake of full disclosure, if a reference is provided I will question its authenticity, validity and basis.  
Proving that anything is "incapable" of interfering with safe operation and reliability of aircraft systems is a logical impossibility.  So, the likelihood of their being a controversy isn't likely.  I haven't participated in RTCA Working groups lately but the likelihood that any such controversy is within either RTCA or the FAA is not worth the time to write about it -- unless one also believes that my elephant repellant is not effective.  I mean, there is no elephant in the room with you, is there?  This is evidance of how good the repellant is.
This section should be removed if a credible basis for it cannot be cited.
--Kernel.package (talk) 22:33, 23 June 2009 (UTC)
replies: text: The statement was added by this edit. Later, this edit removed the source. That said, there certainly has been public discussion on the subject. See , ,  and . More formally, this IEEE Spectrum article examined the hazards.LeadSongDog come howl 06:09, 24 June 2009 (UTC)

text: Neither actually; ARINC 429 is specified independent of microcontroller architecture.  We have 8-bit processors here driving ARINC 429.  ARINC 429 transceivers IC’s were based on 32-bit shift registers; and IIRC the standard predates widespread use of 16-bit processors. IveGoneAway (talk) 22:43, 28 October 2013 (UTC)
thread_title:  Controversial? I don't think so. 

message: The paragraph text says that bits 29 - 31 are used for SSM. The table/diagram immediately following refers only to bits 30 and 31. Don't know which is correct - but they aren't consistent.  — Preceding unsigned comment added by 199.64.0.252 (talk) 18:43, 21 August 2013 (UTC)
replies: text: As I intended to cover in my 18 October 2013 edit, the encoding of the 2 bits in the SSM depends on the data type represented in the data field (BNR, BCD, or other [Boolean or other discrete encodings, or a compound structure]).  Sometimes the SSM is a sign matrix, sometimes it is a status matrix, and sometimes it is both.   In the case of BNR, it is a status only encoding.  If the BNR is sign-less, Bit 29 is simply the encoding of the msb.   If the BNR is signed, the msb happens to also indicate sign – this is completely a consequence of the 2s complement representation.  Thus the standard describes Bit 29 as a (serendipitously) conditional part of the SSM (p. 3).   In contrast, Bit 11 has literal variable functionality – depending on the system, Bit 11 may indicate nominal or degraded accuracy for a BNR and no numerical value. IveGoneAway (talk) 22:43, 28 October 2013 (UTC)
thread_title:  SSM bits 

message: “the bits representing the label are reversed” in respect to what? CAN Arbitration Fields? SPI? I2C?  Considering the Label field in the picture, the bit order looks to be in the same order as the octal number it is representing -- if anything, it is the numbers in the data field that look backward in this perspective. It would probably be fairest to delete the sentence, or at least state what the bits are in reverse to, e.g., the BCD/BNR data field? --  IveGoneAway (talk) 18 October 2013 (UTC)
199.63.142.252 (talk) 06:21, 10 January 2014 (UTC)
thread_title: With Respect to What

message: Hello fellow Wikipedians,
I have just modified  on ARINC 429. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
*Added archive https://web.archive.org/web/20111029161330/http://www.holtic.com:80/category/352-arinc-429.aspx to http://www.holtic.com/category/352-arinc-429.aspx
When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at ).
Cheers.—InternetArchiveBot (Report bug) 08:50, 1 October 2016 (UTC)
thread_title:  External links modified 

message: Hello fellow Wikipedians,
I have just modified 2 external links on ARINC 429. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
*Corrected formatting/usage for http://www.holtic.com/category/352-arinc-429.aspx
*Added archive https://web.archive.org/web/20091007185947/http://www.actel.com/ipdocs/CoreARINC429_DS.pdf to http://www.actel.com/ipdocs/CoreARINC429_DS.pdf
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
Cheers.—InternetArchiveBot (Report bug) 04:51, 24 June 2017 (UTC)
thread_title:  External links modified