Nanometrics Data Formats Reference Guide

More documents

Recommendations

Info

Chapter 3: Private Data Streams 3.3.2 AddChannels messages Clients send an AddChannels message to subscribe to certain data streams. An Add- Channels message contains the following information: 1. Data type requested (time-series, state-of-health, or triggers). 2. Channels requested (given by an array of channel indices, or keys). 3. Delay for the short-term completion buffer (buffered streams only). 4. Parameters for the decimation filter (time-series only). 5. Parameters for buffered packet request (time-series, serial and state of health data only) An AddChannels message can be used in two ways: to add channels to a subscription, or to edit the parameters for a currently subscribed channel. If Stream Manager receives an AddChannels message which includes a channel already in the subscription, it checks if parameters in the AddChannels message (the short-term completion and decimation parameters if they apply) are different from the current parameters for the channel. If the parameters are different, the old values are discarded for the channel, and packets from that channel are processed using the new instructions. The current version of Stream Manager recognizes the five types of Add Channels messages described below. 3.3.2.1 AddTime-SeriesChannels The Add Time-SeriesChannels message is used to request time-series packets. Time series streams can be buffered to ensure that packets for each channel are output in chronological order. When packets are missed, Stream Manager will wait a specified period of time for the gap to be filled by retransmitted packets. Specifying a completion time of 0 will guarantee that packets are in chronological order, without waiting for missed data. Time series streams can be requested in three different output formats: compressed data at the original sample rate, uncompressed data at the original sample rate, or uncompressed data decimated using Stream Manager's built in decimating FIR filters. Uncompressed time-series data is typically sent in packets of fixed length (one second duration). However, missing incoming data may cause Stream Manager to output a shorter packet. An AddDataChannels message can also include a request to receive packets from the Naqs buffer of recent packets, before receiving the stream of new packets. This, effectively, moves the start of the stream several packets into the past. Header: 4 byte int Signature = 0x7ABCDE0F 4 byte int message type = 120 4 byte int message content length = 16 + 4 * N, where N = number of channels Content: 4 byte int number of channels requested = N (use 0 to request all channels) 36 Nanometrics Data Formats Reference Guide 14602R4 2003-11-07
Chapter 3: Private Data Streams 3.3.2.2 AddSohChannels N * 4 byte int Channel key for each requested channel (same as in Channel List message) 4 byte int Short-term-completion time = s , -1
Page 1: Nanometrics Data Formats Reference
Page 4 and 5: © 1996-2003 Nanometrics Inc. All R
Page 6 and 7: Contents 1.5.32 Transmitter bundle.
Page 8 and 9: Contents 4.4.1.10 TriggerRequest .
Page 10 and 11: Chapter 1: NMXP Data Format The ord
Page 12 and 13: Chapter 1: NMXP Data Format 1.3 Pac
Page 14 and 15: Chapter 1: NMXP Data Format bit 3-7
Page 16 and 17: Chapter 1: NMXP Data Format data. T
Page 18 and 19: Chapter 1: NMXP Data Format along w
Page 20 and 21: Chapter 1: NMXP Data Format 4 bytes
Page 24 and 25: Chapter 1: NMXP Data Format 2 byte
Page 26 and 27: Chapter 1: NMXP Data Format 7 = no
Page 32 and 33: Chapter 2: NMX Alert Format String
Page 34 and 35: Chapter 2: NMX Alert Format 2.3.2 A
Page 36 and 37: Chapter 2: NMX Alert Format The fol
Page 38 and 39: Chapter 2: NMX Alert Format argumen
Page 40 and 41: Chapter 2: NMX Alert Format 32 Nano
Page 42 and 43: Chapter 3: Private Data Streams Tri
Page 46 and 47: Chapter 3: Private Data Streams chr
Page 48 and 49: Chapter 3: Private Data Streams 4 b
Page 50 and 51: Chapter 3: Private Data Streams 3.3
Page 52 and 53: Chapter 3: Private Data Streams 44
Page 54 and 55: Chapter 4: Data Access Protocol 4.2
Page 58 and 59: Chapter 4: Data Access Protocol Hea
Page 64 and 65: Chapter 5: Tagged File Format PTR a
Page 66 and 67: Chapter 5: Tagged File Format 37 TA
Page 68 and 69: Chapter 6: Y-File Format UCHAR UCHA
Page 70 and 71: Chapter 6: Y-File Format ULONG LONG
Page 72 and 73: Appendix A: Data Stream Client // d
Page 74 and 75: Appendix A: Data Stream Client } re
Page 76 and 77: Appendix A: Data Stream Client Retu
Page 78 and 79: Appendix A: Data Stream Client Data
Page 80 and 81: Appendix A: Data Stream Client rc =
Page 82 and 83: Appendix A: Data Stream Client ----
Page 84 and 85: Appendix A: Data Stream Client } }
Page 86: Appendix B: Serial Packet CRC SendB

Nanometrics Data Formats Reference Guide

Create successful ePaper yourself

Delete template?

Save as template?