Posts by rickjames99

  • Default dicom.ini 1.4.19b

    Hi


    I've noticed that in 1.4.19b, the default DICOM.ini file contains a lot less options than previous versions. Particularly the # Configure database section. Is there any reason for this?

    We use Conquest in a number of clinics and to keep consistent, is there any issue using a previous version's dicom.ini with our particular settings?


    Thanks

  • Delay forwarding of REG object

    Thanks for the quick response. Here's the log - I am sending a test data set of 7 objects - 5 CT slices and two REG objects. My DICOM device only receives 5 which is in line with the below. It looks like it is certainly recognising the REG objects but I can't figure out why it is failing just yet.


    [DCMRELAY] Written file: C:\dcmrelay\data\27022017\1.3.46.423632.141000201739162144164.1_0001_000000_14970207460000.dcm
    [DCMRELAY] ExportConverter1.0: forward C:\dcmrelay\data\27022017\1.3.46.423632.141000201739162144164.1_0001_000000_14970207460000.dcm to IMPAC_DCM_SCP
    [DCMRELAY] Written file: C:\dcmrelay\data\27022017\1.3.46.423632.141000201739162144164.1_0001_000005_14970207470001.dcm
    [DCMRELAY] Written file: C:\dcmrelay\data\27022017\1.3.46.423632.141000201739162144164.1_0001_000004_14970207480002.dcm
    [DCMRELAY] Written file: C:\dcmrelay\data\27022017\1.3.46.423632.141000201739162144164.1_0001_000003_14970207490003.dcm
    [DCMRELAY] Written file: C:\dcmrelay\data\27022017\1.3.46.423632.141000201739162144164.1_0001_000002_14970207500004.dcm
    [DCMRELAY] Written file: C:\dcmrelay\data\27022017\1.3.46.423632.141000201739162153107.265_0001_000001_14970207510005.dcm
    [DCMRELAY] ***Exportconverter0: Spawning 'forward modality REG after 10000 to IMPAC_DCM_SCP' failed (argv=C:\dcmrelay\data\27022017\1.3.46.423632.141000201739162153107.265_0001_000001_14970207510005.dcm)
    [DCMRELAY] ExportConverter1.0: forward C:\dcmrelay\data\27022017\1.3.46.423632.141000201739162144164.1_0001_000005_14970207470001.dcm to IMPAC_DCM_SCP
    [DCMRELAY] ExportConverter1.0: forward C:\dcmrelay\data\27022017\1.3.46.423632.141000201739162144164.1_0001_000004_14970207480002.dcm to IMPAC_DCM_SCP
    [DCMRELAY] ExportConverter1.0: forward C:\dcmrelay\data\27022017\1.3.46.423632.141000201739162144164.1_0001_000003_14970207490003.dcm to IMPAC_DCM_SCP
    [DCMRELAY] ExportConverter1.0: forward C:\dcmrelay\data\27022017\1.3.46.423632.141000201739162144164.1_0001_000002_14970207500004.dcm to IMPAC_DCM_SCP
    [DCMRELAY] Written file: C:\dcmrelay\data\27022017\1.3.46.423632.141000201739162153117.266_0001_000001_14970207520006.dcm
    [DCMRELAY] ***Exportconverter0: Spawning 'forward modality REG after 10000 to IMPAC_DCM_SCP' failed (argv=C:\dcmrelay\data\27022017\1.3.46.423632.141000201739162153117.266_0001_000001_14970207520006.dcm)
    [DCMRELAY] UPACS THREAD 2: ENDED AT: Fri Jun 09 16:05:54 2017
    [DCMRELAY] UPACS THREAD 2: TOTAL RUNNING TIME: 9 SECONDS

  • Delay forwarding of REG object

    Hello


    I am using Conquest to auto forward DICOM data. I would like to introduce a delay for forwarding certain objects in a study. When receiving CT and REG objects, I am looking to delay the forwarding of the REG objects to give the CT objects a chance to move over a WAN before the REG object is required in the workflow. Is this something Conquest can handle? below looks like what should be getting me close but not yet getting the results I am after.


    ForwardAssociationLevel = *
    ForwardAssociationCloseDelay = 5
    ForwardAssociationRefreshDelay = 3600
    ExportConverters = 2
    ExportModality0 = REG
    ExportConverter0 = forward modality REG after 10000 to AE_SCP
    ExportModality1 = CT
    ExportConverter1 = forward to AE_SCP


    Any input appreciated! Thanks