Posts by auflauf

Is anybody aware of a CE-certified version of conquest, maybe certified by a third party?

Kind regards
Alexander

thanks!
With -fe, the communication goes one step further:

********************************************************
A-ASSOCIATE-RQ Packet Dump
Calling Application Title : "NX1 "
Called Application Title : "DV5800 "
Application Context : "1.2.840.10008.3.1.1.1"
Number of Proposed Presentation Contexts: 1
Presentation Context 0 "1.2.840.10008.5.1.1.9"
--------------- command for request (1) -----------------
(0000, 0000, 04, Type Unknown) [104|68]
(0000, 0002, 22, Type Unknown) "1.2.840.10008.5.1.1.1"
(0000, 0100, 02, Type Unknown) (320|140)
(0000, 0110, 02, Type Unknown) (2|2)
(0000, 0800, 02, Type Unknown) (0|0)
(0000, 1000, 36, Type Unknown) "1.3.51.0.0.2003.1.4.20090408093240.2"
--------------- data for NCREATE request (1) -----------------
(2000, 0000, 04, Type Unknown) [10|a]
(2000, 0010, 02, Type Unknown) (8241|2031)
A-ASSOCIATE-RQ Packet Dump

Calling Application Title : "NX1 "
Called Application Title : "DV5800 "
Application Context : "1.2.840.10008.3.1.1.1"
Number of Proposed Presentation Contexts: 1
Presentation Context 0 "1.2.840.10008.5.1.1.1"
Transfer Syntax: "1.2.840.10008.1.2"
AAssociateRJ: 1, 2, 1

but still the rest is missing..
The corresponding efilm example:

********************************************************
A-ASSOCIATE-RQ Packet Dump
Calling Application Title : "Efilm_kluge "
Called Application Title : "DV5800 "
Application Context : "1.2.840.10008.3.1.1.1"
Number of Proposed Presentation Contexts: 1
Presentation Context 0 "1.2.840.10008.5.1.1.9"
--------------- command for request (1) -----------------
(0000, 0000, 04, Type Unknown) [60|3c]
(0000, 0002, 22, Type Unknown) "1.2.840.10008.5.1.1.1"
(0000, 0100, 02, Type Unknown) (320|140)
(0000, 0110, 02, Type Unknown) (369|171)
(0000, 0800, 02, Type Unknown) (258|102)
--------------- data for NCREATE request (1) -----------------
(2000, 0000, 04, Type Unknown) [10|a]
(2000, 0010, 02, Type Unknown) (8241|2031)
Forwarding NCREATE-RQ 1
Waiting for NCREATE-RSP
--------------- response (command) (1) -----------------
(0000, 0000, 04, Type Unknown) [132|84]
(0000, 0002, 22, Type Unknown) "1.2.840.10008.5.1.1.1"
(0000, 0100, 02, Type Unknown) (33088|8140)
(0000, 0120, 02, Type Unknown) (369|171)
(0000, 0800, 02, Type Unknown) (257|101)
(0000, 0900, 02, Type Unknown) (0|0)
(0000, 1000, 54, Type Unknown) "1.2.840.113564.11.192.168.1.150.2009.3.30.17.0.15.3714"
Forwarding NCREATE-RSP
--------------- command for request (1) -----------------
(0000, 0000, 04, Type Unknown) [60|3c]
(0000, 0002, 22, Type Unknown) "1.2.840.10008.5.1.1.2"
(0000, 0100, 02, Type Unknown) (320|140)
(0000, 0110, 02, Type Unknown) (371|173)
(0000, 0800, 02, Type Unknown) (258|102)
--------------- data for NCREATE request (1) -----------------
(2010, 0000, 04, Type Unknown) [206|ce]
(2010, 0010, 12, Type Unknown) "STANDARD\4,5"
(2010, 0040, 08, Type Unknown) "PORTRAIT"
(2010, 0050, 10, Type Unknown) "14INX17IN "
(2010, 0150, 00, Type Unknown) (null)
(2010, 0500, 00, Type Unknown) (null)
Forwarding NCREATE-RQ 1
Waiting for NCREATE-RSP
--------------- response (command) (1) -----------------
(0000, 0000, 04, Type Unknown) [132|84]
(0000, 0002, 22, Type Unknown) "1.2.840.10008.5.1.1.2"
(0000, 0100, 02, Type Unknown) (33088|8140)
(0000, 0120, 02, Type Unknown) (371|173)
(0000, 0800, 02, Type Unknown) (258|102)
(0000, 0900, 02, Type Unknown) (0|0)
(0000, 1000, 54, Type Unknown) "1.2.840.113564.11.192.168.1.150.2009.3.30.17.0.15.3716"
Forwarding NCREATE-RSP
--------------- response (data) (1) -----------------
(2010, 0000, 04, Type Unknown) [2116|844]
(2010, 0500, 100, Type Unknown) fffffffe(■)ffffffff( )00( )ffffffe0(Ó)5c(\)00( )00( )00( )08)00( )50
(P)11(◄)16(▬)00( )00( )00( )
(2010, 0510, 2000, Type Unknown) fffffffe(■)ffffffff( )00( )ffffffe0(Ó)5c(\)00( )00( )00( )08)00( )5
0(P)11(◄)16(▬)00( )00( )00( )
Forwarding NCREATE-RSP data field
--------------- command for request (1) -----------------
(0000, 0000, 04, Type Unknown) [122|7a]
(0000, 0003, 22, Type Unknown) "1.2.840.10008.5.1.1.4"
(0000, 0100, 02, Type Unknown) (288|120)
(0000, 0110, 02, Type Unknown) (373|175)
(0000, 0800, 02, Type Unknown) (258|102)
(0000, 1001, 54, Type Unknown) "1.2.840.113564.11.192.168.1.150.2009.3.30.17.0.15.3717"
--------------- data for NSET request (1) -----------------
(2020, 0000, 04, Type Unknown) [383238|5d906]
(2020, 0010, 02, Type Unknown) (1|1)
(2020, 0020, 06, Type Unknown) "NORMAL"
(2020, 0110, 00, Type Unknown) (null)
Forwarding NSET-RQ 1
Waiting for NSET-RSP
--------------- response (command) (1) --------

...

I just installed the mingw c++-compiler and tried to compile the changed source file, but a lot of error messages indicates that I would have to have a lot to learn in case I had to compile the file.
I'll better talk to the agfa service rep. tomorrow, maybe they have a simpler generic camera model to choose.

Thanks!
Alexander

This might be too specific, but maybe someone of you has a clue or could point me to another forum more appropriate?

A good starting point for me would be a short explanation of what presumably is missing in the agfa-router communication.

Our setup:
A kodak DV 5800 lasercamera is connected to a 10Mbit network.
Printjobs are sent
-directly to the camera IP from an old ct
-to a dicom print router (from the conquest files, thanks marcel van henk!) who then forwards to the camera
-via the dicom router from a Agfa CR CX85 processing workstation

All but the last work. As far as we can guess, ae-title, IP and port of the print router are filled in correctly in the agfa application and efilm. Pinging the router works from everywhere. Here are some snippets of the dicom router log:

A. These are the log files if agfa sends a print job:
********************************************************
A-ASSOCIATE-RQ Packet Dump
Calling Application Title : "NX1 "
Called Application Title : "DV5800 "
Application Context : "1.2.840.10008.3.1.1.1"
Number of Proposed Presentation Contexts: 1
Presentation Context 0 "1.2.840.10008.1.1"
--------------- command for request (1) -----------------
(0000, 0000, 04, Type Unknown) [56|38]
(0000, 0002, 18, Type Unknown) "1.2.840.10008.1.1"
(0000, 0100, 02, Type Unknown) (48|30)
(0000, 0110, 02, Type Unknown) (1|1)
(0000, 0800, 02, Type Unknown) (257|101)
Forwarding CECHO-RQ 1
Waiting for CECHO-RSP
--------------- response (command) (1) -----------------
(0000, 0000, 04, Type Unknown) [70|46]
(0000, 0002, 22, Type Unknown) "1.2.840.10008.5.1.1.9"
(0000, 0100, 02, Type Unknown) (32816|8030)
(0000, 0120, 02, Type Unknown) (1|1)
(0000, 0800, 02, Type Unknown) (257|101)
(0000, 0900, 02, Type Unknown) (529|211)
Forwarding CECHO-RSP
...
This is repeated until the print job is manually deleted in the agfa application

B. And this is the result when efilm sends a print job:
********************************************************
A-ASSOCIATE-RQ Packet Dump
Calling Application Title : "My_AETitle "
Called Application Title : "DV5800 "
Application Context : "1.2.840.10008.3.1.1.1"
Number of Proposed Presentation Contexts: 1
Presentation Context 0 "1.2.840.10008.5.1.1.9"
--------------- command for request (1) -----------------
(0000, 0000, 04, Type Unknown) [60|3c]
(0000, 0002, 22, Type Unknown) "1.2.840.10008.5.1.1.1"
(0000, 0100, 02, Type Unknown) (320|140)
(0000, 0110, 02, Type Unknown) (369|171)
(0000, 0800, 02, Type Unknown) (258|102)
--------------- data for NCREATE request (1) -----------------
(2000, 0000, 04, Type Unknown) [10|a]
(2000, 0010, 02, Type Unknown) (8241|2031)
Forwarding NCREATE-RQ 1
Waiting for NCREATE-RSP
--------------- response (command) (1) -----------------
(0000, 0000, 04, Type Unknown) [132|84]
(0000, 0002, 22, Type Unknown) "1.2.840.10008.5.1.1.1"
(0000, 0100, 02, Type Unknown) (33088|8140)
(0000, 0120, 02, Type Unknown) (369|171)
(0000, 0800, 02, Type Unknown) (257|101)
(0000, 0900, 02, Type Unknown) (0|0)
(0000, 1000, 54, Type Unknown) "1.2.840.113564.11.192.168.1.150.2009.3.30.17.0.15.3714"
Forwarding NCREATE-RSP
--------------- command for request (1) -----------------
(0000, 0000, 04, Type Unknown) [60|3c]
(0000, 0002, 22, Type Unknown) "1.2.840.10008.5.1.1.2"
(0000, 0100, 02, Type Unknown) (320|140)
(0000, 0110, 02, Type Unknown) (371|173)
(0000, 0800, 02, Type Unknown) (258|102)
--------------- data for NCREATE request (1) -----------------
(2010, 0000, 04, Type Unknown) [206|ce]
(2010, 0010, 12, Type Unknown) "STANDARD\4,5"
(2010, 0040, 08, Type Unknown) "PORTRAIT"
(2010, 0050, 10, Type Unknown) "14INX17IN "
(2010, 0150, 00, Type Unknown) (null)
(2010, 0500, 00, Type Unknown) (null)
Forwarding NCREATE-RQ 1
Waiting for NCREATE-RSP
--------------- response (command) (1) -----------------
(0000, 0000, 04, Type Unknown) [132|84]
(0000, 0002, 22, Type Unknown) "1.2.840.10008.5.1.1.2"
(0000, 0100, 02, Type Unknown) (33088|8140)
(0000, 0120, 02, Type Unknown) (371|173)
(0000, 0800, 02, Type Unknown) (258|102)
(0000, 0900, 02, Type Unknown) (0|0)
(0000, 1000, 54, Type Unknown) "1.2.840.113564.11.192.168.1.150.2009.3.30.17.0.15.3716"
Forwarding NCREATE-RSP
--------------- response (data) (1) -----------------
(2010, 0000, 04, Type Unknown) [2116|844]
(2010, 0500, 100, Type Unknown) fffffffe(■)ffffffff( )00( )ffffffe0(Ó)5c(\)00( )00( )00( )08)00( )50
(P)11(◄)16(▬)00( )00( )00( )
(2010, 0510, 2000, Type Unknown) fffffffe(■)ffffffff( )00( )ffffffe0(Ó)5c(\)00( )00( )00( )08)00( )5
0(P)11(◄)16(▬)00( )00( )00( )
Forwarding NCREATE-RSP data field
--------------- command for request (1) -----------------
(0000, 0000, 04, Type Unknown) [122|7a]
(0000, 0003, 22, Type Unknown) "1.2.840.10008.5.1.1.4"
(0000, 0100, 02, Type Unknown) (288|120)
(0000, 0110, 02, Type Unknown) (373|175)
(0000, 0800, 02, Type Unknown) (258|102)
(0000, 1001, 54, Type Unknown) "1.2.840.113564.11.192.168.1.150.2009.3.30.17.0.15.3717"
--------------- data for NSET request (1) -----------------
(2020, 0000, 04, Type Unknown) [383238|5d906]
(2020, 0010, 02, Type Unknown) (1|1)
(2020, 0020, 06, Type Unknown) "NORMAL"
(2020, 0110, 00, Type Unknown) (null)
Forwarding NSET-RQ 1
Waiting for NSET-RSP
--------------- response (command) (1) -----------------
(0000, 0000, 04, Type Unknown) [132|84]
(0000, 0002, 22, Type Unknown) "1.2.840.10008.5.1.1.4"
(0000, 0100, 02, Type Unknown) (33056|8120)
(0000, 0120, 02, Type Unknown) (373|175)
(0000, 0800, 02, Type Unknown) (257|101)
(0000, 0900, 02, Type Unknown) (0|0)
(0000, 1000, 54, Type Unknown) "1.2.840.113564.11.192.168.1.150.2009.3.30.17.0.15.3717"
Forwarding NSET-RSP
--------------- command for request (1) -----------------
(0000, 0000, 04, Type Unknown) [132|84]
(0000, 0003, 22, Type Unknown) "1.2.840.10008.5.1.1.2"
(0000, 0100, 02, Type Unknown) (304|130)
(0000, 0110, 02, Type Unknown) (375|177)
(0000, 0800, 02, Type Unknown) (257|101)
(0000, 1001, 54, Type Unknown) "1.2.840.113564.11.192.168.1.150.2009.3.30.17.0.15.3716"
(0000, 1008, 02, Type Unknown) (1|1)
Forwarding NACTION-RQ 1
Waiting for NACTION-RSP
--------------- response (command) (1) -----------------
(0000, 0000, 04, Type Unknown) [142|8e]
(0000, 0002, 22, Type Unknown) "1.2.840.10008.5.1.1.2"
(0000, 0100, 02, Type Unknown) (33072|8130)
(0000, 0120, 02, Type Unknown) (375|177)
(0000, 0800, 02, Type Unknown) (257|101)
(0000, 0900, 02, Type Unknown) (0|0)
(0000, 1000, 54, Type Unknown) "1.2.840.113564.11.192.168.1.150.2009.3.30.17.0.15.3716"
(0000, 1008, 02, Type Unknown) (1|1)
Forwarding NACTION-RSP

Marcel,
it works as you described, perfect, thanks a lot!

Kind regards
Alexander

Thank you, that looks great. A few questions remain:

Quote

test -fp incomingport outgoinghost outgoinghost loglevel

sorry for the beginner question: you specified outgoing host twice. You mean camera IP and port?

something like

>test -fp 4711[listening port] 172.nn.nn.n [camera-IP] 0815[camera-port] s[as 'small log' or similar] ?

>test.exe

gives
>usage: dicom [-v filename ] | [-l:local_acr_nema] [-r:remote_acr_nema] [-s<e|s|c>|e|f|m] [-1]<host &| port>

=>???

Thank you

What should I do if I wanted to do the following:

Three parallel networks (TCP/IP, one 10/100 Mbit, two 10Mbit. Different address-spaces, for each vendor one )
All three networks are connected to a Conquest PACS server (with three network cards)
We have a laser camera with only one network adapter.

How could I rout dicom print-jobs from every one of the three networks to one computer (like the conquest-server) and connect him to the laser camera?

The most elegant would be to let the conquest server do the job, collecting the pritn jobs and routing them to the camera.

Thanks for any input.

Alexander

Technically, conquest might be easily able to perform the task of storing and distributing such a low number of images (I use it as a 'commodity pacs' with 30 clients while still archiving on film). However, you have to distinguish image storing and archiving. To my knowledge, there is no built-in backup-solution and no provision for archiving. A solution might be to simply mirror the entire data (HD are cheap nowdays), but you have to provide backup for the operating system, the database and the data by yourself. Using conquest, you need workstations (e.g. the last free efilm version 1.5.3 ) to review the images.
Conquest scan use mysql.

Konquest, on the other hand, has a useable built-in viewer. But if I remember correctly, kpacs is based on an access-db, which precludes professional use as a storage solution.

There are pacs solutions including a pc, db, pacs software, raid including mirroring the operating system, and a tape-streamer for backup. Price was in the range of 20000-24000 €.

Depends on what kind of "small office" you are running...

Regards

Thanks a lot for the tip. Yes, I used mysql. I'll search for the development os mysql and conquest during the last rwo years.
Kind regards

We have an installation with Conquest 1.4.12 alpha here. It works (worked...) flawlessly with 1.4 * 10^6 images, 750 Gb of size. However, we had to rebuild the database to switch to a larger disk, which became tedious. The "regen" or "re-initialize" feature of Version 1.4.12 alpha slows down to approx 2 images in 3 seconds after approx 800 000 images and continues to slow down. If you don't have time to wait for weeks for the rebuilt of the db and stop the regen, you are left with a working database, but an incomplete and painfully slow one.

So actually the only fesible approach appears to be to copy smaller chunks of the files (in the range of 50-100 000 images) to other pcs, import them there into other conquest db, and send them from there via dicom to the main db. This is a task for days . I don't know if there actually is available a streamlined integration of conquest with mysql and a pref file/ini-file appropriate for larger db, but two years ago (the time when we started our 'provisorial' conquest-PACS) there wasn't any.

I would be interested in any suggestions.

Kind regards

I too suggest Conquest. It works (worked...) flawlessly with 1.4 * 10^6 images, 750 Gb of size. However, if you have to rebuild your database, e.g. if you switch to a larger disk, this becomes a tedious task. The "regen" or "re-initialize" feature of Version 1.4.12 alpha slows down to approx 2 images in 3 seconds after approx 800 000 images and continues to slow down. If you don't have time to wait for weeks for the rebuilt of the db and stop the regen, you are left with a working database, but an incomplete and painfully slow one.

So actually the only fesible approach appears to be to copy smaller chunks of the files (in the range of 50-100 000 images) to other pcs, import them there into other conquest db, and send them from there via dicom to the main db. This is a task for days :(. I don't know if there actually is available a streamlined integration of conquest with mysql and a pref file/ini-file appropriate for larger db, but two years ago (the time when we started our 'provisorial' conquest-PACS) there wasn't any.

I would be interested in any suggestions.

Kind regards