Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Remove blank line.

Remove blank line.

Remove blank line.

Remove blank line.

Remove blank line.

Remove blank line.

Add a blank line after private defs banner.

Add a blank line after private defs banner.

Remove extra blank line.

Remove extra blank line.

Remove blank line.

Remove blank line.

Just 1 blank line here is sufficient.

Just 1 blank line here is sufficient.

Since these are coming from UI s/w now (right?), I don't think they should begin with "test" which we reserve for messages that only come from Dialin. Move up above "test" functions.

Since these are coming from UI s/w now (right?), I don't think they should begin with "test" which we reserve for messages that only come from Dialin.
Move up above "test" functions.

This is a common unit - could be built into DD or TD f/w. Need #ifdef to see if _DD_ or _TD_ build so you know which messaging and records to initialize.

This is a common unit - could be built into DD or TD f/w. Need #ifdef to see if _DD_ or _TD_ build so you know which messaging and records to initialize.

These don't look like UI alarms. Comment suggests we already know what to call these. Why aren't we just using the names we want?

These don't look like UI alarms. Comment suggests we already know what to call these. Why aren't we just using the names we want?

Make sure Dialin gets these too when you merge.

Make sure Dialin gets these too when you merge.

LEAHI-DD-FIRMWARE-LDT-3975_Water Treatment and Degassing - FW Iteration - 4/4:
LEAHI-DD-FIRMWARE-LDT-3975_Water Treatment and Degassing - FW Iteration - 4/4:
LEAHI-DD-FIRMWARE-LDT-4246_FW Support for UI Demo
LEAHI-DD-FIRMWARE-LDT-4246_FW Support for UI Demo
Add a blank line before group end marker.

Add a blank line before group end marker.

Are we only doing DD messages? And since these could be coming from UI now, these shouldn't be considered "Dialin" messages anymore and should be moved up to section before 0x8000 IDs where normal ...

Are we only doing DD messages?
And since these could be coming from UI now, these shouldn't be considered "Dialin" messages anymore and should be moved up to section before 0x8000 IDs where normal system messages are defined.

Bamboo Commit: Updated the Copyright section and replaced tabs with 4 spaces

  1. … 5 more files in changeset.
by the end of S27 we will know if we need to keep this module. If so, then we can integrate it into PIControllers.c

by the end of S27 we will know if we need to keep this module. If so, then we can integrate it into PIControllers.c

If this is the core change, can we introduce this logic in PI controller.c itself with a simple flag check (say, if 'IsDerivativeEnabled" set to true, add the derivative signal to Control signal. e...

If this is the core change, can we introduce this logic in PI controller.c itself with a simple flag check (say, if 'IsDerivativeEnabled" set to true, add the derivative signal to Control signal. else, just a PI control signal would work. (something similar to Feed forward enabled flag)

nope. removed.

nope. removed.

fixed

fixed

fixed

fixed

fixed

fixed

fixed

fixed

LDT-3218: code review comments

  1. … 3 more files in changeset.
Add blank line before return.

Add blank line before return.

Add blank line after declarations.

Add blank line after declarations.

Why U32? Why not RECOVER_STATE_T?

Why U32? Why not RECOVER_STATE_T?