hdfirmware / firmware / App / Services

SystemCommMessages.h

Clone Tools

Stats

Commits this week: 0
Total Committers: 13
Last Commit: 19 Nov
Commits this week: 0

Lines of code count not available

Commit Activity

Commits By Day In Week
52 week commits volume
Commits By Day In Week
Commits by day
Commits By Day In Week
Commits by hour
Commits By Hour In Day
Commit calendar
 

Most active committers (90 days)

loading
loading
  • last updated a few seconds ago
All Commits Reviews
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Wednesday 03 Nov 2021
3:42 pm

Sean Nash

Merge branch 'DEN-9906-hd_dev-flow-measurement-changes' into develop

Options
    • -11
    • +0
    ./SystemCommMessages.h
  2. … 15 more files in changeset.
3:11 pm

Sean Nash

Fixed bugs DEN-10983 and DEN-10982. Removed obsolete code associated with obsoleted components/features.

Options
    • -11
    • +0
    ./SystemCommMessages.h
  2. … 12 more files in changeset.
Monday 01 Nov 2021
10:19 am

Sean Nash

Added file header.

Added file header.

Friday 29 Oct 2021
1:51 pm

Hung Nguyen <hnguyen@diality.com>

Fixed merge conflict

Options
    • -5
    • +9
    ./SystemCommMessages.h
  2. … 19 more files in changeset.
Thursday 28 Oct 2021
12:59 pm

Hung Nguyen <hnguyen@diality.com>

DEN-9906 Fixed merge conflict

Options
    • -4
    • +5
    ./SystemCommMessages.h
  2. … 4 more files in changeset.
12:45 pm

Hung Nguyen <hnguyen@diality.com>

DEN-9906 Implement HD dialysate flow sensor

Options
    • -1
    • +4
    ./SystemCommMessages.h
  2. … 4 more files in changeset.
Wednesday 27 Oct 2021
4:12 pm

Sean Nash

DEN-9906: Added overrides for blood pump rotor count and arterial pressure offset. Removed unused handling of DG data and related functions/variables. Fixed DEN-10973.

Options
    • -4
    • +5
    ./SystemCommMessages.h
  2. … 11 more files in changeset.
10:48 am

hnguyen  (deleted user)

RESOLVED IN CODE WALKTHROUGH

RESOLVED IN CODE WALKTHROUGH

10:48 am

hnguyen  (deleted user)

RESOLVED IN CODE WALKTHROUGH

RESOLVED IN CODE WALKTHROUGH

10:48 am

hnguyen  (deleted user)

RESOLVED IN CODE WALKTHROUGH

RESOLVED IN CODE WALKTHROUGH

10:47 am

hnguyen  (deleted user)

RESOLVED IN CODE WALKTHROUGH

RESOLVED IN CODE WALKTHROUGH

10:45 am

hnguyen  (deleted user)

RESOLVED IN CODE WALKTHROUGH

RESOLVED IN CODE WALKTHROUGH

10:40 am

Behrouz NematiPour

RESOLVED IN CODE WALKTHROUGH.

RESOLVED IN CODE WALKTHROUGH.

10:39 am

Behrouz NematiPour

RESOLVED IN CODE WALKTHROUGH.

RESOLVED IN CODE WALKTHROUGH.

10:37 am

Behrouz NematiPour

RESOLVED IN CODE WALKTHROUGH.

RESOLVED IN CODE WALKTHROUGH.

10:36 am

Behrouz NematiPour

RESOLVED IN CODE WALKTHROUGH.

RESOLVED IN CODE WALKTHROUGH.

8:49 am

Sean Nash

Fixed.

Fixed.

8:43 am

Sean Nash

Fixed.

Fixed.

8:41 am

Sean Nash

If using a "==" comparison operator, I like to put the literal first so that the compiler will error if I accidentally use "=" instead. Otherwise, I like to put the literal last because it reads be...

If using a "==" comparison operator, I like to put the literal first so that the compiler will error if I accidentally use "=" instead.
Otherwise, I like to put the literal last because it reads better.

8:38 am

Sean Nash

I was thinking 150 was perhaps too fast for UI. But you're right - that only seems to be true at startup. I'll put back to 150.

I was thinking 150 was perhaps too fast for UI. But you're right - that only seems to be true at startup. I'll put back to 150.

8:36 am

Sean Nash

This toggle macro is designed to be generic - so does not assume you are toggling between 0 and 1. Could be toggling between ON and OFF or OPEN and CLOSED, etc... So you have to give the macro the ...

This toggle macro is designed to be generic - so does not assume you are toggling between 0 and 1. Could be toggling between ON and OFF or OPEN and CLOSED, etc... So you have to give the macro the two values that you are toggling between.

8:34 am

Sean Nash

FALSE is simply zero and TRUE is one. In case a boolean is somehow corrupted to something other than 1 or 0, I like to err on the side of safety. So the way I have it now, if isBloodPumpRunning() g...

FALSE is simply zero and TRUE is one. In case a boolean is somehow corrupted to something other than 1 or 0, I like to err on the side of safety.
So the way I have it now, if isBloodPumpRunning() gets corrupted to > 1, it will consider that the pump is not running which is the safer thing to do.

8:30 am

Sean Nash

currentSubMode is already a U32 - no cast needed.

currentSubMode is already a U32 - no cast needed.

Tuesday 26 Oct 2021
10:24 pm

Behrouz NematiPour

Shouldn't be? ( FALSE == isBloodPumpRunning() )

Shouldn't be?

( FALSE == isBloodPumpRunning() )
10:06 pm

Behrouz NematiPour

why here currentMode is casted while currentSubMode didn't? data.opMode = (U32)currentMode; data.subMode = currentSubMode;

why here
currentMode is casted while currentSubMode didn't?

data.opMode = (U32)currentMode;
data.subMode = currentSubMode;
9:45 pm

Behrouz NematiPour

Does a toggle function/macro need the second and third parameters, since whatever value it currently has should be reversed?

Does a toggle function/macro need the second and third parameters, since whatever value it currently has should be reversed?

9:42 pm

Behrouz NematiPour

Could you please explain why the ack timeout increased, is it for POST ack issues or there were other things too?

Could you please explain why the ack timeout increased, is it for POST ack issues or there were other things too?

2:32 pm

hnguyen  (deleted user)

should be if ( TRUE != getRinsebackCompleted() ) for consistency

should be if ( TRUE != getRinsebackCompleted() ) for consistency

2:31 pm

hnguyen  (deleted user)

add last else else { }

add last else
else
{

}

2:31 pm

Sean Nash

Fixed.

Fixed.