search

pymedphys / pymedphys

A community effort to develop an open standard library for Medical Physics in Python. Building quality transparent software together via peer review and open source distribution. Open code is better science.
https://docs.pymedphys.com
Apache License 2.0
309 stars 73 forks source link

iCOM listener protocol able to cause the sequencer to lose connection to the Linac #849

Open SimonBiggs opened 4 years ago

SimonBiggs commented 4 years ago

In both the pymedphys iCOM listener tool, and other commercial iCOM listener tools I have been able to have access to I have found that the listener itself can cause Mosaiq to stop recording a treatment delivery. The treatment delivery continues uninterrupted, the treatment staff are then prompted by Mosaiq to write in the actual delivered MUs.

This appears to be reproducible with all iCOM listeners I have been able to test this with by undergoing the following steps:

chop-shape commented 4 years ago

Hi, Simon. Have you fixed this bug or do you have any strategy to avoid the "lose connection". elekta log bug_mosaiq elekta log bug1

SimonBiggs commented 4 years ago

Hi @chop-shape,

There certainly is a few strategies we have. Make sure that the network connection between the NSS and the centre router, and then the computer that the listener is running on is stable. Leave the listener running while the machine is running.

Currently I have a case with Elekta regarding this.

Can I ask specifically what are the reproducible steps that causes the issue on your end?

chop-shape commented 4 years ago

Thanks for your reply.

My linac is Synergy with a MLCi2 head and NSS is not equiped. I installed the iCOM listener service on the computer which is on the same local nerwork as NRT. Set the linac IP and 1706 port, then started the listener, about ten minutes later the linac can not work.

SimonBiggs commented 4 years ago

Hi @chop-shape,

I personally wouldn't recommend installing anything on any of the machines on the NRT network. Instead, just install it on one of your own machines within your centre, and point the IP address of the iCom listener to the external NSS IP.

icetomato commented 2 years ago

@chop-shape can you get the Solution?

SimonBiggs commented 2 years ago

@icetomato there's quite a bit of details around setting up an iCom listener over at:

https://docs.pymedphys.com/lib/howto/add-a-linac.html

SimonBiggs commented 2 years ago

@icetomato, let me know if you need any help. We could potentially set up a video call if that would help?

icetomato commented 2 years ago

@SimonBiggs

Thank you, I will try this method https://docs.pymedphys.com/lib/howto/add-a-linac.html and i just want konw if the hospital don't have NSS how can i get icomlogs safety and don't let the treatment machine doesn't work
just like this image

SimonBiggs commented 2 years ago

The lose connection issue is common to all iCOM listeners that listen to Elekta's standard interface. I have observed it occuring when there is an abrupt network disconnect between the iCOM listener and the linac. Such as a power failure on the computer running the listener software, or disconnecting the network cable on the iCOM listener.

I would be surprised if your Linac didn't have an NSS. I was under the impression that was a standard feature of Elekta Linacs. @brjdenis are you aware of Elekta Linacs coming without an NSS?

mchamberland commented 1 year ago

The lose connection issue is common to all iCOM listeners that listen to Elekta's standard interface. I have observed it occuring when there is an abrupt network disconnect between the iCOM listener and the linac. Such as a power failure on the computer running the listener software, or disconnecting the network cable on the iCOM listener.

I can confirm. I have just reproduced this bug using the RadCalc Linac Logger. I will independently open a ticket with Elekta.

SimonBiggs commented 1 year ago

Thanks @mchamberland :slightly_smiling_face: