Dear Alex,
I noticed that opening the .tlh file with a text editor (after compiling), at
the end of the file there is an #include
in my case (row 4847) :
#include
"D:\Programmi\MITK\USGFW2-SDK-4.1.0\SDK\samples_cpp_vs2017\b_mode\sample\Debug\usgfw2.tli"
So, it also needs the .tli file.
To be honest, once I found a way , I didnt try to modify the path and add both
file to the MITK_US_TELEMED_SDK_PATH.
I thought it was cleaner in my case to leave the compiled files in the path and
link them by creating a new variable in the cmakegui.
Best regards,
Andrea
________________________________
From: Seitel, Alexander <a.sei...@dkfz-heidelberg.de>
Sent: Thursday, May 20, 2021 2:51 PM
To: Andrea Roberti <andrea.robe...@univr.it>
Cc: mitk-users@lists.sourceforge.net <mitk-users@lists.sourceforge.net>
Subject: RE: MITK Ultrasound Plugin
Dear Andrea,
Glad that you found a way to get it to work for your setting.
Re 2:
I wonder why adding a new flag is necessary. Wouldn’t it work if the usgfw2.tlh
file is in the location specified for ${MITK_US_TELEMED_SDK_PATH}$?
To keep the conversation on the mailing list, just also answer to
mitk-users@lists.sourceforge.net<mailto:mitk-users@lists.sourceforge.net>
Best
Alex
From: Andrea Roberti [mailto:andrea.robe...@univr.it]
Sent: Thursday, May 20, 2021 11:39 AM
To: Seitel, Alexander <a.sei...@dkfz-heidelberg.de>
Subject: Re: MITK Ultrasound Plugin
Dear Alexander,
I had already changed the CMakeLists to compile the 64 bit version
Anyway, I managed to get the ultrasound probe to work with 64bit!
Here are the various steps to make it work:
1) compile again the usgfw2.tlh file (inside there's an absolute path) with the
same version of VS. (MFC components are required)
2) I created a new CMake Flag (USGFW2) which is the PATH the lead to the
usgfw2.tlh file .
The CMakeLists to modify is in the source (Modules\US\USHardwareTelemed) , and
remove the if statement
MITK_CREATE_MODULE(
DEPENDS MitkUS
INCLUDE_DIRS "${MITK_US_TELEMED_SDK_PATH}" "${USGFW2}"
INTERNAL_INCLUDE_DIRS ${INCLUDE_DIRS_INTERNAL}
AUTOLOAD_WITH MitkUS
)
3) Fix error C2259: '<someclass>' : cannot instantiate abstract class
add in the header mitkUSTelemedDevice.h :
virtual mitk::USProbe::Pointer GetProbeByName(std::string name);
virtual mitk::USProbe::Pointer GetCurrentProbe();
virtual std::vector<mitk::USProbe::Pointer> GetAllProbes();
and in the source mitkUSTelemedDevice.cpp : also, an empty implementations of
the functions
The last thing I tried out of desperation was to run as administrator, and now
it works !
hope it helps someone!
Thanks
Andrea
PS: I dont know how to reply directly to the sourceforge, that's why i'm
sending email ??
________________________________
From: Seitel, Alexander
<a.sei...@dkfz-heidelberg.de<mailto:a.sei...@dkfz-heidelberg.de>>
Sent: Thursday, May 20, 2021 9:17 AM
To: Andrea Roberti <andrea.robe...@univr.it<mailto:andrea.robe...@univr.it>>
Cc: mitk-users@lists.sourceforge.net<mailto:mitk-users@lists.sourceforge.net>
<mitk-users@lists.sourceforge.net<mailto:mitk-users@lists.sourceforge.net>>
Subject: RE: MITK Ultrasound Plugin
Dear Andrea,
Please keep the conversation on the mailing list such that others are also
aware of potential solutions to your problem.
The current implementation of the Telemed device is only available for 32 bit
builds (cf.
https://phabricator.mitk.org/source/mitk/browse/develop/Modules/US/USHardwareTelemed/CMakeLists.txt)
You could test the 64 bit version of the SDK by disabling the respective if
statement in the CMake configuration of MITK.
Generally you have to make sure that both MITK and the Telemed SDK have the
same build configuration (32 bit vs 64 bit)
Best regards
Alex
From: Andrea Roberti [mailto:andrea.robe...@univr.it]
Sent: Wednesday, May 19, 2021 11:43 AM
To: Seitel, Alexander
<a.sei...@dkfz-heidelberg.de<mailto:a.sei...@dkfz-heidelberg.de>>
Subject: Re: MITK Ultrasound Plugin
Dear Alexander,
thanks for your quick reply !
We compiled the 32 bit version and also the 64 bit version (now the 64 bit
Telemed SDK is available! https://www.pcultrasound.com/download/sdk/)
In both versions we had no warnings or errors, and now we see all the plugins.
First, we download the SDK and execute the "usgfwsetup_x64", then we copied the
file "usgfw2.tlh" to the MITK_US_TELEMED_SDK_PATH.
Finally, we compile.
We tryed our device with EchoWave and it works.
how can we be sure we have all the files (on our build) needed to make Telemed
work on MITK?
Thanks in advance,
Andrea
________________________________
From: Seitel, Alexander
<a.sei...@dkfz-heidelberg.de<mailto:a.sei...@dkfz-heidelberg.de>>
Sent: Wednesday, May 19, 2021 9:23 AM
To: Andrea Roberti <andrea.robe...@univr.it<mailto:andrea.robe...@univr.it>>;
mitk-users@lists.sourceforge.net<mailto:mitk-users@lists.sourceforge.net>
<mitk-users@lists.sourceforge.net<mailto:mitk-users@lists.sourceforge.net>>
Cc: Chiara Tenga <chiarate...@gmail.com<mailto:chiarate...@gmail.com>>
Subject: RE: MITK Ultrasound Plugin
Dear Andrea,
Great that you found a way to get the plugins to work. The Ultrasound Module
within MITK provides a microservice based API for the ultrasound devices which
should, if the device is configured correctly, automatically make the device
available e.g. in the respective widgets (see also
https://docs.mitk.org/nightly/USModulePage.html). Unfortunately I’m not sure
how compatible the SDKs of LogiScan 128 and MicrUS EXT-1H are. Are you
experiencing any warnings / errors during CMake build and / or compilation of
the ultrasound module? That might help narrowing down the problem.
Best regards
Alex
From: Andrea Roberti [mailto:andrea.robe...@univr.it]
Sent: Tuesday, May 18, 2021 6:50 PM
To: mitk-users@lists.sourceforge.net<mailto:mitk-users@lists.sourceforge.net>
Cc: Chiara Tenga <chiarate...@gmail.com<mailto:chiarate...@gmail.com>>
Subject: Re: [mitk-users] MITK Ultrasound Plugin
Dear all,
we solved the previous problem! Now we are able to see the plugin and many
others related to the Navigation module.
But now we are facing another problem, we are unable to see the ultrasound
device with MITK.
Our model is Telemed MicrUS EXT-1H, which is different from the device you have
used for development ("Telemed LogicScan 128").
Is there any incompatibility with our device?
Do we have to implement the wrapper with the MITK libraries? or are we missing
something?
Thanks
Andrea
________________________________
From: Andrea Roberti <andrea.robe...@univr.it<mailto:andrea.robe...@univr.it>>
Sent: Wednesday, May 12, 2021 2:51 PM
To: mitk-users@lists.sourceforge.net<mailto:mitk-users@lists.sourceforge.net>
<mitk-users@lists.sourceforge.net<mailto:mitk-users@lists.sourceforge.net>>
Subject: [mitk-users] MITK Ultrasound Plugin
Dear all,
we are having some problem to activate the Ultrasound plugin !
Basically, we compile the MITK following the tutorial by adding the Telemed
API, etc (https://docs.mitk.org/nightly/USHardwareTelemedPage.html)
The compilation (32 bit) was successful, and we can see the dll in the path
(...\MITK-build\bin\Debug) but when we open the workbench there is no plugin or
icon like this https://docs.mitk.org/nightly/org_mitk_gui_qt_ultrasound.html
We verify that when we open the workbench we have all the paths including the
dll.
How can we load this plugin ?
Maybe we miss something !
Thanks in advance,
Andrea
_______________________________________________
mitk-users mailing list
mitk-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mitk-users
