Yamcs Server Updates (v3.x.x)
Yamcs 3.4.10 [.rpm] Jun 18, 19
- Include detail of base commands in response to MDB requests
Yamcs 3.4.9 [.rpm] May 20, 19
- Restrict the number of parameter archive filler tasks that run concurrently to 1 (to avoid OOM)
Yamcs 3.4.8 [.rpm] Apr 11, 19
- Fix algorithms having as input binary raw or engineering values
Yamcs 3.4.7 [.rpm] Oct 25, 18
- Fix for issue #277: Event Viewer: sorting makes it open the wrong “event details”
Yamcs 3.4.6 [.rpm] Oct 01, 18
- added a workaround for a bug where the data is not garbage collected after a parameter archive refill happens
Yamcs 3.4.5 [.rpm] Jul 11, 18
- fixed the replay service to always take into account the parameter group exclusion option implemented in 3.4.4
Yamcs 3.4.4 [.rpm] May 09, 18
- added the possibility to exclude parameter groups from replays
Yamcs 3.4.3 [.rpm] Mar 28, 18
- fixed the replay not starting at the correct time
- change the serialized XTCEDB filename to limit its length (use SHA-1 of the old name)
Yamcs 3.4.2 [.rpm] Feb 12, 18
- fixed Artemis data links
- the parameter select dialog from the Archive Browser will show now also parameters that are not part of containers
Yamcs 3.4.0 [.rpm] Dec 06, 17
- moved artemis into a separate source project which yamcs-core does not depend on.
Allow to connect to an external Artemis server by specifying artemisUrl: “tcp://…” into yamcs.
.yaml or yamcs.yaml
- added the possibility to restart instances and send information about current connected instance/processor via websocket
- added command history cascading via Artemis
- TcpTcDataLink: added an option to limit the rate of commands sent
- make an rpm for yamcs-simulation which can be used together with the yamcs rpm to get a yamcs sistem runing.
Yamcs 3.3.1 [.rpm] Nov 13, 17
- Moved the MulticastTmDataLink out of the yamcs-core (into yamcs-dass) because it’s DaSS specific
- Added a new UdpTmDataLink to replace the removed multiacst functionality. Contrary to the multicast service, the UDP one receives packets as CCSDS packets without any extra header
Yamcs 3.3.0 [.rpm] Oct 24, 17
- Support index requests with request parameters encoded in the HTTP request body in order to allow a large number of packets to be specified (otherwise, the request would exceed maximum URI size).
- Allow alias parameter name references in the MDB SpreadSheets (including in the Alarm sheet which didn’t allow any reference at all)
- Fixed the reading of ranges (inclusive vs exclusive) from XTCE XML files
- Added two options to websocket parameter subscription:
- send an update when parameters are expiring (by default false)
- send the first value from cache if available (by default true)
- Change the expirationTime (absolute time) to expireMillis (relative time) in the ParameterValue.
- Implemented parameter expiration in the USS web displays
- Allow to specify custom decoders to be used in container(packet) processing
- Added binary data encoding with leading size specified (similar to string)
- Changed the spreadsheet to make clearer the difference between raw value, encoding (how to decode the raw value from the binary) and engineering value (raw value passed through a calibration function)
- For standalone parameters (i.e. not extracted from XTCE packets) coming without an engineering value, calibrate (raw->eng value) them inside the processor rather than before being injected in the stream. This means the parameters are stored in the stream archive also in the initial form (could be raw+eng, only raw or only eng) and they are calibrated (using the current MDB) for each replay Of course ParameterArchive will store them calibrated.
- Added a command “yamcs confcheck” to check a complete yamcs configuration by loading the services without starting them
Yamcs 3.2.2 [.rpm] May 17, 17
- Fixed tag handling in Yamcs Monitor/Archive Browser
Yamcs 3.2.1 [.rpm] May 15, 17
- Added an option to “yamcs rocksdb compact” to specify the target file size and changed the default size from 64MB to 256MB
- Java expressions can be used for raw->engineering value calibration (in addition to polynomial and spline). This allow to use mathematical expressions such as logarithms and trigonometric functions.
- fixed seek in replays
- Fix in Yamcs Monitor: remove closed processors from the list
- RocksDB: set by default the table block cache to 8MB (previously it was disabled)
Yamcs 3.2.0 [.rpm] Apr 18, 17
- Improved the yamcs command line with several new sub-commands (xtcedb, parchive)
- Removed Artemis based replays and management (control processors)
- Added a new yatch(table/stream) data type PARAMETER_VALUE to replace PROTOBUF(ParameterValue) for more flexibility
Yamcs 3.1.1 [.rpm] Mar 14, 17
- fixed a bug in the RestClient causing the Swing client tools (Yamcs Monitor &co) to NPE when doing File -> Connect to Yamcs (connection by specifying the http url in the command line still worked)
Yamcs 3.1.0 [.rpm] Mar 14, 17
- MDB: allow parameters without raw types if they are not part of a container
- REST Api: add option to get the details of parameters in ‘list parameter’
- Ease extension of the FilePollingTmDatalink and TmFileReader.
- if processor -> cacheall is disabled, retrieve at least all parameters that have alarms associated
- allow algorithm manager to be usable in replays
- Improved XTCE XML parsing support: - read alarms - read string parameters - read multiple space systems
- Removed the name from the DataEncoding classes (in XTCE DataEncodings are not named)
- allow to remove a parameter from the XtceDB (to be used in a controlled way only)
- Changed the order of starting the services:
- All global services are created
- All instance services are created
- All global services are started
- All instance services are started
Used to be 1,3,(2,4)+ - and this makes for example the HttpServer to be started before the instances are created and some methods (like subscribe event,time,etc) will fail at first because the processor is not available.
- updated to RocksDB 5.1.2
Yamcs 3.0.0 [.rpm] Jan 12, 17
This is the first non-zero (0.x.y) release of Yamcs after almost 10 years of development and 4 years after making it open-source. We call it 3.0 instead of 1.0 because internally at Space Applications we have already defined Yamcs 1 and 2 for the versions used in actual Control Centres.
- there is no difference between version 3.0 and 0.30.0 except the version number.