dialin

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Merge branch 'develop' of ssh://dvm-linux02:7999/vv/dialin into develop

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

DEN9906 Updated code to publish raw conductivity data

DEN-11705 worked on the software configuration

These are all the same changes from http://dvm-linux02:8060/cru/DIALIN-BUG-S63-1

These are all the same changes from

http://dvm-linux02:8060/cru/DIALIN-BUG-S63-1

These are all the same changes from http://dvm-linux02:8060/cru/DIALIN-BUG-S63-1

These are all the same changes from

http://dvm-linux02:8060/cru/DIALIN-BUG-S63-1

This looks backwards. double should be 8, float should be 4.

This looks backwards. double should be 8, float should be 4.

Header suggests there are only 2 parameters. What is this 3rd param and why is it zero?

Header suggests there are only 2 parameters. What is this 3rd param and why is it zero?

DIALIN-UI-S63
DIALIN-UI-S63
Merge branch 'UI_S63' into develop

Band-aid the Blood prime message for now

- UI and Dialin are not in sync with the MessageList.

Merge branch 'DEN-11980-sw_dev-sprint-64' into develop

DIAL-145: Added get function for UI version. Removed debugging statement.

Merge branch 'DEN-11750-dg_dev-dg-dialysate-temperature-control-tune-up' into develop

DEN-11750 updated the calibration record

Merge branch 'DEN-11750-dg_dev-dg-dialysate-temperature-control-tune-up' into develop

DEN-11750 updated the nv_ops_utils.py

Merge branch 'DEN-11980-sw_dev-sprint-64' into develop

DIAL-145: Implemented UI version request in hemodialysis_device.py. Handler method as well.

DEN-11750 updated the software configurations

Overall the use of this file is a bit funny. If this is ran within a Squish test, maybe we should rename/move the file (Ex: system_env_BAT.py) to be more coherent as it currently implies that it is...

Overall the use of this file is a bit funny. If this is ran within a Squish test, maybe we should rename/move the file (Ex: system_env_BAT.py) to be more coherent as it currently implies that it is unit testing something in this folder when it is testing the ENV and CAN.

Totally in favor of the workaround.

Totally in favor of the workaround.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

Fixed.

Fixed.

DIALIN-BUG-S63: DIALIN-BUG-S63-1

- Addressed code review comments.

That is correct and I have something in mind to improve the code. But I believe this is more related to Dialin bugs: 1 - First one which we talked about that Dialin creates all the objects even it...

That is correct and I have something in mind to improve the code.

But I believe this is more related to Dialin bugs:
1 - First one which we talked about that Dialin creates all the objects even it is not being used in the _init_.py files which cause different use-cases of the API to be not compatible together and can't be used together.
2 - the other issue is that the Dialin as an API should by nature be a passive code and just have the capabilities to be extended those observers have to be removed from Dialin.

For now, I'll put a workaround for this, and later we should discuss the better implementation of the Dialin API.

Separate functions have been created to keep the string representations clearer. It is not safe to use something like "b" or "B" since anyone can even but something like "hello" which probably does...

Separate functions have been created to keep the string representations clearer.
It is not safe to use something like "b" or "B" since anyone can even but something like "hello" which probably doesn't mean anything and is an error.
to overcome this flow the different functions implemented here have to be used.

Also since the intention of the function here is clear the length has been calculated regarding the type conversion in each function.
which helps have a lot of clearer code.
Please refer to the usage in:
d9b45e5b52db2540a79cbc8795d82dda4fd3984b on dialin develop branch.

the code has changed from:

        major = struct.unpack('B', bytearray(
            message['message'][self.START_POS_MAJOR:self.END_POS_MAJOR]))
        minor = struct.unpack('B', bytearray(
            message['message'][self.START_POS_MINOR:self.END_POS_MINOR]))
        micro = struct.unpack('B', bytearray(
            message['message'][self.START_POS_MICRO:self.END_POS_MICRO]))
        build = struct.unpack('H', bytearray(
            message['message'][self.START_POS_BUILD:self.END_POS_BUILD]))
        compatibility = struct.unpack('H', bytearray(
            message['message'][self.START_POS_COMPAT:self.END_POS_COMPAT]))

which was so error-prone to the following code:

        major, index = bytearray_to_byte(payload, index, False)
        minor, index = bytearray_to_byte(payload, index, False)
        micro, index = bytearray_to_byte(payload, index, False)
        build, index = bytearray_to_short(payload, index, False)
        compt, index = bytearray_to_integer(payload, index, False)