SystemCommTD.c

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
LEAHI-TD-FIRMWARE-LDT-2199_Beta 1.0 FW Integration - TD Implementation
LEAHI-TD-FIRMWARE-LDT-2199_Beta 1.0 FW Integration - TD Implementation
LEAHI-TD-FIRMWARE-LDT-2199_Beta 1.0 FW Integration - TD Implementation
LEAHI-TD-FIRMWARE-LDT-2199_Beta 1.0 FW Integration - TD Implementation
Fixed.

Fixed.

Fixed.

Fixed.

Fixed.

Fixed.

When Systems gives me Leahi terms, they will be very small fractions.

When Systems gives me Leahi terms, they will be very small fractions.

Fixed.

Fixed.

You're right. Old comment from Denali. Fixed.

You're right. Old comment from Denali. Fixed.

Came from Denali, so I believe this is what they wanted. The nearly 5 minutes is the one the user sees.

Came from Denali, so I believe this is what they wanted. The nearly 5 minutes is the one the user sees.

space needed in sizeof( BOOL ). Follow the same for line no : 526.

space needed in sizeof( BOOL ). Follow the same for line no : 526.

Please update I/O.

Please update I/O.

Add alarm.

Add alarm.

Please add param.

Please add param.

just 0.0F would work?

just 0.0F would work?

Is it just on/off control or variable speed control?

Is it just on/off control or variable speed control?

Alarm descriptions and trigger conditions calls out "more than 4 minutes" and Instructions says, "nearly 5 minutes". is this intended to display this way?

Alarm descriptions and trigger conditions calls out "more than 4 minutes" and Instructions says, "nearly 5 minutes". is this intended to display this way?

Why?

Why?

Restore bulk of this function for now.

Restore bulk of this function for now.

I am. Didn't want to wait (up to 50ms) for pump to stop if hard stop is requested. So forcing to off immediately. Not how I would ordinarily want to handle this, but in this case I am.

I am. Didn't want to wait (up to 50ms) for pump to stop if hard stop is requested. So forcing to off immediately. Not how I would ordinarily want to handle this, but in this case I am.

Why is this necessary? I would think state machine would already handle this.

Why is this necessary? I would think state machine would already handle this.

TD-LDT-736_General Alarm Requirements TD
TD-LDT-736_General Alarm Requirements TD
I can update the numbers.

I can update the numbers.

But what is 0x3000?

But what is 0x3000?