Setting up dcm4che with Agfa CR-30X (native NX viewer software)

[cahi...@googlemail.com]

Hello,
   I am setting up dcm4chee as a PACs archive for images generated by our Agfa CR30-X machine and it's "NX viewer" software.

The NX software can be configured to send images to a number of PACs servers.  If anyone has experience of this, I would be grateful to hear from them. 

The first bit of configuration I could do with a pointer with is the "Type of PACs archive".  There are several options: generic, impax 4.5, 5.2, 6.0, SE, Musica or Standard V9000.  What category does dcm4chee fall under?

Thanks in advance.

[Suresh Viswanathan]

You should probably use Generic.

Suresh.

--
You received this message because you are subscribed to the Google Groups "dcm4che" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+u...@googlegroups.com.
To post to this group, send email to dcm...@googlegroups.com.
Visit this group at http://groups.google.com/group/dcm4che.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[cahi...@googlemail.com]

Suresh - thank you.  Any particular reason for this choice?

Cahir

[Suresh Viswanathan]

You're welcome. Impax is Agfa's own PACS and they probably use a proprietary communication. Not sure about SE, Musica or Standard V9000 but they are probably proprietary too. dcm4chee adheres to the DICOM standard as closely as possible and hence the suggestion to go with generic.

Suresh.

[cahi...@googlemail.com]

Thank you.  That is very helpful.  Will let you know if the setting works out.

[cahi...@googlemail.com]

OK - I have a query regarding getting the Afga NX digital radiography software to "talk" to dcm4chee.

My setup is as follows:  I have successfully added dcm4chee as a PACs server to the Afga NX software.   The Agfa machine can ping the PACs server.  But so far I cannot get the NX software to archive any images to the dcm4chee server.  The NX windows machine has two network cards in it.  One is on the 192.x.x.x range and is used so that the NX computer can communicate with the digital radiography unit.  The other is on a separate private IP range which the dcm4chee server is connceted to, and I installed this card so that the NX machine can talk to the dcm4chee server.

I have made the assumption from reading installation notes, that the NX machine MUST be added to the dcm4chee server as an "AET" before any images can be transferred from the NX node to dcm4chee, ie, two way communication must be possible.  Is this correct?  So I added the NX machine as an AET in the dcm4chee web interface.  However, I cannot ping from dcm4chee to NX (see attached screenshot).  I think this is because they are on different IP ranges.  Can anyone tell me if this is the cause of my woes?

Thanks.

Cahir.

[Sam Wittlin]

Hi... Did you ever figure this out for the NX archive?
Thanks!

[raasem]

hello , i know its a very old topic , but i would like to know if you found any solution for you issue , im interested to