Recent Posts

Pages: [1] 2 3 ... 10
1
Issues/Problems / Re: Latest Win10 Upgrade
« Last post by James_Pickard on May 16, 2018, 12:09:10 pm »
Hi poepol,

Thank you for your post.  I assume you are talking about the latest feature update for Windows 10, 1803?

Regardless, unfortunately Medmont Studio version 5 is not supported on Windows 10.  Only version 6 is supported.  To continue to use Medmont Studio on Windows 10, please upgrade to version 6.  Please contact your local distributor who can assist with this.  They can be found here:

http://medmont.com/contact/

There could also be an issue with your E300 instrument if Windows is unable to detect it.  Contact your local distributor to find out if there is a problem there and they will be able to assist. 

Kind regards,
2
Issues/Problems / Latest Win10 Upgrade
« Last post by poepol on May 15, 2018, 09:03:24 pm »
Hi

Since the latest Win10 feature upgrade a few days ago Medmont Studio (ver 5) does not recognise my E300. I checked the licence and E300 are loaded, all seems OK.

Solution?

Thanks
3
Issues/Problems / SOLVED: Review stations can't connect to Medmont Studio Server
« Last post by RobJ on February 10, 2018, 02:32:27 am »
Shortly after I made the original post above, I also submitted a support request at medmont.com/support.  I immediately rec'd an e-mail confirming my request.  Three minutes later I rec'd an e-mail from James Picard (Support, Medmont Intl.) directing me to contact the distributor (Precision Technology Services, Vancouver, BC. Canada) from whom we purchased our topographer.  James provided all the necessary contact info for Precision Tech Svc.  I reached out to Precision via e-mail and literally minutes later I rec'd a phone call from Dave Barreto, IT Specialist for Precision Tech Svc.  After explaining my situation to Dave, he was able to walk me through some trouble shooting and a final resolution.  W O W !!!  I wish all of the vendors that I deal with were as on-the-ball as Medmont and Precision Technology Services.  After a long and frustrating day, I left work with a sense of accomplishment.  Thanks!

The final solution was a quick change to the server.settings file on the server.  Even though I specified the <ServerAddress> as the IP of the server (rather than using the hostname), I had to change the setting <UseIpAddress> from true to false.  How's that for a head scratcher? 
4
Issues/Problems / Solved: Review stations can't connect to Medmont Studio Server
« Last post by RobJ on February 09, 2018, 07:47:54 am »
As stated in the subject, I'm unable to get review stations to connect to the server.  We're running v 6.0.3.3 on Win 7 x86 on the review station and server.  The server has a static IP, the IP and port number are correct in the Client.Settings file.  I grabbed a WireShark and can see the SYN:ACK going back and forth between the two.  Here's a snip from the MedmontStudio.log:

**** 2/8/2018 11:20:37 AM Exception (The type initializer for 'Medmont.Studio.Data.StudioProxy' threw an exception.) in XmlArrayList while reading Medmont.M700.Client.ThresholdPrintReport - the remainder of this item will be ignored
**** 2/8/2018 11:20:37 AM Exception (The type initializer for 'Medmont.Studio.Data.StudioProxy' threw an exception.) in XmlArrayList while reading Medmont.M700.Client.ThresholdPrintReport - the remainder of this item will be ignored
**** 2/8/2018 11:20:37 AM Exception (The type initializer for 'Medmont.Studio.Data.StudioProxy' threw an exception.) in XmlArrayList while reading Medmont.M700.Client.ThresholdMultiPrintReport - the remainder of this item will be ignored
**** 2/8/2018 11:20:37 AM Exception (The type initializer for 'Medmont.Studio.Data.StudioProxy' threw an exception.) in XmlArrayList while reading Medmont.M700.Client.ThresholdMultiPrintReport - the remainder of this item will be ignored
**** 2/8/2018 11:20:37 AM Exception (The type initializer for 'Medmont.Studio.Data.StudioProxy' threw an exception.) in XmlArrayList while reading Medmont.M700.Client.ThresholdGlaucomaReport - the remainder of this item will be ignored
**** 2/8/2018 11:20:37 AM Exception (The type initializer for 'Medmont.Studio.Data.StudioProxy' threw an exception.) in XmlArrayList while reading Medmont.M700.Client.ThreeZoneReport - the remainder of this item will be ignored
**** 2/8/2018 11:20:37 AM Exception: SocketException
Description: No connection could be made because the target machine actively refused it 127.0.0.1:8085
Source: mscorlib

Stack Trace

Server stack trace:
   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
   at System.Runtime.Remoting.Channels.RemoteConnection.CreateNewSocket(EndPoint ipEndPoint)
   at System.Runtime.Remoting.Channels.RemoteConnection.CreateNewSocket()
   at System.Runtime.Remoting.Channels.RemoteConnection.GetSocket()
   at System.Runtime.Remoting.Channels.SocketCache.GetSocket(String machinePortAndSid, Boolean openNew)
   at System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.SendRequestWithRetry(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream)
   at System.Runtime.Remoting.Channels.Tcp.TcpClientTransportSink.ProcessMessage(IMessage msg, ITransportHeaders requestHeaders, Stream requestStream, ITransportHeaders& responseHeaders, Stream& responseStream)
   at System.Runtime.Remoting.Channels.BinaryClientFormatterSink.SyncProcessMessage(IMessage msg)

Exception rethrown at
  • :

   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
   at Medmont.Data.DataObjectServer.ServerConfig()
   at Medmont.Data.DataObjectProxy.NewInstance(DataObjectServer sServer)
   at Medmont.Data.DataObjectProxy..ctor(DataObjectServer sServer)
   at Medmont.Studio.Data.StudioProxy.NewProxy(String sName)
   at Medmont.Studio.Data.StudioProxy..cctor()


Any suggestions?
5
Issues/Problems / Updating to v6.2.5 fails to download resource
« Last post by James_Pickard on January 25, 2018, 12:26:54 pm »
An error occurs when trying to update to Medmont Studio v6.2.5 with the following error:

"An error occurred while downloading a required file.  You may retry downloading the file or cancel setup."

This is caused by Microsoft changing a link to one of the components needed by Medmont Studio to update and the installer can't download it.  While we work with Microsoft to get this rectified, the component can be downloaded and installed manually using the below links depending on whether your system is 32 or 64bit.

http://www.medmont.com/files/SQLLocalDb/sqlncli_x64.msi
http://www.medmont.com/files/SQLLocalDb/sqlncli_x86.msi

Once this has been installed, please retry the update installer and it should succeed.
6
FAQ / What part of the DICOM standard is supported?
« Last post by David on December 06, 2017, 11:28:30 am »
Medmont Studio software implements C-STORE and C-Find capability. The C-FIND command is used to import patient demographics from a work list server (avoid double data entry) while the C-STORE is used to submit print reports to a storage server.

Studio supports submitting reports in two formats;
1) EncapsulatedPDF and
2) Multi Frame True Colour Secondary Capture.

Medmont Studio also supports the ability to import DICOM files into the DV2000 diagnostic imaging module. The DICOM Watcher utility is provided to monitor a folder on your hard drive for new DICOM files. If it detects a new file it will automatically import that DICOM file, it does not require the DV2000 capture window to be opened. DICOM files, imported this way, must be in the Visible Light Photographic Image Class format.

A DV2000 license is required to import DICOM images into the DV2000 module.
7
Issues/Problems / Re: video mode processing
« Last post by Palani on October 10, 2017, 10:04:51 am »
Hi John,
I rang you this morning and someone told me that you are with a patient.
Can you please call me on 0392590811 ?
Thanks
Palani
8
Issues/Problems / Re: video mode processing
« Last post by John Boulos on October 07, 2017, 08:14:57 am »
Hi all
I have a similar issue, the images (static) have been captured, but I don't know how to view the video. Can anyone provide a tip?
Thanks
John
Modemont version 5.3.5
9
The Tear Film Quality map shows the tear film surface quality (TFSQ) over the surface of the eye at a given point in time.   This is basically a measurement at each point on the eye of local variability in the ring width.  Typically local tear film break down is characterized by a large variability in the ring width.

Mathematically the TFSQ at a point is calculated by finding the standard deviation (SD) in the widths of the surrounding rings 10 degrees either side of the point.  The TFSQ  at the point is then calculated as percentage of the square of the SD normalized by the average width (W) between the rings:

TFSQ = 100 * (SD / Average W)^2

A local TFSQ value of greater than 0.3 typically indicates that there is some tear film breakup going on in that area.

The TFSQ Area attribute (which is graphed over time in the bottom graph for Tear Film Exams) is the percentage of the eye, within a 7mm chord, that has a local TFSQ value greater than 0.3 (ie is in breakup).  So a value of 5 in the graph indicates that 5% of the eye surface has tear film breakup.

The Auto Tear Film Breakup Time (TBUT) is calculated by finding the first two consecutive frames where the TFSQ Area exceeds 5%.

The Tear Film Breakup map shows the time (in seconds) until the TFSQ exceeds 0.3 for each point on the cornea (ie the time till breakup).   It is useful for understanding how the tear film breakup progresses over time.
10
Feature Discussions & Suggestions / Re: Composite topography maps - best way to take
« Last post by Grant on August 31, 2017, 09:26:12 am »
While placido topography is more accurate toward the center, the drop off in accuracy for the E300 is very small.    It is more important that you have as large an overlap as possible between the captured images while still being able to capture rings right out to the limbus.   The new Composite Capture wizard in Version 6 makes getting this right much easier by providing guidance and auto capturing once the patient fixation is in the right area.
Pages: [1] 2 3 ... 10