We need to decide what DG should do if HD comm times out. Alarm may not make sense since HD apparently not connected to receive/display alarm. Appropriate action may be mode specific.
We need to decide what DG should do if HD comm times out. Alarm may not make sense since HD apparently not connected to receive/display alarm. Appropriate action may be mode specific.
Not Always. ovData will stay True until the Reset function is called (which is then assigned ovInitData's value). Our handler only calls the Set/Reset function. No parameters are given.
Not Always. ovData will stay True until the Reset function is called (which is then assigned ovInitData's value). Our handler only calls the Set/Reset function. No parameters are given.
Looks like it was commented out in this commit in August. http://dvm-linux02:7990/projects/DG/repos/dgfirmware/commits/47205a5002f27add91d8548f31c8a6fa18993fea#firmware/App/Services/SystemComm.c ...
Looks like it was commented out in this commit in August.
I noticed you are using a U32 as a boolean without typecasting. I know a boolean is an unsigned integer behind the scenes but to be specific we should explicitly typecast.
I noticed you are using a U32 as a boolean without typecasting. I know a boolean is an unsigned integer behind the scenes but to be specific we should explicitly typecast.