DICOM @ OFFIS

Hi, it looks like something in the arriving command set of the C-STORE-RQ is wrong; in particular the DCMTK parser complains that this tag: (0000,0100) US [1] CommandField is missing, though at least in the DCM4CHEE log it is still present. Maybe you can record the DICOM communication using wireshar...

Hi,

at least I can say that there is no DCMTK-based solution. This is probably not well-suited for this forum.

Best regards,
Michael

Hi,

either CARDIAC1 is not configured in the PACS to your IP address/port, or the selected study does not have any images. Use --debug option and post check/post the details of the C-MOVE response.

Best regards,
Michael

P.S: And remove all but the following attributes from the C-GET request: D: (0008,0052) CS [STUDY] # 6, 1 QueryRetrieveLevel D: (0020,000d) UI [1.2.840.113663.1500.1.313721677.1.1.20140708.145420.781] # 56, 1 StudyInstanceUID I removed: D: (0008,0050) SH (no value available) # 0, 0 AccessionNumber D...

You must also propose various Storage SOP Classes to the server which the server can use on the connection to send you the images. Look into getscu.cc how it's done there.

BR Michael

Great! And greetings back to Löningen/Berlin

BR,
Michael

Correct, you will receive the images on the same connection that is used to deliver the C-GET.

BR,
Michael

Hi,

please paste the full log of the dcmsend call. Add option --debug to show all relevant info.

BR,
Michael

Ebaad wrote: ↑Tue, 2023-07-25, 14:42 After 17 years, I am back to the same question, but was able to resolve it.

It took a little while but what the heck Glad that it works for you now and that you remember this old post

BR Michael

This requires more explanation. Read through the PACS tutorial to understand how C-MOVE works in general.

BR Michael

dcmsend -aec TEPE 10.17.128.10 2010 ex.dcm

This should also be obvious from looking into the dcmsend manual page that you easily find via google.

Or it's a memory issue when handling over objects/memory areas from jni to ofstd and/or back.

If this is on Windows, I sometimes experienced that the cmd.exe window was the reason and hitting Enter in it helped. I think this only happens if the window is or was focused. I don't know what the underlying reason is, though. Also try option -dhl (on any OS) which avoids that DNS lookup runs into...

Hi Horst, regarding your questions: In the case of the default settings, I could see that the request to the DICOM server remains pending and does not terminate. I could also determine this with echoscu. as stated by echoscu help page, the default is "unlimited", which seems to be in line ...

Hi, That's a classic ;) Some attributes are within the Scheduled Procedure Step Sequence (0040,1000), and your request must reflect that. Try: ./findscu.exe www.dicomserver.co.uk 104 -k 0010,0010=Bowen^William -k 0010,0040 -k 0040,0100[0].0008,0060 -k 0040,0100[0].0040,4005 Besides that, you probabl...