documentation error- is it transition start time ?
How are we entering the complete state? If we are planning to implement this function later, can we please add a TODO?
The public function name signalGoToInstallState is not sufficiently descriptive. Would renaming it to requestTubeSetInstall() be appropriate?
RESOLVED IN CODEWALKTHROUGH
This doesn't seem to be correct. Persistence should start once fill complete pressure is achieved, not after D65 opening?
Already set this above.
updated
yes, removed
updated to now change result to FALSE if we get a rr that is not NONE
remove demo code
Changed TD Opmode from Standy state to Treatment state
Remove this flag.
this method removed but updated elsewhere
remove this file and port anything needed into config.py for consistency just like we are doing in http://devapps.diality.us:8060/cru/LEAHI-TESTSUITES-LDT-1650-1
Move to ConductivityTeensy.c?
#ifdef
Why exposed? Shouldn't the SettingsBase decide where the children must anchor, or locate?
For signals and slots as we tlaked use blocks of
onSomething: { aFunctionCall() }
Unless there are multiple similar calls that need alignment in one line.
Please make vDateTime optional; if not set, return the current datetime epoch. It is better to use the 'timeEvent' (right now, onSetDateUIFinished).
Align '_', and '=' please.
Same as https://devapps.diality.us/cru/#LEAHI-APPLICATION-LDT-2727-1CFR-76783
Add the comments for coefficients. bring a top-level comment explaining the formula where these coefficients are being used.
Please remove for the above reasons.
I thought we made the 3000 timeout the default value and need to be set unless it is different. Please correct me if that is fixed on another branch.
What is happening here? Not clear if we need cartridge param. Let's remove it for now.
assigned 0.0F as per sameer's suggestion
Added
Add rinsebackPublishTimerCtr to outputs
The checks are back in a generic function.
use uniform naming convention. All other places used conductivity
This should be FS (file system), not the OS, unless you run a script and it is being executed by bash/sh.
Separate models in separate classes headerbar and water sample
To resolve the build failure with DD, haven't added all the features, instead added TODO comment
Is this defined elsewhere? We shouldn't define this in multiple places. I think it should be in one header file - maybe balancing chamber controller.
reworked to use the request functions we have in the respective op modes. They check the standby constraint
Why do we need to remove this?
#ifdef USE_TEENSY_CONDUCTIVITY_DRIVER
please align imports.
Remove extra line.
add a space between message and )
remove blank line.
I have deleted strings.py file from Bitbucket branch feature/LDT-1650-headerbar-information
change to closeOnStateChange
this was existing code.. Updated to use the DeviceController and made updates accordingly. And Tested and still works
BN Appprvoes
Updated to follow format
Please use the following commands from NetworkManager utilities, since in Leahi we are not using the wpa_supplicant directly:
nmcli connection delete DilaityIoT nmcli connection delete $(nmcli -t -f NAME connection show --active)
Got a suggestion or an issue? Discuss it on the Atlassian Community or visit Atlassian Support for other options.