Drivers

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
move static function after public function

move static function after public function

let public function on top

let public function on top

Let all public functions come on top for all files

Let all public functions come on top for all files

LDT-1886 updated the code in the ejector motor disable function

Should we comment this out before merging?

Should we comment this out before merging?

LDT-1886 addressed the code review comments

  1. … 3 more files in changeset.
Done

Done

Done

Done

Align =

Align =

Should be 2 blank lines above/below test banner.

Should be 2 blank lines above/below test banner.

LDT-1886 updated the pinch valves homing sequence

  1. … 4 more files in changeset.
Done

Done

LDT-1886 updated the ejectormotor initialization

Should we initialize to inactive (and use #define)?

Should we initialize to inactive (and use #define)?

Took note that the FPGA interface is at the driver level.

Took note that the FPGA interface is at the driver level.

Done

Done

LDT-1886 updated the ejectors code. Transferred the FPGA interface to the ejector motor level.

  1. … 6 more files in changeset.
Should this be an enum at driver level? Driver get would return enum so controller doesn't have to figure out what it means.

Should this be an enum at driver level? Driver get would return enum so controller doesn't have to figure out what it means.

Use U32 unless there is a good reason to use U08.

Use U32 unless there is a good reason to use U08.

Why bypassing driver here?

Why bypassing driver here?

Why are we bypassing driver here?

Why are we bypassing driver here?

Then your doxygen return comment looks backward.

Then your doxygen return comment looks backward.

Why is controller bypassing driver to get to fpga?

Why is controller bypassing driver to get to fpga?

According to the HDD, it is a '1' when inactive and becomes a '0' when active. It becomes active when it reaches the position.

According to the HDD, it is a '1' when inactive and becomes a '0' when active. It becomes active when it reaches the position.

Seems backward. Why is inactive = TRUE? I would expect TRUE to indicate that the optical sensor is detecting home (retracted) position.

Seems backward. Why is inactive = TRUE? I would expect TRUE to indicate that the optical sensor is detecting home (retracted) position.

LEAHI-TD-FIRMWARE-LDT-1886_Blood Set Auto-Load and Auto-Eject - TD
LEAHI-TD-FIRMWARE-LDT-1886_Blood Set Auto-Load and Auto-Eject - TD
documentation error- is it transition start time ?

documentation error- is it transition start time ?