Recent Posts

Pages: [1] 2 3 ... 10
1
Issues/Problems / Re: fixation light and bowl illumination not working
« Last post by Michael on June 29, 2018, 12:53:54 pm »
Hi there,

I would start by checking the fuses. You could also check to see if the central fixation light is on when you power up the machine and if you hold your hand inside the bowl at the 12 o'clock position you should see the background illumination increase. Can you please quickly test both of these things and if there is still no response, take out the patient switch and test again.

Kind Regards
Michael Eldridge
2
Issues/Problems / Re: fixation light and bowl illumination not working
« Last post by taringajohn on June 29, 2018, 07:21:33 am »
I now have this same problem. No lights at all, error on start of MStudio.

Green light on power cord entry is still on...could this be a fuse?
How did banoptic resolve the problem??
Thanks
3
Issues/Problems / Re: Latest Win10 Upgrade
« Last post by daveb on May 30, 2018, 02:35:38 am »
The issue you reported has been seen with v6 as well.
Try this, it might work for you too.

http://www.medmont.com/forum/index.php?topic=6807.0

But if not, please do understand that v5 is not officially supported on Windows 10.



4
Issues/Problems / Windows 10 Feature Update 1803 causing camera issues
« Last post by James_Pickard on May 29, 2018, 10:21:11 am »
We have had some reports of Windows 10 Feature Update 1803 causing problems with Medmont Studio being able to see our instrument cameras.  We are investigating this issue to find the root cause but have yet to reproduce it in our lab.

If you encounter this issue, please first try the troubleshooting steps listed here to re-enable your camera:
http://maxedtech.com/fix-camera-webcam-not-working-in-windows-10-1803/
(step 4 is not required)

We will continue to investigate the root cause of this issue and hope to have a permanent fix shortly.

Kind regards
5
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,
6
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
7
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? 
8
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?
9
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.
10
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.
Pages: [1] 2 3 ... 10