Posts by yjdcom

  • Ask about worklist AET

    hi

    I would like to inquire about the worklist.

    Can it define the data returned by each device based on the AET and Modality requested by the device?

    For example, I have three CT equipments. The AETs are CT1, CT2, and CT3. The three equipments obtain different examination information according to different AETs.

    How should I configure this. Can you give me an example? And whether this worklist can add a configuration window to the main program.

  • About dicom-routing request help

    hi

    I consulted the CT equipment manufacturer, and his reply is that the current equipment is sent like this, and there is no way to adjust it. I want to ask if there is any way to speed up the conquest acceptance, such as multi-threaded reception.

    There is no problem with conquest being used as a DX router, and now it's just a CT

  • About dicom-routing request help

    Another pacs server I use now can reach 183 CTs in 12 seconds. It takes 52 seconds for me to use conquest to complete. I have contacted the CT equipment manufacturer and asked them to check whether it is serialized and sent.

  • About dicom-routing request help

    Hello, I have tested and the log between two conquests is like this.

    ===============================

    TEST]

    [TEST] UPACS THREAD 29: STARTED AT: Tue Mar 22 21:42:25 2022

    [TEST] Calling Application Title : "MYPCAS "

    [TEST] Called Application Title : "TEST "

    [TEST] Application Context : "1.2.840.10008.3.1.1.1", PDU length: 32768

    [TEST] Presentation Context 0 "1.2.840.10008.5.1.4.1.1.2" 1

    [TEST] Presentation Context 1 "1.2.840.10008.5.1.4.1.1.7" 1

    [TEST] Written file: C:\Users\Administrator\Desktop\dicomserver150b\Data\2203220289\1.2.840.1.99.1.47.2.1647917401892_0101_000001_16479565460000.dcm

    [TEST] Written file: C:\Users\Administrator\Desktop\dicomserver150b\Data\2203220289\1.2.840.1.99.1.47.2.1647917401892_0101_000002_16479565460001.dcm

    [TEST] Written file: C:\Users\Administrator\Desktop\dicomserver150b\Data\2203220289\1.2.840.1.99.1.47.2.1647917401894_0201_000001_16479565460002.dcm

    [TEST] Written file: C:\Users\Administrator\Desktop\dicomserver150b\Data\2203220289\1.2.840.1.99.1.47.2.1647917401894_0201_000002_16479565460003.dcm

    [TEST] Written file: C:\Users\Administrator\Desktop\dicomserver150b\Data\2203220289\1.2.840.1.99.1.47.2.1647917401894_0201_000003_16479565460004.dcm

    [TEST] Written file: C:\Users\Administrator\Desktop\dicomserver150b\Data\2203220289\1.2.840.1.99.1.47.2.1647917401894_0201_000004_16479565460005.dcm

    [TEST] Written file: C:\Users\Administrator\Desktop\dicomserver150b\Data\2203220289\1.2.840.1.99.1.47.2.1647917401894_0201_000005_16479565460006.dcm

    [TEST] Written file: C:\Users\Administrator\Desktop\dicomserver150b\Data\2203220289\1.2.840.1.99.1.47.2.1647917401894_0201_000006_16479565460007.dcm

    [TEST] Written file: C:\Users\Administrator\Desktop\dicomserver150b\Data\2203220289\1.2.840.1.99.1.47.2.1647917401894_0201_000007_16479565460008.dcm

    [TEST] Written file: C:\Users\Administrator\Desktop\dicomserver150b\Data\2203220289\1.2.840.1.99.1.47.2.1647917401894_0201_000008_16479565460009.dcm

    [TEST] Written file: C:\Users\Administrator\Desktop\dicomserver150b\Data\2203220289\1.2.840.1.99.1.47.2.1647917401894_0201_000009_1647956546000a.dcm

    [TEST] Written file: C:\Users\Administrator\Desktop\dicomserver150b\Data\2203220289\1.2.840.1.99.1.47.2.1647917401894_0201_000010_1647956546000b.dcm

    [TEST] Written file: C:\Users\Administrator\Desktop\dicomserver150b\Data\2203220289\1.2.840.1.99.1.47.2.1647917401894_0201_000011_1647956546000c.dcm

    [TEST] Written file: C:\Users\Administrator\Desktop\dicomserver150b\Data\2203220289\1.2.840.1.99.1.47.2.1647917401894_0201_000012_1647956546000d.dcm

    [TEST] Written file: C:\Users\Administrator\Desktop\dicomserver150b\Data\2203220289\1.2.840.1.99.1.47.2.1647917401894_0201_000013_1647956546000e.dcm

    [TEST] Written file: C:\Users\Administrator\Desktop\dicomserver150b\Data\2203220289\1.2.840.1.99.1.47.2.1647917401894_0201_000014_1647956546000f.dcm

    [TEST] Written file: C:\Users\Administrator\Desktop\dicomserver150b\Data\2203220289\1.2.840.1.99.1.47.2.1647917401894_0201_000015_16479565460010.dcm

    [TEST] Written file: C:\Users\Administrator\Desktop\dicomserver150b\Data\2203220289\1.2.840.1.99.1.47.2.1647917401894_0201_000016_16479565460011.dcm

    [TEST] Written file: C:\Users\Administrator\Desktop\dicomserver150b\Data\2203220289\1.2.840.1.99.1.47.2.1647917401894_0201_000017_16479565460012.dcm

    [TEST] Written file: C:\Users\Administrator\Desktop\dicomserver150b\Data\2203220289\1.2.840.1.99.1.47.2.1647917401894_0201_000018_16479565460013.dcm

    [TEST] Written file: C:\Users\Administrator\Desktop\dicomserver150b\Data\2203220289\1.2.840.1.99.1.47.2.1647917401894_0201_000019_16479565460014.dcm

    [TEST] Written file: C:\Users\Administrator\Desktop\dicomserver150b\Data\2203220289\1.2.840.1.99.1.47.2.1647917401894_0201_000020_16479565460015.dcm

    [TEST] Written file: C:\Users\Administrator\Desktop\dicomserver150b\Data\2203220289\1.2.840.1.99.1.47.2.1647917401894_0201_000021_16479565460016.dcm

    [TEST] Written file: C:\Users\Administrator\Desktop\dicomserver150b\Data\2203220289\1.2.840.1.99.1.47.2.1647917401894_0201_000022_16479565460017.dcm

    [TEST] Written file: C:\Users\Administrator\Desktop\dicomserver150b\Data\2203220289\1.2.840.1.99.1.47.2.1647917401894_0201_000023_16479565460018.dcm

    [TEST] Written file: C:\Users\Administrator\Desktop\dicomserver150b\Data\2203220289\1.2.840.1.99.1.47.2.1647917401894_0201_000024_16479565460019.dcm

    [TEST] Written file: C:\Users\Administrator\Desktop\dicomserver150b\Data\2203220289\1.2.840.1.99.1.47.2.1647917401894_0201_000025_1647956546001a.dcm

    [TEST] Written file: C:\Users\Administrator\Desktop\dicomserver150b\Data\2203220289\1.2.840.1.99.1.47.2.1647917401894_0201_000026_1647956546001b.dcm


    .............................

    The CT device and conquests transfer log is like this


    -----------------------------------------------------


    [PACS] UPACS THREAD 1256: STARTED AT: Mon Mar 21 17:39:21 2022

    [PACS] Calling Application Title : "SVCT "

    [PACS] Called Application Title : "PACS "

    [PACS] Application Context : "1.2.840.10008.3.1.1.1", PDU length: 16384

    [PACS] Presentation Context 0 "1.2.840.10008.5.1.4.1.1.2" 1

    [PACS] Presentation Context 1 "1.2.840.10008.5.1.4.1.1.7" 1

    [PACS] ImportConverter1.1: forwarded object to CTAE

    [PACS] ImportConverter2.1: forwarded object to mview

    [PACS] Written file: d:\dicom-router\data\2203210271\1.2.840.1.99.1.47.2.1647834099746_0202_000021_16478555620353.dcm

    [PACS] UPACS THREAD 1256: ENDED AT: Mon Mar 21 17:39:22 2022

    [PACS] UPACS THREAD 1256: TOTAL RUNNING TIME: 1 SECONDS

    [PACS]

    [PACS] UPACS THREAD 1257: STARTED AT: Mon Mar 21 17:39:22 2022

    [PACS] Calling Application Title : "SVCT "

    [PACS] Called Application Title : "PACS "

    [PACS] Application Context : "1.2.840.10008.3.1.1.1", PDU length: 16384

    [PACS] Presentation Context 0 "1.2.840.10008.5.1.4.1.1.2" 1

    [PACS] Presentation Context 1 "1.2.840.10008.5.1.4.1.1.7" 1

    [PACS] ImportConverter1.1: forwarded object to CTAE

    [PACS] ImportConverter2.1: forwarded object to mview

    [PACS] Written file: d:\dicom-router\data\2203210271\1.2.840.1.99.1.47.2.1647834099746_0202_000022_16478555630354.dcm

    [PACS] UPACS THREAD 1257: ENDED AT: Mon Mar 21 17:39:23 2022

    [PACS] UPACS THREAD 1257: TOTAL RUNNING TIME: 1 SECONDS

    [PACS]

    [PACS] UPACS THREAD 1258: STARTED AT: Mon Mar 21 17:39:23 2022

    [PACS] Calling Application Title : "SVCT "

    [PACS] Called Application Title : "PACS "

    [PACS] Application Context : "1.2.840.10008.3.1.1.1", PDU length: 16384

    [PACS] Presentation Context 0 "1.2.840.10008.5.1.4.1.1.2" 1

    [PACS] Presentation Context 1 "1.2.840.10008.5.1.4.1.1.7" 1

    [PACS] ImportConverter1.1: forwarded object to CTAE

    [PACS] ImportConverter2.1: forwarded object to mview

    [PACS] Written file: d:\dicom-router\data\2203210271\1.2.840.1.99.1.47.2.1647834099746_0202_000023_16478555630355.dcm

    [PACS] UPACS THREAD 1258: ENDED AT: Mon Mar 21 17:39:23 2022

    [PACS] UPACS THREAD 1258: TOTAL RUNNING TIME: 0 SECONDS

    [PACS]

  • About dicom-routing request help

    Thank you very much for your reply!


    I tested your configuration here, and the speed hasn't changed much now, and I haven't found a setting to close new links on the CT device.

    I did a Conquest storage test here, the total number of CT slices is 183

    1.Conquest is only stored to the local hard disk (SSD), the configuration is the default and no changes have been made, and the database has tested MYSQL and SQLITE. It took 53 seconds to store the CT183 CTs.


    2. Conquest performs routing forwarding, and there are three forwarding targets:

    CTAE, MVIEW, FRONTDOCKSCP, the configuration files used are:


    The first configuration:

    ExportConverters = 3

    ExportModality0 = CT

    ExportConverter0 = forward to mview;forward to FRONTDOCKSCP;forward to CTAE

    ExportModality1 = DX

    ExportConverter1 = forward to mview;forward to FRONTDOCKSCP;forward to DRAE


    Second configuration:


    ExportConverters = 3

    ExportModality0 = CT

    ExportConverter0 = forward series after 60 to mview;forward series after 60 to FRONTDOCKSCP;forward series after 60 to CTAE

    ExportModality1 = DX

    ExportConverter1 = forward series after 60 to mview;forward series after 60 to FRONTDOCKSCP;forward series after 60 to DRAE


    For these two configurations, it took 55 seconds to store 183 CTs.


    After these two tests, I came to the conclusion that my Conquest is too slow to accept CTs, I still have a pacs here, it accepts CTs faster, and it only takes 13 seconds to store 183 CTs.

    Is there any way for Conquest to transmit CT faster? If I have 100 patients for examination a day, each with 500 CT films, it will take 3 hours to transmit to Conquest, which is a waste of time.


    ---------------------------------------------------------

    The following is the test video address

    ---------------------------------------------------------

    first option


    The second option


    This is the transfer speed of 3rd party PCAS


    -------Please click the text above to watch----------

  • About dicom-routing request help

    Thanks for your reply, can you give me an example of dicom.ini


    this is my configuration

    ------------------------------------------------

    # This file contains configuration information for the DICOM server

    # Do not edit unless you know what you are doing


    [sscscp]

    MicroPACS = sscscp


    # Network configuration: server name and TCP/IP port#

    MyACRNema = PACS

    TCPPort = 5678


    # Host, database, username and password for database

    SQLHost = localhost

    SQLServer = C:\1\Data\dbase\conquest.db3

    Username =

    Password =

    SqLite = 1

    DoubleBackSlashToDB = 0

    UseEscapeStringConstants = 0


    # Configure server

    ImportExportDragAndDrop = 1

    ZipTime = 05:

    UIDPrefix = 1.2.826.0.1.3680043.2.135.738236.38031092

    EnableComputedFields = 1


    FileNameSyntax = 4


    # Configuration of compression for incoming images and archival

    DroppedFileCompression = un

    IncomingCompression = un

    ArchiveCompression = as


    # For debug information

    PACSName = PACS

    OperatorConsole = 127.0.0.1

    DebugLevel = 0


    # Configuration of disk(s) to store images

    MAGDeviceFullThreshHold = 30

    MAGDevices = 1

    MAGDevice0 = c:\1\data\


    # Configuration of forwarding and/or converter programs to export DICOM slices

    ForwardAssociationLevel = SERIES

    ForwardAssociationCloseDelay = 5

    ForwardAssociationRefreshDelay = 3600

    ForwardAssociationRelease = 1


    ExportConverters = 2

    ExportModality0 = CT

    ExportConverter0 = forward to SERVER;forward to CTAE

    ExportModality1 = DX

    ExportConverter1 = forward to SERVER;forward to DRAE


    ForwardCollectDelay = 60

    MaximumExportRetries = 0

    MaximumDelayedFetchForwardRetries = 0



    ------------------------------------------------


    I read the manual, I don't know a few parameters very well, can you please explain?



    ExportStationName0 = CT_SCANNER

    ExportCalledAE0 = CONQUESTSRV1

    ExportCallingAE0 = CONQUESTSRV2

    ExportFilter0 = Rows = 512 and Columns = 512

    ----------------------------------------------------

  • About dicom-routing request help

    你好


    我是来自中国的conquest忠实用户，现在我用的版本是1.5.0b，


    我的使用环境，我介绍一下，


    我现在有两个检查设备，一个动作，一个 DX，


    存储设备室三个，一个设备存储CT和DX，一个设备存储CT，一个设备存储DX，一个设备用来充当路由


    当CT和DX向路由发送数据，根据设备类型自动分配。


    我用conquest这个是用来做路由的，但是现在我遇到了一个问题，就是当我传输CT的时候非常慢，2分钟才传了200+图，我想咨询一下应该怎么设置呢。


    我附上我的设置，麻烦帮我看看哪里出了问题，谢谢你！




    Hi


    I am a loyal user of conquest from China, the version I use now is 1.5.0b,


    My usage environment, let me introduce,


    I now have two inspection devices, one motion, one DX,


    Three storage equipment rooms, one for CT and DX, one for CT, one for DX, and one for routing


    When CT and DX send data to the router, they are automatically assigned according to the device type.


    I use conquest for routing, but now I have encountered a problem, that is, when I transmit CT, it is very slow. It only took 2 minutes to transmit 200+ pictures. I want to ask how to set it up.


    I am attaching my settings, please help me to see what is wrong, thank you!


    here is the config file



    dicom.txt


    dgatesop.txt


    log.txt