Dashboard

Welcome Message

Welcome to Atlassian Crucible with Fisheye .

To report a bug or suggest a feature please raise an issue in our public Jira.

Customize this welcome note.

Support

You are running Crucible 4.8.14 with Fisheye 4.8.14 (20240111091859 2024-01-11 09:20)

If you are experiencing any issues, please contact your administrator. You may also want to browse the documentation or search the support forums. Still stuck? You can start a support ticket at support.atlassian.com or raise a bug or feature request at jira.atlassian.com.

Customize the support message.

Today
44 mins ago

Vendor - TEL - Jashwant Gantyada

LDT-3103 pressure range check for diff qd for d48 pump

Options
    • -2
    • +30
    /firmware/App/Controllers/BalancingChamber.c
1 hr ago

Dara Navaei

LDT-3259 work in progress. Updating the FPGA module to Leahi

Options
    • -1
    • +1
    /firmware/App/BLCommon.h
    • -8
    • +50
    /firmware/App/Services/FPGA.c
1 hr ago

Vendor - TEL - Jashwant Gantyada

2 hrs ago

Raghu Kallala

2 hrs ago

Raghu Kallala

2 hrs ago

Dara Navaei

Bamboo Commit: Updated Branch staging For Project DD

Options
    • -5
    • +5
    /DD/BETA/DD_BETA_Manifest.csv
    • binary
    /DD/BETA/DD_Debug_Beta_v0.0.0-54.out
    • binary
    /DD/BETA/DD_Debug_Beta_v0.0.0-55.out
    • binary
    /DD/BETA/DD_Release_Beta_v0.0.0-54.out
    • binary
    /DD/BETA/DD_Release_Beta_v0.0.0-55.out
2 hrs ago

Dara Navaei

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

Options
    • -1
    • +1
    /firmware/App/DDCommon.h
2 hrs ago

Dara Navaei

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

Options
    • -1
    • +1
    /firmware/App/Drivers/ConductivityTeensy.c
    • -1
    • +1
    /firmware/App/Drivers/ConductivityTeensy.h
    • -1
    • +1
    /firmware/App/Monitors/Conductivity.c
    • -1
    • +1
    /firmware/App/Monitors/Conductivity.h
    • -2
    • +2
    /firmware/App/Monitors/Temperature.c
2 hrs ago

Michael Garthwaite

Merge branch 'LDT-3372-v1-conductivity-fixes' into staging

Options
Sunday 08 Mar
2:23 pm

Dara Navaei

LDT-3259 work in progress added a new broadcast channel from FFU

Options
    • -2
    • +4
    /firmware/App/Common.h
    • -6
    • +4
    /firmware/App/Modes/ModeStandby.c
    • -0
    • +2
    /firmware/App/Modes/ModeUpdate.c
    • -7
    • +9
    /firmware/App/Services/CommBuffers.c
    • -2
    • +62
    /firmware/App/Services/Download.c
    • -0
    • +2
    /firmware/App/Services/Download.h
    • -21
    • +24
    /firmware/App/Services/SystemComm.c
    • -3
    • +3
    /firmware/BL.dil
    • -2
    • +2
    /firmware/source/can.c
2:22 pm

Dara Navaei

Saturday 07 Mar
3:22 pm

Dara Navaei

3:09 pm

Dara Navaei

LEAHI-DD-FIRMWARE-LDT-3605_(DD) BLD sensor intermittently does not read for B2.0 HW
LEAHI-DD-FIRMWARE-LDT-3605_(DD) BLD sensor intermittently does not read for B2.0 HW
3:06 pm

Dara Navaei

LDT-3605 updated the blood leak driver for the hardware config restart

Options
    • -13
    • +1
    /firmware/App/Monitors/BloodLeak.c
3:03 pm

Dara Navaei

LDT-3605 updated the test support to initialize the blood leak driver if a new hardware config is selected

Options
    • -0
    • +5
    /TestSupport.c
2:40 pm

Dara Navaei

LEAHI-DD-FIRMWARE-LDT-2004_Dialysate Composition - DD
LEAHI-DD-FIRMWARE-LDT-2004_Dialysate Composition - DD
Friday 06 Mar
7:00 pm

Vendor - TEL - Sameer Poyil and Sean Nash

3:54 pm

Dara Navaei

Bamboo Commit: Updated Branch staging For Project TD

Options
    • -4
    • +4
    /TD/BETA/TD_BETA_Manifest.csv
    • binary
    /TD/BETA/TD_Debug_Beta_v0.0.0-29.out
    • binary
    /TD/BETA/TD_Debug_Beta_v0.0.0-30.out
    • binary
    /TD/BETA/TD_Release_Beta_v0.0.0-29.out
    • binary
    /TD/BETA/TD_Release_Beta_v0.0.0-30.out
3:26 pm

Dara Navaei

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

Options
    • -1
    • +1
    /firmware/App/TDCommon.h
3:26 pm

Dara Navaei

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

Options
    • -2
    • +2
    /firmware/App/Services/SystemCommTD.c
    • -2
    • +2
    /firmware/App/TDCommon.h
    • -2
    • +2
    /firmware/App/Tasks/TaskBG.c
3:26 pm

Dara Navaei

3:24 pm

Dara Navaei

Merged LDT-3599

Options
2:53 pm

Nicholas Ramirez

removed and model now lives in c++

removed and model now lives in c++

2:52 pm

Nicholas Ramirez

model moved to c++

model moved to c++

2:52 pm

Nicholas Ramirez

updated and moved

updated and moved

2:50 pm

Nicholas Ramirez

LDT-3398 HDF - SW - 01 - Main-Tx HDF Tab - R&I - 05: DEV - Feature Implementation

address cr comments

Options
    • -0
    • +2
    /leahi.pro
    • -0
    • +1
    /sources/gui/GuiGlobals.cpp
    • -11
    • +3
    /sources/gui/qml/components/HeaderBar.qml
    • -0
    • +3
    /sources/gui/qml/main.qml
    • -1
    • +1
    /sources/gui/qml/pages/treatment/TreatmentHDF.qml
    • -1
    • +1
    /sources/gui/qml/pages/treatment/TreatmentHeparin.qml
    • -19
    • +19
    /sources/gui/qml/pages/treatment/sections/TreatmentHDFComponent.qml
    • -0
    • +31
    /sources/view/VListModel.cpp
    • -0
    • +59
    /sources/view/VListModel.h
    • -0
    • +1
    /sources/view/VView.h
2:48 pm

Sean Nash

See my comment above. We should return BOOL so Dialin request can be ACK/NAK'd.

See my comment above. We should return BOOL so Dialin request can be ACK/NAK'd.

2:46 pm

Sean Nash

No faults from Dialin commands - we never want Dialin to cause system to go to fault because it requested something invalid - we only NAK the invalid request. We should do whatever is needed (if an...

No faults from Dialin commands - we never want Dialin to cause system to go to fault because it requested something invalid - we only NAK the invalid request.
We should do whatever is needed (if anything) to start the mode normally in an else.
And we should return TRUE/FALSE in these signal functions so that when it's called from Dialin msg handler, the msg handler can return ACK/NAK to Dialin if sub mode is invalid.

2:42 pm

Sean Nash

We shouldn't request op mode until we're sure we're happy with the whole thing. Need to determine whether we are already in the op mode being requested. If so, no need to request it again - just re...

We shouldn't request op mode until we're sure we're happy with the whole thing.
Need to determine whether we are already in the op mode being requested. If so, no need to request it again - just request new sub mode if not already in it. If not, the currentSubMode checked below is not relevant (applies to current mode, not the requested mode) and we need to request new op mode and signal that new op mode that we will want to start in a specific sub mode.

2:38 pm

Sean Nash

Declarations should be at top of scope (right before memcpy).

Declarations should be at top of scope (right before memcpy).