|
I have a new dll
from FLI called mmgr_dal_FLICamera.dll. I put it in the Micro-Manager directory
with the other mmgr_dal dlls but it doesn't appear in the Hardware Configuration
Manager, Add Device List. Is there something else I'm suppose to do to get
Micro-Manager to find this dll?
Thanks ====================================================================== If you have received this electronic transmission in error, ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ micro-manager-general mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/micro-manager-general |
|
Hi Paul,
Does your DLL match the current device interface version number? And are you using the same platform (32 or 64 bit) for your DLL and Micro-Manager? Lastly, you may need to check the bottom of the device list, because devices in the MMDeviceList.txt file will appear first. Best regards, Arthur On Fri, Nov 4, 2011 at 8:34 AM, Cousoulis, Paul <[hidden email]> wrote:
------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ micro-manager-general mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/micro-manager-general |
|
In reply to this post by Cousoulis, Paul
It's not showing up on the bottom of the device list. Is the device interface version number something I can find from a dump?
Here is the top part of a MinGw objdump -p: mmgr_dal_FLICamera.dll: file format pei-i386 Characteristics 0x2102 executable 32 bit words DLL Time/Date Fri Dec 24 14:56:31 2010 ImageBase 10000000 SectionAlignment 00001000 FileAlignment 00000200 MajorOSystemVersion 5 MinorOSystemVersion 0 MajorImageVersion 0 MinorImageVersion 0 MajorSubsystemVersion 5 MinorSubsystemVersion 0 Win32Version 00000000 SizeOfImage 00064000 SizeOfHeaders 00000400 CheckSum 00064c0d Subsystem 00000002 (Windows GUI) DllCharacteristics 00000000 SizeOfStackReserve 00100000 SizeOfStackCommit 00001000 SizeOfHeapReserve 00100000 SizeOfHeapCommit 00001000 LoaderFlags 00000000 NumberOfRvaAndSizes 00000010 The Data Directory Entry 0 00058380 00000972 Export Directory [.edata (or where ever we found it)] Entry 1 0005798c 00000064 Import Directory [parts of .idata] Entry 2 0005e000 000001b4 Resource Directory [.rsrc] Entry 3 00000000 00000000 Exception Directory [.pdata] Entry 4 00000000 00000000 Security Directory Entry 5 0005f000 0000340c Base Relocation Directory [.reloc] Entry 6 00048230 0000001c Debug Directory Entry 7 00000000 00000000 Description Directory Entry 8 00000000 00000000 Special Directory Entry 9 00000000 00000000 Thread Storage Directory [.tls] Entry a 00053760 00000040 Load Configuration Directory Entry b 00000000 00000000 Bound Import Directory Entry c 00048000 000001b8 Import Address Table Directory Entry d 00000000 00000000 Delay Import Directory Entry e 00000000 00000000 Reserved Entry f 00000000 00000000 Reserved >Hi Paul, >Does your DLL match the current device interface version number? And are >you using the same platform (32 or 64 bit) for your DLL and Micro-Manager? >Lastly, you may need to check the bottom of the device list, because >devices in the MMDeviceList.txt file will appear first. >Best regards, >Arthur >On Fri, Nov 4, 2011 at 8:34 AM, Cousoulis, Paul ><pcousoulis@...: >> ** >> I have a new dll from FLI called mmgr_dal_FLICamera.dll. I put it in the >> Micro-Manager directory with the other mmgr_dal dlls but it doesn't appear >> in the Hardware Configuration Manager, Add Device List. Is there something >> else I'm suppose to do to get Micro-Manager to find this dll? >> >> Thanks ====================================================================== This electronic message transmission and any attachments are confidential and/or proprietary and may constitute legally privileged information of Meso Scale Diagnostics, LLC. The information is intended for solely the use of '[hidden email]' ([hidden email]). If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or the taking of any action in reliance of this information is strictly prohibited. You are not authorized to retain it in any form nor to re-transmit it, and you should destroy this email immediately. If you have received this electronic transmission in error, please notify us by telephone (240-631-2522) or by electronic mail to the sender of this email, Cousoulis, Paul ([hidden email]), immediately. ===================================================================== ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ micro-manager-general mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/micro-manager-general |
|
Hi Paul,
Where is the DLL from? Did you write it yourself? Otherwise you will likely need to get help from the authors. Best regards, Arthur On Fri, Nov 4, 2011 at 1:08 PM, Cousoulis, Paul <[hidden email]> wrote: It's not showing up on the bottom of the device list. Is the device interface version number something I can find from a dump? ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ micro-manager-general mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/micro-manager-general |
|
Administrator
|
In reply to this post by Cousoulis, Paul
Hi Paul.
> It's not showing up on the bottom of the device list. Is the device interface version number something I can find from a dump? Run Micro-Manager in debug mode (Tools->Options) from the command line (or scour through the Corelog.txt file) and look what Micro-Manager does with your dll when you start the Hardware Configuration Wizard. If you are building against the current code in the repository, make sure that you run the latest nightly build, NOT the latest release (1.4.6). Best, Nico ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ micro-manager-general mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/micro-manager-general |
|
In reply to this post by Cousoulis, Paul
Running in debug mode I get in the Log file. LOG(2011-11-04T16:44:35.957710, 6052, 000E6470:): > FLICamera LOG(2011-11-04T16:44:35.957710, 6052, 000E6470:): Error occured. Device core. Module interface version: core=7, library=4 LOG(2011-11-04T16:44:35.957710, 6052, 000E6470:): > Unable to load FLICamera library. java.lang.Exception: Module interface version: core=7, library=4 in Thread[AWT-EventQueue-0,6,main] at mmcorej.MMCoreJJNI.CMMCore_getAvailableDevices(Native Method) at mmcorej.CMMCore.getAvailableDevices(CMMCore.java:200) at org.micromanager.conf.Device.getLibraryContents(Device.java:133) at org.micromanager.conf.MicroscopeModel.loadAvailableDeviceList(MicroscopeModel.java:247) at org.micromanager.conf.ConfiguratorDlg.initialize(ConfiguratorDlg.java:196) at org.micromanager.conf.ConfiguratorDlg.<init>(ConfiguratorDlg.java:104) at org.micromanager.MMStudioMainFrame$28.actionPerformed(MMStudioMainFrame.java:1383) at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1995) at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2318) at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:387) at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:242) at javax.swing.AbstractButton.doClick(AbstractButton.java:357) at javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:1220) at javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:1261) at java.awt.Component.processMouseEvent(Component.java:6041) at javax.swing.JComponent.processMouseEvent(JComponent.java:3265) at java.awt.Component.processEvent(Component.java:5806) at java.awt.Container.processEvent(Container.java:2058) at java.awt.Component.dispatchEventImpl(Component.java:4413) at java.awt.Container.dispatchEventImpl(Container.java:2116) at java.awt.Component.dispatchEvent(Component.java:4243) at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4322) at java.awt.LightweightDispatcher.processMouseEvent(Container.java:3986) at java.awt.LightweightDispatcher.dispatchEvent(Container.java:3916) at java.awt.Container.dispatchEventImpl(Container.java:2102) at java.awt.Window.dispatchEventImpl(Window.java:2440) at java.awt.Component.dispatchEvent(Component.java:4243) at java.awt.EventQueue.dispatchEvent(EventQueue.java:599) at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:273) at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:183) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:173) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:168) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:160) at java.awt.EventDispatchThread.run(EventDispatchThread.java:121) I'll pass this along to the author. Thanks Paul ====================================================================== This electronic message transmission and any attachments are confidential and/or proprietary and may constitute legally privileged information of Meso Scale Diagnostics, LLC. The information is intended for solely the use of '[hidden email]' ([hidden email]). If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or the taking of any action in reliance of this information is strictly prohibited. You are not authorized to retain it in any form nor to re-transmit it, and you should destroy this email immediately. If you have received this electronic transmission in error, please notify us by telephone (240-631-2522) or by electronic mail to the sender of this email, Cousoulis, Paul ([hidden email]), immediately. ===================================================================== ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ micro-manager-general mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/micro-manager-general |
|
Administrator
|
On Nov 4, 2011, at 1:50 PM, Cousoulis, Paul wrote:
> Running in debug mode I get in the Log file. > > LOG(2011-11-04T16:44:35.957710, 6052, 000E6470:): > FLICamera > LOG(2011-11-04T16:44:35.957710, 6052, 000E6470:): Error occured. Device core. Module interface version: core=7, library=4 Micro-Manager 1.3 uses module version 4. You could see if the device shows up in 1.3. For this (and other reasons), we encourage all device adapter authors to donate their code to the Micro-Manager repository. If the authors so wishes, we can keep the code non-public. Only by having the code compiled at the same time can we guarantee that their versions will match. Best, Nico ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ micro-manager-general mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/micro-manager-general |
|
In reply to this post by Cousoulis, Paul
The dll works with version 1.3. Thank you Paul ====================================================================== This electronic message transmission and any attachments are confidential and/or proprietary and may constitute legally privileged information of Meso Scale Diagnostics, LLC. The information is intended for solely the use of '[hidden email]' ([hidden email]). If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or the taking of any action in reliance of this information is strictly prohibited. You are not authorized to retain it in any form nor to re-transmit it, and you should destroy this email immediately. If you have received this electronic transmission in error, please notify us by telephone (240-631-2522) or by electronic mail to the sender of this email, Cousoulis, Paul ([hidden email]), immediately. ===================================================================== ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ micro-manager-general mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/micro-manager-general |
|
In reply to this post by Cousoulis, Paul
Hello,
I have a similar problem. I have rebuilt my device adapter using the most recient repository version 1.4 code and verified it with the test programs. I then place my adapter dll in the Micromanager directory and it is not seen by the hardware wizard. (also not at the bottom of the list) What do i need to do that I am missing? My adapter worked in the 1.3 version but failed under 1.4. I think i have made all the needed changes, it builds correctly and seems to test ok using the Library, Device and Core test programs. I am at a stand still now trying to get this released. Your help is needed. Thanks Louis |
|
Administrator
|
On Nov 15, 2011, at 3:38 PM, lashford wrote: > I have rebuilt my device adapter using the > most recient repository version 1.4 code and verified it with the test > programs. I then place my adapter dll in the Micromanager directory and it > is not seen by the hardware wizard. (also not at the bottom of the list) Are you running the latest nightly build of Micro-Manager? Your adapter will not work in Micro-Manager 1.4.6. You really, really, need the latest nightly build. Besr, Nico ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ micro-manager-general mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/micro-manager-general |
|
Nico,
Yes I am using SVN and do an 'update' prior to doing my build. Shouldn't that give me the latest build files? I think i am using ver 1.47 files. Louis |
|
Administrator
|
On Nov 15, 2011, at 5:22 PM, lashford wrote: > Yes I am using SVN and do an 'update' prior to doing my build. > Shouldn't that give me the latest build files? Yes, however, you are using binaries from a certain other version. When is the last time you installed Micro-Manager, i.e. what exact version are you running? > I think i am using ver 1.47 Download and install the latest nightly build. Please make sure that you are using he latest nightly build from: http://valelab.ucsf.edu/~MM/MMwiki/index.php/Micro-Manager_Nightly_Builds Best, Nico ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ micro-manager-general mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/micro-manager-general |
|
In reply to this post by Nico Stuurman
Nico,
Do how do I get my dll included in the Adapter List? I guess more to the point is how do I get my adapter included in the MM Builds. I will be creating other Device Adapters so I would like to get setup to be able to check in code if that is possible. Thanks, Louis Ashford |
|
> Do how do I get my dll included in the Adapter List?
Run your code from a Micro-Manager binary that has the same Device Interface version as the adapter that you build. > I guess more to the point is how do I get my adapter included in the MM Builds. I will be creating other Device Adapters so I would like to get setup to be able to check in code if that is possible. Pleas email us (me) the code that you want to be included. I'll add it to the repository and give you write access to that part of the repository. Best, Nico ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ micro-manager-general mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/micro-manager-general |
| Powered by Nabble | See how NAML generates this page |
