| Dicom send not working |
Sep 20, 2022 12:00 AM
by VetMed
by VetMed
I have connected Radiant with my dicom workstation/PACS (c-move). Sending from PACS to Radiant works, Retrieving with Radiant from PACS works, but I cannot see the cases stored in Radiant with my PACS and Radiant cannot send to my PACS.
I get the nice error message that you already show in your manual (under dicom send). What can I do to make it work?
Thank you!
PS: just changed my permanent license to a subscripition :-). I really like Radiant!
I get the nice error message that you already show in your manual (under dicom send). What can I do to make it work?
Thank you!
PS: just changed my permanent license to a subscripition :-). I really like Radiant!
Sep 28, 2022 12:21 AM
by VetMed
by VetMed
Update - I might have found the problem, and it looks like a bug to me. Radiant is installed on the same PC (obviously with different port and AET) as my PACS. Since I can send from Radiant everywhere else in my dicom network without any issues (as long as its not on the same PC), this seems to be the reason.
Any way to overcome this issue?
Thanks!
Any way to overcome this issue?
Thanks!
Sep 28, 2022 03:07 PM
by
by
RadiAnt uses DCMTK to send images to PACS. What is the error that you get while trying to upload studies to your local PACS? How is your local PACS defined in the PACS configuration window in RadiAnt?
Sep 28, 2022 03:30 PM
by VetMed
by VetMed
Can you send me a link where I can upload screenshots? Then I can provide you with the detailed information.
But the basic dicom connection works (I can receive with Radiant from my PACS, both when searching it from Radiant and when sending from PACS), the echo test connection works in both directions, the AET, Port numbers and IP parameters are correct in both directions (checked 5 times). Deactivating Firewall does not change the problem. Transfer protocol is C-Move.
Thanks!
But the basic dicom connection works (I can receive with Radiant from my PACS, both when searching it from Radiant and when sending from PACS), the echo test connection works in both directions, the AET, Port numbers and IP parameters are correct in both directions (checked 5 times). Deactivating Firewall does not change the problem. Transfer protocol is C-Move.
Thanks!
Jan 3, 2023 01:20 PM
by
by
Please contact us via https://www.radiantviewer.com/contact/ and you'll be able to send the screenshots to the email we'll reply from.
Jan 11, 2023 01:31 AM
by VetMed
by VetMed
First thanks for coming back to me. I was able to find out the problem. I had an AE-Title on my PACS which contained a space (eg: PACS 1). When I removed the space (PACS1) (and adapted the AETs accordingly in the dicom send parameters) it worked. I figured that out because I could send without any problems to another PACS on my PC, just with a different AET without spaces in it. So it seems to be a little bug. I will send you the screenshot for the error message via the link you provided me (but it is rather unspecific).
Best,
Vetmed
Best,
Vetmed
Jun 21, 2023 08:00 PM
by
by
Thank you Vetmed for reporting the issue. We have fixed it in version 2023.1
Jun 29, 2023 02:00 PM
by Vetmed
by Vetmed
Thank you - you are the best!
Now we only need curved MPR, Hanging Protocols, Series subtraction and of course the possibility to save newly generated series as dicom, and you will be PERFECT!!!! :-)
Now we only need curved MPR, Hanging Protocols, Series subtraction and of course the possibility to save newly generated series as dicom, and you will be PERFECT!!!! :-)
Feb 13, 2024 08:40 AM
by Teodora
by Teodora
WHy I am not able to open the stored echo videos on Radiant? I see them as echo image, not a vdieo. I usually transfer them on a stick, and them open them on my PC.
Mar 17, 2024 08:13 PM
by
by
They're probably coming from GE scanner. They use proprietary format for storing cine loops.