1. You need a test to wait for the timer to countdown all the way and confirm FW is receiving the request. I suggest setting the inerval to 5 min and add a way to wait 5 min max until we receive the Request from UI.. e.g. To listen for a UI message look into can_interface.register_receiving_publication_function().. example in Solution infusion. 2. I would like a test during the timer running to change the interval time and verify the count down updates per the new interval. e.g. set 30 min and verify the count down is going down to the nearest 30 min interval, Open the vitals interval popup and change to 5 min and confirm then test the countdown udpates to countdown to the nearest 5 min mark
How can settings be pending when you set that flag to TRUE in the code below this? And why would we want to use uf volume setting in the else part of this ternary?
I don't think the number of samples is what you want as 3rd parameter. You want number of bytes so 4 x number of samples so you should pass "sizeof( roRRSamples )".
Even though we are giving the type a name at the bottom of the enum, we typically still want to give the enum a name up top here. See other enums throughout code for examples.
when I get the version with python3 version.py it will show the correct branch and commit version instead of just 1.0.0, which tells nothing. I use this when they ask what version of dialin I have, as I know the branch, but not the commit version, and it's faster with this then asking git around.
Is this always needed or is it only needed in one or more specific modes (i.e. gen dialysate mode)? If only needed in specific modes, I think this should be called from those modes (similar to BC exec).
Thanks for catching that. Yes, this was an accidental change on my part. I’ll revert it and proceed with deleting ModeTxParams.c and the related header files as suggested.
You are running release
CR4.8.14
FE4.8.14
(20240111091859 2024-01-11 09:20),
please report your release number when reporting bugs.
