piston_pump.py

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Why do we have an "ro" and an "fp" folder? Is "ro" folder obsolete (replaced by "fp")?

Why do we have an "ro" and an "fp" folder? Is "ro" folder obsolete (replaced by "fp")?

Isn't timestamp typically first (or last) in publish list?

Isn't timestamp typically first (or last) in publish list?

LEAHI-DIALIN-LDT-2655_Cannot override conductivity sensor temperature from the conductivity module
LEAHI-DIALIN-LDT-2655_Cannot override conductivity sensor temperature from the conductivity module
done - as part of this comment, the piston pump module was deleted

done - as part of this comment, the piston pump module was deleted

done

done

done

done

LDT-2352: Addressed code review comments

  1. … 4 more files in changeset.
This message ID (0xF0) is no longer valid? and remove empty spaces.

This message ID (0xF0) is no longer valid? and remove empty spaces.

Update the comments = Valve 7, D26.

Update the comments = Valve 7, D26.

Update the comments - Valve 4, D21

Update the comments - Valve 4, D21

Merged LDT-1196

  1. … 4 more files in changeset.
Merged LDT-1196

  1. … 8 more files in changeset.
LDT-2300: Resolved code review comments

  1. … 40 more files in changeset.
Done - timestamps added to DD, FP, and TD

Done - timestamps added to DD, FP, and TD

Done

Done

Done

Done

Done

Done

LEAHI-DIALIN-LDT-2352_Dialin: Update enumerations to match merged DD and FP
LEAHI-DIALIN-LDT-2352_Dialin: Update enumerations to match merged DD and FP
I'm not sure I really understand the question here, but I do know that the DD Heaters data is being published with this handler: I've organized all heater data into a nested dictionary so that only...

I'm not sure I really understand the question here, but I do know that the DD Heaters data is being published with this handler: I've organized all heater data into a nested dictionary so that only one "variable" is being published. The same goes for the other publish functions before each handler. I will reorganize the order of the published variables so that timestamp is listed last.

No timestamp?

No timestamp?

I didn't see dbg variables in the publish list above.

I didn't see dbg variables in the publish list above.

Is msg_id_dd_heaters_data really being published here? Should it be? ** This comment applies to all classes as it appears you've done this everywhere. Also, I think we typically list the timestamp ...

Is msg_id_dd_heaters_data really being published here? Should it be? ** This comment applies to all classes as it appears you've done this everywhere.
Also, I think we typically list the timestamp last.

Replace "dg" with "dd".

Replace "dg" with "dd".

Replace "hd" with "dd".

Replace "hd" with "dd".