application

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
update the length check of the message in MessageGlobals.h const QHash<Gui::GuiActionType ,quint8> payloadLen { . . {Gui::GuiActionType::ID_DialysateOutletFlow , 10 * 4 }...

update the length check of the message in MessageGlobals.h

const QHash<Gui::GuiActionType ,quint8> payloadLen {
.
.
{Gui::GuiActionType::ID_DialysateOutletFlow                     ,  10 * 4       }, //10 parameters each 4bytes
.
.
}
param 11 is missing 01 F32-refUFVolMl 02 F32-measUFVolMl 03 F32-measRotSpdRPM 04 F32-measSpdRPM 05 F32-measMCSpdRPM ...

param 11 is missing

01    F32-refUFVolMl	              
02    F32-measUFVolMl	              
03    F32-measRotSpdRPM	            
04    F32-measSpdRPM	              
05    F32-measMCSpdRPM	            
06    F32-measMCCurrmA	            
07    F32-setPWMpct	                
08    F32-dopCorrOffset	            
09    F32-dopCalcRate	              
10    F32-ufCalcRate	              
11    U32-rotorHall	                
12    F32-currentSetUFRate          
param 11 is missing 01 F32-refUFVolMl 02 F32-measUFVolMl 03 F32-measRotSpdRPM 04 F32-measSpdRPM 05 F32-measMCSpdRPM ...

param 11 is missing

01    F32-refUFVolMl	              
02    F32-measUFVolMl	              
03    F32-measRotSpdRPM	            
04    F32-measSpdRPM	              
05    F32-measMCSpdRPM	            
06    F32-measMCCurrmA	            
07    F32-setPWMpct	                
08    F32-dopCorrOffset	            
09    F32-dopCalcRate	              
10    F32-ufCalcRate	              
11    U32-rotorHall	                
12    F32-currentSetUFRate          

I think we should use mL/min as is. and do not convert to Liter.

I think we should use mL/min as is. and do not convert to Liter.

Update the cpp as well

Update the cpp as well

UI-DEN-16335_UI VD S105 Disable confirm device config - [READY]
UI-DEN-16335_UI VD S105 Disable confirm device config - [READY]
UI-DEN-16335_UI VD S105 Bluetooth Missing Connect Logs - [READY]
UI-DEN-16335_UI VD S105 Bluetooth Missing Connect Logs - [READY]
UI-DEN-16335_UI VD S105 - P1B - Display UF Rate - [READY]
UI-DEN-16335_UI VD S105 - P1B - Display UF Rate - [READY]
RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

RESOLVED

Done.

Done.

Per our call, you have agreed to leave it above in this location. No change in location

Per our call, you have agreed to leave it above in this location. No change in location

We clarify this thread with a call.

We clarify this thread with a call.

This is no longer applicable due to the changes from our conversation.

This is no longer applicable due to the changes from our conversation.

I made the changes based on the call we had.

I made the changes based on the call we had.

not clear what it means.

not clear what it means.

In bluetoothInterface.cpp, there's a set of macros towards the top. NOTIFY_DEVICE_CONNECT and NOTIFY_DEVICE_DISCONNECT

In bluetoothInterface.cpp, there's a set of macros towards the top. NOTIFY_DEVICE_CONNECT and NOTIFY_DEVICE_DISCONNECT

I think actually, we should connected as paired state. As the re-connection is truly a re-connection after a connection/pairing has been established

I think actually, we should connected as paired state. As the re-connection is truly a re-connection after a connection/pairing has been established

where do you use this ctor?

where do you use this ctor?

I remember and and can we use reconnect as a Paired State.

I remember and and can we use reconnect as a Paired State.

Yes, ticket wants pairing, but you had stated in a call that we need to go by the SRS or the requirement and the requirement attached to the ticket said disconnection/connection of accessories

Yes, ticket wants pairing, but you had stated in a call that we need to go by the SRS or the requirement and the requirement attached to the ticket said disconnection/connection of accessories