Posts by Kalyansiva

    Hi Marcel,


    Below is the log when i try to use 1.4.19b. My DCM server receives it but I cannot open it from there.


    [JEEVAN] C-Move Destination: "DCM4CHEE "
    [JEEVAN] Number of images to send: 2
    [JEEVAN] Accepted compression: ui
    [JEEVAN] Sending file : C:\Users\Pc\Downloads\dicomserver1419b\distribution\Data\0009703828\1.3.46.670589.5.2.10.2156913941.892665339.860724_0001_002000_14579035620000.dcm
    [JEEVAN] Accepted compression: ui
    [JEEVAN] Sending file : C:\Users\Pc\Downloads\dicomserver1419b\distribution\Data\0009703828\1.3.46.670589.5.2.10.2156913941.892665339.860724_0001_003000_14579035620001.dcm
    [JEEVAN] C-Move (PatientRoot)
    [JEEVAN] UPACS THREAD 39: ENDED AT: Fri Oct 20 11:25:36 2017
    [JEEVAN] UPACS THREAD 39: TOTAL RUNNING TIME: 3 SECONDS


    Where JEEVAN is my Conquest Local AE Title.

    Hi Marcel,


    Has Bug #15 been corrected in the latest release of 1.4.19b ?


    Hi Marcel,r "


    We are using conquest 1.4.19 as a router that receives DICOM and sends it to our DCM4CHE server in the cloud.


    We are able to send images in a compressed format (j2..jk etc) but at DCM4CHE we are unable to view the images. The viewer throws us an error "no image reader available for transfer syntax 1.2.840.10008.1.2". Could you help us correct this issue? Is it an issue with the transfer syntax that conquest is using here and can it be corrected? It works well for uncompressed images (using "ul" etc.). I'm helping a rural centre and they need faster transmission of images.


    Thanks a lot!


    K

    Hi Marcel,


    Another small doubt, I have been using export converters to automatically send images to a target server. I have seen that sometimes the receiving of images in Conquest is really slow, and when I remove the export converters line from the dicom.ini file, it is much faster.


    Is there any way I can delay the export converters from sending the images by a particular amount in time (say 30s)? or can i delay it till all images in a study have been received?


    Thanks,
    Kalyan

    Hi Marcel,


    Wanted your help and insight on the problem that I am facing:


    I am using conquest with j2 compression to send compressed images to a dcm4che server. The files are being received but I am not able to view them. On looking at the logs, we are getting the following error:
    no image reader available for transfer syntax 1.2.840.10008.1.2


    Do you know why this is happening and how I could solve this issue?


    Regards,
    Kalyan

    Hi Marcel,


    Currently I am pushing JPEG Lossless compressed images using "ul", not j2. It's definitely better than what I had so going with it for now; parallelly understanding how to configure dcm to allow receiving of images. Your idea of receiving on conquest and autoforwarding is great and that's what I'm trying to work on now.

    Hi Marcel,


    I went through the manual, specifically Appendix 2 - DICOM Gateway or Virtual server.


    Suppose I would like to forward all incoming scans to Ae Title: AETITLE1 and Ip Address: aa.bb.cc.dd on port number xxxxx, what would be the forward statement, could you help me? And dicom.ini is the file in the root folder right? As i see many dicom.ini's.

    Hi All,


    I am using conquest as a DICOM router to send cases remotely to another server and its working well. I'd like to know if I could set rules on the GUI that will allow me to automatically send all studies received by conquest to my remote server without any manual intervention. Would appreciate any help in this regard!


    Regards,
    Kalyan

    Hi Marcel,


    Another doubt: does it matter how we store on disc? So if we store "uncompressed" and send using ul, is it different from store as "jpeg lossless" and send using "ul"? Does it send as stored ? Am asking as Orthanc doesn't send as stored, if I remember correctly.

    Hi Marcel,


    Log line is below when sending is j2 enabled:


    [CONQUESTSRV1] Accepted compression: ui
    [CONQUESTSRV1] Sending file : c:\users\sony\desktop\conquest dicom\data\7rAgWJ\1.3.12.2.1107.5.2.5.11090.5.0.582367483902153_0003_000012_14969924900006.dcm


    I could not find anything about accepted compression: ui in the manual.


    (Strip=1) comes when I am using "ul" compression. Below is the log for that:


    [CONQUESTSRV1] Sending file : c:\users\sony\desktop\conquest dicom\data\7rAgWJ\1.3.12.2.1107.5.2.5.11090.5.0.582367483902153_0003_000012_14969924900006.dcm
    [CONQUESTSRV1] [recompress]: recompressed with mode = ul (strip=1)

    Sure Marcel,


    I'm using the GUI of Conquest.


    Under Tab "Known DICOM Providers"
    <AETITLE of my Test Server> <Ip address of my test server> <Port No. 11112> <Compression: j2>


    If I put ul instead of j2, i am able to get it to my server and view it but it is much slower.

    Hi Marcel,


    I realised another thing during the testing; when i give the type of compression as "ul" or "ub", then i am able to view the images in the backend. Only when i give j2...6 etc I am unable to view. It is better to use the j compressions as I can see a significant increase in speed.


    I also tried 17d and I found the same problem. Unable to view the images in the backend when I use j2.

    Hi Marcel,


    Thank you for the fast response! I am using Conquest DICOM Server 1.4.19.


    Attached is the DICOM that I have sent. It has been received by DCM server but i'm not able to view the image using a viewer (weasis and oviyam) in this case.

    Hi Everyone,


    I work in India on a project where we are trying to do teleradiology with remote rural hospitals. The issue is that their net is slow. We are trying to use Conquest to compress the images at the hospital end and send it to our DCM4CHEE server. I have enabled j2 compression on Conquest and the images are getting received by our server but we cannot view the images (Weasis and Oviyam viewers). Could someone help me with what the issue could be ?


    Merçi!
    Kalyan