From greg.j.kazz at jpl.nasa.gov Thu May 15 18:20:45 2014 From: greg.j.kazz at jpl.nasa.gov (Kazz, Greg J (312G)) Date: Thu, 15 May 2014 18:20:45 +0000 Subject: [Sls-slp] How do you use TC-MAPs in your agency ? Message-ID: Dear SLP WG, We are trying to determine the number of VCs that are required for commanding robotic missions for the Next Generation Space Link Protocol (NGSLP). Can you tell inform us, based on past experience, the number of Virtual Channels (VCs) you use for uplink and how you use TC Multiplexer Access Points (MAPs)? Thanks! Greg Kazz and Ed Greenberg -------------- next part -------------- An HTML attachment was scrubbed... URL: From tyamada at isas.jaxa.jp Fri May 16 04:01:21 2014 From: tyamada at isas.jaxa.jp (Takahiro Yamada) Date: Fri, 16 May 2014 13:01:21 +0900 Subject: [Sls-slp] How do you use TC-MAPs in your agency ? In-Reply-To: References: Message-ID: <8B08D8B7-2D45-4B5B-BE09-3FE3F6612652@isas.jaxa.jp> Greg, > We are trying to determine the number of VCs that are required for commanding robotic missions for the Next Generation Space Link Protocol (NGSLP). Can you tell inform us, based on past experience, the number of Virtual Channels (VCs) you use for uplink and how you use TC Multiplexer Access Points (MAPs)? At JAXA/ISAS, we use VCs for distinguishing between the primary and backup command systems. So we use two VCs (at most). We use MAPs for distinguishing different types of command decoders (hardware decoder, software decoder, etc.). Depending on the project, two to ten MAPs are used in a VC. I hope this information helps. Best regards, Takahiro Yamada From timothy.j.ray at nasa.gov Fri May 16 13:57:59 2014 From: timothy.j.ray at nasa.gov (Ray, Timothy J. (GSFC-5830)) Date: Fri, 16 May 2014 13:57:59 +0000 Subject: [Sls-slp] How do you use TC-MAPs in your agency ? In-Reply-To: <8B08D8B7-2D45-4B5B-BE09-3FE3F6612652@isas.jaxa.jp> References: <8B08D8B7-2D45-4B5B-BE09-3FE3F6612652@isas.jaxa.jp> Message-ID: <10145D9C82606F428D57F5CDFB48210107DB39CB@NDMSMBX403.ndc.nasa.gov> Greg, We (NASA/Goddard) use only one VC for commanding. We do not use MAPs. Tim From Gilles.Moury at cnes.fr Fri May 16 16:59:14 2014 From: Gilles.Moury at cnes.fr (Moury Gilles) Date: Fri, 16 May 2014 16:59:14 +0000 Subject: [Sls-slp] How do you use TC-MAPs in your agency ? In-Reply-To: <10145D9C82606F428D57F5CDFB48210107DB39CB@NDMSMBX403.ndc.nasa.gov> References: <8B08D8B7-2D45-4B5B-BE09-3FE3F6612652@isas.jaxa.jp> <10145D9C82606F428D57F5CDFB48210107DB39CB@NDMSMBX403.ndc.nasa.gov> Message-ID: <442F062EBF46F247A96B8A50EF3EB6F4154ADFC9@TW-MBX-P04.cnesnet.ad.cnes.fr> Dear Greg, At CNES, we use typically: - 2 VCs : one for the nominal TC decoder, one for the redundant TC decoder - 4 to 8 MAPs depending on the command&control configuration of the spacecraft Best regards, Gilles Gilles MOURY CNES Toulouse -----Message d'origine----- De : sls-slp-bounces at mailman.ccsds.org [mailto:sls-slp-bounces at mailman.ccsds.org] De la part de Ray, Timothy J. (GSFC-5830) Envoyé : vendredi 16 mai 2014 15:58 À : Kazz, Greg J (JPL-312G)[Jet Propulsion Laboratory] Cc : sls-slp at mailman.ccsds.org Objet : RE: [Sls-slp] How do you use TC-MAPs in your agency ? Greg, We (NASA/Goddard) use only one VC for commanding. We do not use MAPs. Tim _______________________________________________ Sls-slp mailing list Sls-slp at mailman.ccsds.org http://mailman.ccsds.org/mailman/listinfo/sls-slp From greg.j.kazz at jpl.nasa.gov Sat May 17 19:01:37 2014 From: greg.j.kazz at jpl.nasa.gov (Kazz, Greg J (312G)) Date: Sat, 17 May 2014 19:01:37 +0000 Subject: [Sls-slp] Follow on question concerning agency use of MAPs and Segmentation on Telecommand Message-ID: All, Thank you very much for your helpful responses. An additional question: For those agencies who said they do use MAPs on TC, do you also segment packets on the uplink? If this is true, is segmentation used due to the limited size of 1017/1019 octets or less of the current TC frame? Thanks! Greg CCSDS SLP WG -------------- next part -------------- An HTML attachment was scrubbed... URL: From greg.j.kazz at jpl.nasa.gov Mon May 19 17:27:32 2014 From: greg.j.kazz at jpl.nasa.gov (Kazz, Greg J (312G)) Date: Mon, 19 May 2014 17:27:32 +0000 Subject: [Sls-slp] The Proposed NGSLP Spacecraft ID Use Field Message-ID: Dear SLP WG, Yet another question for you! The proposed NGSLP frame format has a SPACECRAFT ID USE FIELD field that would identify mission phase in which the data contained in the transfer frame was generated. This proposed field is 2 bits long. This field is not going to change after launch so: Is this field necessary? Or should ground data services provide an other method (e.g., SFDU header) to identify when the data was generated? Any Comments? Rationale for inclusion of the field: Currently missions request multiple SCID assignments to uniquely identify the environment in which the data was generated. This practice reduces the number of SCIDs that are available to CCSDS member agencies. Moreover the SANA spacecraft ID registry is very limited: The number of possible SCIDs by Transfer Frame Version Number are: 1024 Version 1, 256 Version 2, 1024 Version 3 IDs. The Spacecraft ID Use Field provides a mission unique Spacecraft ID applicable for all pre and post launch phases while self-identifying the phase in which the data was generated. Three of the four values of this field (“00”, “01”, “10”) are mission defined. The fourth value, ‘11’ is reserved for post launch data. Thanks! Greg Keeping an eye to the future -------------- next part -------------- An HTML attachment was scrubbed... URL: From greg.j.kazz at jpl.nasa.gov Tue May 20 15:28:08 2014 From: greg.j.kazz at jpl.nasa.gov (Kazz, Greg J (312G)) Date: Tue, 20 May 2014 15:28:08 +0000 Subject: [Sls-slp] FW: [Cesg-all] Proc & Org YB published Version In-Reply-To: <8539_1400597161_537B6AA9_8539_7978_1_OF8BEE4DDE.5BBA59A5-ONC1257CDE.0050C065-C1257CDE.00511C7E@esa.int> References: <8539_1400597161_537B6AA9_8539_7978_1_OF8BEE4DDE.5BBA59A5-ONC1257CDE.0050C065-C1257CDE.00511C7E@esa.int> Message-ID: Dear SLP WG, For your information please. Regards, Greg Kazz Chairman CCSDS SLS-SLP WG From: "Nestor.Peccia at esa.int" > Date: Tuesday, May 20, 2014 at 7:45 AM To: "cesg-all at mailman.ccsds.org" > Subject: [Cesg-all] Proc & Org YB published Version Dear all Please find below the link to the ORGANIZATION AND PROCESSES FOR THE CCSDS, published in April 2014 after CESG / CMC Approval http://public.ccsds.org/publications/archive/A02x1y4.pdf I assume you will further distribute the link to your WG members. ciao nestor This message and any attachments are intended for the use of the addressee or addressees only. The unauthorised disclosure, use, dissemination or copying (either in whole or in part) of its content is not permitted. If you received this message in error, please notify the sender and delete it from your system. Emails can be altered and their integrity cannot be guaranteed by the sender. Please consider the environment before printing this email. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ATT00001.txt URL: From tyamada at isas.jaxa.jp Wed May 21 04:36:25 2014 From: tyamada at isas.jaxa.jp (Takahiro Yamada) Date: Wed, 21 May 2014 13:36:25 +0900 Subject: [Sls-slp] The Proposed NGSLP Spacecraft ID Use Field In-Reply-To: References: Message-ID: <163F5678-1F40-42DE-B628-3097E3A2B00F@isas.jaxa.jp> Greg, > The proposed NGSLP frame format has a SPACECRAFT ID USE FIELD field that would identify mission phase in which the data contained in the transfer frame was generated. This proposed field is 2 bits long. This field is not going to change after launch so: Is this field necessary? Or should ground data services provide an other method (e.g., SFDU header) to identify when the data was generated? At the ground system of JAXA/ISAS, every frame or packet is associated with a generation or reception time, So, the field you mentioned above is not necessary. Best regards, Takahiro Yamada From kscott at mitre.org Thu May 29 18:21:57 2014 From: kscott at mitre.org (Scott, Keith L.) Date: Thu, 29 May 2014 18:21:57 +0000 Subject: [Sls-slp] RE: Your RIDs against Overview of Space Comm Protocols GB In-Reply-To: References: Message-ID: <5EE81C5C4CFFF4418C5EAD12F49D64EE4C21F032@IMCMBX01.MITRE.ORG> Greg, I'm OK with your modifications and dispositions. v/r, --keith From: Kazz, Greg J (312G) [mailto:greg.j.kazz at jpl.nasa.gov] Sent: Wednesday, April 16, 2014 8:33 AM To: Scott, Keith L. Cc: sls-slp at mailman.ccsds.org Subject: Your RIDs against Overview of Space Comm Protocols GB Keith, Attach please find responses to your CESG considerations on the CCSDS 130-G-2.1 Green Book, Overview of Space Comm Protocols GB. Please let me know if these responses address your concerns sufficiently so that Gian Paolo can generate a CMC poll to move this book towards publication as the Version 3 GB. Best regards, GReg -------------- next part -------------- An HTML attachment was scrubbed... URL: