SystemComm.c

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
DEN-8886: Added messages to request and receive UI version info. Request UI version info at start of POST.

  1. … 3 more files in changeset.
First sizeof() should have U32 (same as above).

First sizeof() should have U32 (same as above).

The first sizeof() has ALARM_ID_T. You converted that param to a U32 (which is appropriate) and so you should have U32 in that sizeof().

The first sizeof() has ALARM_ID_T. You converted that param to a U32 (which is appropriate) and so you should have U32 in that sizeof().

I think the data are floats, so 0 should be 0.0.

I think the data are floats, so 0 should be 0.0.

Sent events only for changed settings.

Sent events only for changed settings.

Set UF volume initially to 0 and removed this variable and related function.

Set UF volume initially to 0 and removed this variable and related function.

It is part of background task in the battery monitor exec function. The initial value is 0, we will wait here till we get status.

It is part of background task in the battery monitor exec function. The initial value is 0, we will wait here till we get status.

Done. I prefer generally output description, so refactor is easier. Normally, a refactor will often make these variables in the doxygen comment obsolete (variable name change).

Done. I prefer generally output description, so refactor is easier. Normally, a refactor will often make these variables in the doxygen comment obsolete (variable name change).

Dara Navaei Please take a look.

Dara Navaei Please take a look.

This message is requested by UI. UI wants to keep it consistent with other request message, in case there is reject reason in the future.

This message is requested by UI. UI wants to keep it consistent with other request message, in case there is reject reason in the future.

Removed.

Removed.

If fault mode calls the treatment log data collect function, the record can be zeroed also.

If fault mode calls the treatment log data collect function, the record can be zeroed also.

The transition function will call this init function.

The transition function will call this init function.

DEN-8679: Addressed code review

  1. … 9 more files in changeset.
Done.

Done.

Fixed.

Fixed.

Fixed.

Fixed.

Done.

Done.

The else is when AC power detected. Added clear alarm condition.

The else is when AC power detected. Added clear alarm condition.

DEN-8886: Added UI compatibility POST test. Updated alarm audio per latest HDD. Added handling of UI and DG version messages. Fixed watchdog POST. Added recovery check to watchdog POST.

  1. … 11 more files in changeset.
Merge branch 'DEN-8886-hd_dg_dev-self-tests-2-of-2' into develop

  1. … 18 more files in changeset.
Seems like the two states given as data are not very meaningful. Consider just setting before/after data to zero for this event.

Seems like the two states given as data are not very meaningful. Consider just setting before/after data to zero for this event.

Not sure this variable (and related get function) are needed.

Not sure this variable (and related get function) are needed.

User may not have changed all 4 settings. Should we only send events for those that actually changed?

User may not have changed all 4 settings. Should we only send events for those that actually changed?

I think this will be the time we initiate a treatment. Is that what we want? Or should we move this to transition function to capture time of treatment start?

I think this will be the time we initiate a treatment. Is that what we want? Or should we move this to transition function to capture time of treatment start?

Are there ever any reject reasons? Is this message requested by UI or sent unsolicited when ready?

Are there ever any reject reasons? Is this message requested by UI or sent unsolicited when ready?

I think we set UF volume to zero in TreatmentParams mode, so this condition should not be necessary.

I think we set UF volume to zero in TreatmentParams mode, so this condition should not be necessary.

Why not zero record here? I see it is zeroed just prior to creation at end of treatment, but that means this record may have prior treatment's data until current treatment is over.

Why not zero record here? I see it is zeroed just prior to creation at end of treatment, but that means this record may have prior treatment's data until current treatment is over.

If typical h/w response is very quick (e.g. < 1ms) and worst case is still pretty quick (e.g. < 5ms), then I think this is ok with the t/o there to prevent getting stuck in loop forever. Also, batt...

If typical h/w response is very quick (e.g. < 1ms) and worst case is still pretty quick (e.g. < 5ms), then I think this is ok with the t/o there to prevent getting stuck in loop forever.
Also, battery monitor is called from background task so we can be a little more relaxed about this.

Why would we zero it when no AC detected?

Why would we zero it when no AC detected?