Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Merge branch 'staging' of bitbucket.org:diality-cloud/dd-firmware into LDT-1195-dd-is-balancing-chamber-switching

do we need bracket here ? all text should start with capital

do we need bracket here ? all text should start with capital

Why a * here ?

Why a * here ?

is it write states or read state ?

is it write states or read state ?

is documentation correct ?

is documentation correct ?

Bamboo Commit: Updated DDCommon.h with build versions from Bamboo.

resolved merge conflicts for LDT-3677

LEAHI-DD-FIRMWARE-LDT-3677_Request: add SW config to enable defeatured IOFP control in the IOFP FW
LEAHI-DD-FIRMWARE-LDT-3677_Request: add SW config to enable defeatured IOFP control in the IOFP FW
LDT-3677 added fix to reset value when TC is disabled for Boost pump and defeatured

LDT-3749 addressed review comments

You are right, modified in all places

You are right, modified in all places

LDT-2008: code review comments.

LDT-3735: Fixed dependency between NVM files.

FALSE?

FALSE?

FALSE?

FALSE?

Should default be TRUE? If we are being asked to validate an jump to an invalid state, shouldn't we return FALSE?

Should default be TRUE? If we are being asked to validate an jump to an invalid state, shouldn't we return FALSE?

Vinayakam Mani, how does that signal happen normally? In your example, when would DD signal FP when starting pre-gen mode? If that signal happened in pre-gen transition function, it would always ha...

Vinayakam Mani, how does that signal happen normally? In your example, when would DD signal FP when starting pre-gen mode? If that signal happened in pre-gen transition function, it would always happen regardless of how we got to pre-gen mode.

Add comment that these modes not (yet?) supported.

Add comment that these modes not (yet?) supported.

LDT-3103 addressed code review comments and merged latest staging

Merge branch 'staging' into LDT-3103-closed-loop-control-pressure-threshold-fix

Why do some functions take sensor as a U32 and some as a CONDUCTIVITY_SENSORS_T? The latter seems appropriate.

Why do some functions take sensor as a U32 and some as a CONDUCTIVITY_SENSORS_T? The latter seems appropriate.

Remove blank line.

Remove blank line.

Remove blank line.

Remove blank line.

Add blank line before return.

Add blank line before return.

Add blank line before return.

Add blank line before return.

Remove blank line.

Remove blank line.

Why are we switching sensors around?

Why are we switching sensors around?