leahi-common

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
LDT-1195: Added balancing chamber idle state

its a standard c library , for that no need to comment. using ceil() function

its a standard c library , for that no need to comment. using ceil() function

it is used for publish

it is used for publish

This is a default framework for all modules, even though there is nothing right now, left it as it is.

This is a default framework for all modules, even though there is nothing right now, left it as it is.

I don't see it being used in this state. Do we need this?

I don't see it being used in this state. Do we need this?

I don't think we need a start state as this state is doing nothing. It is just transitioning to the next state. We can just directly start from the next state.

I don't think we need a start state as this state is doing nothing. It is just transitioning to the next state. We can just directly start from the next state.

I think we have to define macros for magic number.

I think we have to define macros for magic number.

Why NUM_OF_?

Why NUM_OF_?

Variable name suggests it is an action/cmd from UI. Comment suggests it is the number of actions. Which is it? And we should initialize in the init function - not here.

Variable name suggests it is an action/cmd from UI. Comment suggests it is the number of actions. Which is it?
And we should initialize in the init function - not here.

I think we have to include a comment specifying what function is being used from this file.

I think we have to include a comment specifying what function is being used from this file.

Is this really a timer counter? Looks like a flow rate.

Is this really a timer counter? Looks like a flow rate.

Updated

Updated

Added back

Added back

Updated

Updated

LDT-3344 merge Beta2.0 changes to develop

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

LDT-3344 merge Beta2.0 changes to staging

I don't see why we need the extra precision here. I suspect a 64-bit division is expensive (s/w library implementation instead of co-processor) so I don't like to use doubles unless it is truly nec...

I don't see why we need the extra precision here. I suspect a 64-bit division is expensive (s/w library implementation instead of co-processor) so I don't like to use doubles unless it is truly necessary.

Add blank line before return.

Add blank line before return.

0.0F

0.0F

Use "F64" macro instead of double.

Use "F64" macro instead of double.

Yes , right now its void , so that's why i didn't change that . I will push new code

Yes , right now its void , so that's why i didn't change that . I will push new code

setAirPumpState could return a BOOL (FALSE if range check fails or state invalid) that you can set result to.

setAirPumpState could return a BOOL (FALSE if range check fails or state invalid) that you can set result to.

Inputs is none or FPGA.

Inputs is none or FPGA.

done

done