BSSRECV(1)
π BSSRECV(1) β the bssrecv page, but make it cute
okay bestie, welcome to bssrecv, one of the BSS executables. it's a reception test program. yes it's from the BSS manual, no we're not being boring about it. π
β¨ NAME β¨
bssrecv β Bundle Streaming Service reception test program π°οΈ
β¨ SYNOPSIS β¨
bssrecv
that's it. that's the whole synopsis. no flags, no arguments, just vibes. π«Ά
β¨ DESCRIPTION β¨
bssrecv uses BSS to acquire streaming data from bssStreamingApp. that's the whole point of it, that's its little purpose in life. πΈ
it's a menu-driven interactive test program, and you run it from the operating system shell prompt. like, you just type it and it opens a menu. iconic behavior honestly.
here's what it lets you do:
- begin and end a session of BSS data acquisition from
bssStreamingApp, displaying the data as it arrives in real time β±οΈ - replay data acquired during the current session π
- replay data acquired during a prior session π
π the three parameters bestie, you gotta know these
to initiate the acquisition or replay of data from bssStreamingApp, the user must provide values for three parameters. three! count them! π
- BSS database name β all data acquired by the BSS session thread gets written to a BSS "database" comprising three files: table, list, and data. the name of the database is the root name that is common to the three files β like, for example,
db3.tbl,db3.lst,db3.datwould be the three files making up thedb3BSS database. so the root name isdb3. you see the vision. π - path name β all three files of the selected BSS database must reside in the same directory of the file system. no splitting them up, they're a package deal. the path name of that directory is required. π
- endpoint ID β to acquire streaming data issued by
bssStreamingApp, thebssrecvsession thread must open the BP endpoint to which that data is directed. for this purpose, the ID of that endpoint is needed. that's it, that's the endpoint ID. π°οΈ
π the menu (the main character of this whole page)
bssrecv offers the following menu options:
- Open BSS Receiver in playback mode β
bssrecvprompts the user for the three parameter values noted above, then opens the indicated BSS database for replay of the data in that database. πΏ - Start BSS receiving thread β
bssrecvprompts the user for the three parameter values noted above, then starts a background session thread to acquire data into the indicated database. every bundle that gets acquired is passed to a display function that prints a single line consisting ofNconsecutive'*'characters, whereNis computed as the data number at the start of the bundle's payload data, modulo 150. so it's like a little asterisk bar chart, kind of a slay. β¨ <br> > heads up though: the database is not open for replay at this time. π« - Run BSS receiver thread β
bssrecvprompts the user for the three parameter values noted above, then starts a background session thread to acquire data into the indicated database (displaying the data as described for option 2 above) and also opens the database for replay. best of both worlds, she contains multitudes. π - Close current playback session β
bssrecvcloses the indicated BSS database, terminating replay access. bye bye playback π - Stop BSS receiving thread β
bssrecvterminates the current background session thread. replay access to the BSS database, if currently open, is not terminated. so the thread stops but the replay keeps vibing. π¦ - Stop BSS Receiver β
bssrecvterminates the current background session thread. replay access to the BSS database, if currently open, is also terminated. this one takes everything out. π - Replay session β
bssrecvprompts the user for the start and end times bounding the reception interval that is to be replayed, then displays all data within that interval in both forward and reverse time order. the display function performed for this purpose is the same one that is exercised during real-time acquisition of streaming data. yes, same display function, consistent queen. π - Exit β
bssrecvterminates. that's the door. go home. πͺ
β¨ EXIT STATUS β¨
"0"βbssrecvhas terminated. zero, as in zero problems, as in we're done here. β
β¨ FILES β¨
no configuration files are needed. none. zero. nothing to set up, we love a low-maintenance icon. π
β¨ ENVIRONMENT β¨
no environment variables apply. the environment said "not my business" and honestly, respect. π
β¨ BUGS β¨
report bugs to <ion-bugs@korgano.eecs.ohiou.edu>. like actually report them, don't just complain in the group chat. π
β¨ SEE ALSO β¨
π bestie note: this page was brought to you byperl v5.24.1, dated2016-07-07. yes she's a 2016 baby and she's still serving. periodt. πβ¨
π¦ where this page comes from
- ubuntu jammy: ion 3.2.1+dfsg-1.1 Β· BSD-3-Clause
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms