view RefPrj/Firmware/.project @ 635:66c8a4ff9fc4

Debounce fallback warning: In previous versions the fallback option (automatical setting of a fixed setpoint) was only done for communication timeout scenario in combination with a HUD. It is now also applied in case all sensors are rated as out of bounds. The signaling of the fallback warning (including optional automatic setpoint change) is now done taking a 5 seconds debounds time into account. In case a fallback warning is active, then the only way to reset it is by selecting a new setpoint or by changing the sensor configuration (no change compared to previous implementation
author Ideenmodellierer
date Wed, 24 Feb 2021 21:03:22 +0100
parents d24395f7c939
children
line wrap: on
line source

<?xml version="1.0" encoding="UTF-8"?>
<projectDescription>
	<name>OSTC4_Firmware</name>
	<comment></comment>
	<projects>
	</projects>
	<buildSpec>
		<buildCommand>
			<name>org.eclipse.cdt.managedbuilder.core.genmakebuilder</name>
			<triggers>clean,full,incremental,</triggers>
			<arguments>
			</arguments>
		</buildCommand>
		<buildCommand>
			<name>org.eclipse.cdt.managedbuilder.core.ScannerConfigBuilder</name>
			<triggers>full,incremental,</triggers>
			<arguments>
			</arguments>
		</buildCommand>
	</buildSpec>
	<natures>
		<nature>org.eclipse.cdt.core.cnature</nature>
		<nature>org.eclipse.cdt.managedbuilder.core.managedBuildNature</nature>
		<nature>org.eclipse.cdt.managedbuilder.core.ScannerConfigNature</nature>
		<nature>fr.ac6.mcu.ide.core.MCUProjectNature</nature>
		<nature>fr.ac6.mcu.ide.core.MCUSingleCoreProjectNature</nature>
	</natures>
	<linkedResources>
		<link>
			<name>Common</name>
			<type>2</type>
			<locationURI>OSTC4/Common</locationURI>
		</link>
		<link>
			<name>Discovery</name>
			<type>2</type>
			<locationURI>OSTC4/Discovery</locationURI>
		</link>
	</linkedResources>
	<variableList>
		<variable>
			<name>OSTC4</name>
			<value>$%7BWORKSPACE_LOC%7D/ostc4</value>
		</variable>
	</variableList>
</projectDescription>