Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Single instance receiving DICOM #137

Open
xnogard opened this issue Jan 30, 2025 · 3 comments
Open

Single instance receiving DICOM #137

xnogard opened this issue Jan 30, 2025 · 3 comments

Comments

@xnogard
Copy link

xnogard commented Jan 30, 2025

Just purchased from the App Store on my macbook M3. Im trying to send some DICOMs from my DICOM server but it seems I can send one study at a time. All other studies will timeout while the initial one is still sending. On OsiriX and Horos, I was able to send upto 6 studies at time. Just want to see if I missed a config or is it hardcoded to have one connection instance.

@bettar
Copy link
Owner

bettar commented Feb 3, 2025

  1. How are you sending the studies ? From a command on Terminal ? From another app with a GUI ? From the same PC ? From the same LAN ?
  2. Did you check the Network Logs (available from the Network menu) ?
  3. What error messages do you get if you launch the app from Terminal ?
  4. Any pop up error messages ?
  5. When you send the second study, is the first one being interrupted, or is the second one not even started ?
  6. Are you able to check with Wireshark what is going on at the network protocol level ?
  7. Which macOS version are you running ?

@xnogard
Copy link
Author

xnogard commented Feb 4, 2025

  1. I was sending from a DICOM app such as Orthanc and MicroDicom over the network to the Macbook with miele-lxiv. First instance of DICOM would cross, as I send the next study it will just sit pending and then times out/fail on Orthanc/MicroDICOM. There were no popup errors on the Macbook end.
  2. The network logs only show successful connection/received studies, while the timed out ones are not shown.
  3. Launching from Terminal and sending exams does not show up, nor any failure show up in the terminal. Other actions such as deleting studies, shows on the Terminal.
  4. No popup for any failures
  5. Correct, the second study did not start at all.
  6. I ran Wireshark, it only shows the initial connection that is sending. Nothing shows up regarding the second server send.
  7. This was done on a new Macbook Air M3 with Sonoma

In addition, I sent a large study from one of my server, then on my second server I sent another study. The second study from the second server would time out (DUL network read timeout)

Thanks for the response!

@bettar
Copy link
Owner

bettar commented Feb 4, 2025

I am not clear on what you meant in your original post "I can send one study at a time":

  1. Does it mean that to send the second study you have to wait for the first one to be finished
  2. or does it mean that to send the second study you need to restart the app ?

If Wireshark doesn't show anything when you send the second one it means the sending entity is not even initiating the comms, so I would first fix that problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants