[XPDR] FW: ARINC 768A Committee I/O Proposal

[Sam Buckwalter]

Hello All:

Please read the email thread below regarding reserving blocks of numbers.


Sam Buckwalter
ARINC Industry Activities an SAE ITC Program
Lead Principle Engineer
Program Director

m 1+443.454.0584
sam.buckwalter at sae-itc.org



From: Schueler, Kurt <Kurt.Schueler at garmin.com>
Sent: Friday, April 1, 2022 1:01 PM
To: Sam Buckwalter <Sam.Buckwalter at sae-itc.org>
Cc: Cooper, Seth <Seth.Cooper at garmin.com>
Subject: FW: ARINC 768A Committee I/O Proposal


Hi, Sam-

Here’s Randy’s proposal. As discussed in meeting, we will need to anticipate/document how to reserve blocks of numbers.

Thanks,

Kurt

From: Jacobson, Randy H Collins <Randy.Jacobson at collins.com<mailto:Randy.Jacobson at collins.com>>
Sent: Monday, February 07, 2022 9:09 AM
To: Gibson, Tim <Timothy.Gibson at garmin.com<mailto:Timothy.Gibson at garmin.com>>; Cooper, Seth <Seth.Cooper at garmin.com<mailto:Seth.Cooper at garmin.com>>; Schueler, Kurt <Kurt.Schueler at garmin.com<mailto:Kurt.Schueler at garmin.com>>
Subject: RE: ARINC 768A Committee I/O Proposal

CAUTION - EXTERNAL EMAIL: Do not click any links or open any attachments unless you trust the sender and know the content is safe.


About 20 seconds after I sent my last email – I had a thought.  It would be nice to require for the main two manufactures at least one pin being ground; that way the “default” (nothing grounded) is neither of them.

I also thought that the default config should probably be something that we define – for example for use on a test bench in a service center.

So I moved things around just a smidge and would like to amend my initial proposal.

Network Ident Pin #

9
8
7
6
5
4
3
2
1
Block #1A
0
0
0
Reserved for Equipment Manufacturer
Block #1B
0
0
1
Reserved
Block #2
0
1
Reserved for Aircraft Manufacturer 'A'
Block #3
1
0
Reserved for Aircraft Manufacturer 'B'
Block #4A
1
1
0
Reserved
Block #4B
1
1
1
Reserved
Note: Other blocks / sub-blocks may be added using strobed pins

Randy
- - - - - - - - - - -
Randy Jacobson
Collins Aerospace
Traffic Surveillance Systems Architect

From: Jacobson, Randy H Collins
Sent: Monday, February 07, 2022 10:01 AM
To: Tim Gibson <timothy.gibson at garmin.com<mailto:timothy.gibson at garmin.com>>; Seth Cooper <seth.cooper at garmin.com<mailto:seth.cooper at garmin.com>>; Kurt.Schueler at garmin.com<mailto:Kurt.Schueler at garmin.com>
Subject: FW: ARINC 768A Committee I/O Proposal

Network Ident Pin #

9
8
7
6
5
4
3
2
1
Block #1
0
0
Reserved for Aircraft Manufacturer 'A'
Block #2
0
1
Reserved for Aircraft Manufacturer 'B'
Block #3A
1
0
0
Reserved
Block #3B
1
0
1
Reserved
Block #4A
1
1
0
Reserved
Block #4B
1
1
1
Reserved for Equipment Manufacturer
Note: Other blocks / sub-blocks may be added using strobed pins

I don’t have any issues with what is proposed (either the 8 or the 16), but I really liked the model Mohammed mentioned it the other day of patterning this off how Mode S addresses are partitioned out – where bigger counties are given a bigger block.  I believe this is also how IP addresses are handed out.

So Aircraft Manufacturer 'A' & Aircraft Manufacturer 'B' are like the US and the Soviet Union (now Russia) which get the biggest chunk of addresses.  Other groups are subdivided.

I also did not want to list a number from “0 – 31” or anything like that as we do have the option of adding additional bits through the use of strobed pins.

I also thought that we might want a subblock for ourselves – on our own closed systems.

I am not objecting to your proposals at all; if we went with one of the proposals you guys came up with I would support it.  I am just proposing some additions for your consideration.  If you like this – bring it forward to the rest of the group.

Randy
- - - - - - - - - - -
Randy Jacobson
Collins Aerospace
Traffic Surveillance Systems Architect

From: xpdr-bounces at mailman.sae-itc.org<mailto:xpdr-bounces at mailman.sae-itc.org> <xpdr-bounces at mailman.sae-itc.org<mailto:xpdr-bounces at mailman.sae-itc.org>> On Behalf Of Paul Prisaznuk
Sent: Friday, February 04, 2022 4:52 PM
To: xpdr at mailman.sae-itc.org<mailto:xpdr at mailman.sae-itc.org>
Subject: [External] [XPDR] Fwd: ARINC 768A Committee I/O Proposal

Hello all,

I am pleased to forward Garmin input to ARINC Project Paper 768A, 2G ISS.  Comments to Tim Gibson at Garmin per his message below.

Paul Prisaznuk
ARINC


________________________________
From: Gibson, Tim <Timothy.Gibson at garmin.com<mailto:Timothy.Gibson at garmin.com>>
Sent: Friday, February 4, 2022, 4:00 PM
To: Larry Hesterberg; Paul Prisaznuk
Cc: Cooper, Seth; Schueler, Kurt; Kuhlman, Kyle
Subject: ARINC 768A Committee I/O Proposal

Per today’s discussion in the ARINC Surveillance WG meeting for APIM 19-007:

Updated Proposed ARINC768A I/O with pinout attached and uploaded to SAE Teams Fileshare (link below).

Request OEMs, Equipment Manufacturers, and Airlines review and comment ahead of 2/25 meeting.

  *   Tab “Summary Middle & Bottom” was reviewed in the meeting without comment driving change
  *   Tab “Middle Plug” request comment and review on specific pin assignments (color code matches summary tab)
  *   Andre’s comment for Block 1 Block 2 safety segregation has been attempted to be addressed
  *   Randy’s comment about non-standard 429 pin arrangements has been attempted to be addressed
  *   Tabs “Network ID Pin List – 16 blocks” and “Network ID Pin List – 8 blocks” are provided to drive conversation in next meeting about reserving ID code blocks for suppliers up front.  This is the “rock” we have brought to Randy.

Thanks again for allowing us time today to discuss Pinout! We’re excited to continue the conversation.




Tim Gibson
Team Leader, Design Engineering - Aviation
1200 East 151st Street, Olathe, KS 66062
Direct: 913.440.5591
tim.gibson at garmin.com<mailto:tim.gibson at garmin.com>


________________________________

CONFIDENTIALITY NOTICE: This email and any attachments are for the sole use of the intended recipient(s) and contain information that may be Garmin confidential and/or Garmin legally privileged. If you have received this email in error, please notify the sender by reply email and delete the message. Any disclosure, copying, distribution or use of this communication (including attachments) by someone other than the intended recipient is prohibited. Thank you.


Nothing in this message is intended to constitute an electronic signature unless a specific statement to the contrary is included in this message. Confidentiality Note: This message is intended only for the person or entity to which it is addressed. This email, and any attachments, may contain confidential and/or proprietary material. Any review, transmission, dissemination or other use, or taking of any action in reliance upon this message by persons or entities other than the intended recipient is prohibited. If you received this message in error, please contact the sender and permanently delete any printout of the message, the original and any copy of the e-mail and its attachments from your computer.


Nothing in this message is intended to constitute an electronic signature unless a specific statement to the contrary is included in this message. Confidentiality Note: This message is intended only for the person or entity to which it is addressed. This email, and any attachments, may contain confidential and/or proprietary material. Any review, transmission, dissemination or other use, or taking of any action in reliance upon this message by persons or entities other than the intended recipient is prohibited. If you received this message in error, please contact the sender and permanently delete any printout of the message, the original and any copy of the e-mail and its attachments from your computer.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.sae-itc.org/pipermail/xpdr/attachments/20220401/98bbdd0f/attachment-0001.html>