dd-firmware

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Bamboo Commit: Updated the Copyright section and replaced tabs with 4 spaces

Merge LDT-3219-dd-d3-opens-as-soon-as-dd-is-po into staging

Bamboo Commit: Updated DDCommon.h with build versions from Bamboo.

Merge branch 'staging' of bitbucket.org:diality-cloud/dd-firmware into staging

Merge LDT-3219-dd-d3-opens-as-soon-as-dd-is-po into develop

LDT-3219 removing D3 open in standby mode
LDT-3219 removing D3 open in standby mode
Bamboo Commit: Updated DDCommon.h with build versions from Bamboo.

Bamboo Commit: Updated the Copyright section and replaced tabs with 4 spaces

Merge branch 'LDT-3514-dialin-config' into staging

LDT-2004: warning reduction relating to teensy driver. Removed Ifdefs for teensy and replaced some of them as beta 1.9 test config. WIP.

    • -5
    • +12
    /firmware/App/Controllers/Heaters.c
    • -16
    • +20
    /firmware/App/Monitors/Conductivity.c
    • -25
    • +33
    /firmware/App/Monitors/Temperature.c
Bamboo Commit: Updated DDCommon.h with build versions from Bamboo.

Merge branch 'LDT-3514-dialin-config' into develop

LDT-3514: wrapped ALARM_ID_FP_POWER_BUDGET_OUT_OF_RANGE around test config TEST_CONFIG_FP_DISABLE_RO_CURRENT_ALARM.

LEAHI-DD-FIRMWARE-LDT-3514_Dialin config request to disable IOFP current monitoring
LEAHI-DD-FIRMWARE-LDT-3514_Dialin config request to disable IOFP current monitoring
LDT-2004: warning reductions for teensy driver

added

added

added

added

LDT-3372: code review comments.

fixed.

fixed.

then we return false as expected

then we return false as expected

These are correct variable names based on their coefficient names in calculations of conductivity.

These are correct variable names based on their coefficient names in calculations of conductivity.

Can you clarify? this is allowing us to switch conductivity calculations based on the needs of the dialin user. ( systems team testing for accuracy )

Can you clarify? this is allowing us to switch conductivity calculations based on the needs of the dialin user. ( systems team testing for accuracy )

removed. thanks!

removed. thanks!

parameter check happens in getTeensyCondId

parameter check happens in getTeensyCondId

Yes as it is a way for us to identify if the teensy is not responding to us correctly. This along with no LED activity on the board helps us identify teensy failures

Yes as it is a way for us to identify if the teensy is not responding to us correctly. This along with no LED activity on the board helps us identify teensy failures