Micro-Manager

Re: RAMPS Problem (DavidA.Moore)

classic Classic list List threaded Threaded
♦
♦
 5 messages Options
Nikita Vladimirov
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: RAMPS Problem (DavidA.Moore)

Nikita Vladimirov

Hi, David,

I have recently fixed some bugs in RAMPS device adapter, and use it in MM without any problems. Firmware running on RAMPS is Sprinter, stages: Thorlabs DRV001.

Check my repo with the latest RAMPS code. Good luck!

Nikita Vladimirov




_______________________________________________
micro-manager-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/micro-manager-general
DavidA.Moore
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: RAMPS Problem (DavidA.Moore)

DavidA.Moore
Nikita,
Thank you for working on the RAMPS adapter. I am very excited to see general
purpose hardware integrated into micro-manager. The possibilities are
endless.

I would very much like to try your bug fixes, but I do not currently have a
build environment set up. Do you have any plans to merge your changes into
the nightly builds? Is it possible to share a compiled *.dll file? If not, I
will start working on a build environment.

Thanks Again!

David



--
Sent from: http://micro-manager.3463995.n2.nabble.com/


_______________________________________________
micro-manager-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/micro-manager-general
DavidA.Moore
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: RAMPS Problem (DavidA.Moore)

DavidA.Moore
Nikita,

Thank you very much for your help, and for your support of this excellent
open source tool!

 I copied your DLL into the Micro-Manager 1.4 install directory.
Unfortunately, the results are the same.


Here are my symptoms:
I am able to select, and apparently install RAMPS in the Hardware
Configuration Wizard, including selection of the XY and Z stage.
I am able to save the configuration, although trying to reload the
configuration gives an error
        "Error: Failed to load hardware configuration, Line 31:
Property,Core,Initialize,1, Error in device "RAMPSHub":(Error message
unavailable) (110)
I am unable to move the steppers using the Stage Control GUI.
Using the same hardware, I am able to install Free Serial Port and fully
control the RAMPS board through beanshell g-code.

Here is my environment"
 2018-12-21T11:25:00.462733 tid6200 [IFO,App] MM Studio version: 1.4.23
20181210
2018-12-21T11:25:00.462733 tid6200 [IFO,App] MMCore version 8.7.1
2018-12-21T11:25:00.462733 tid6200 [IFO,App] Device API version 69, Module
API version 10
2018-12-21T11:25:00.462733 tid6200 [IFO,App] Operating System: Windows 7
(amd64) 6.1
2018-12-21T11:25:00.462733 tid6200 [IFO,App] JVM: Java HotSpot(TM) 64-Bit
Server VM, version 1.6.0_31, 64-bit

RAMPS 1.4, Marlin
   * Marlin release version identifier
   */
  #define SHORT_BUILD_VERSION "1.1.9"

Excerpts from Log:

RAMPS loading:
2018-12-21T11:25:22.383081 tid6200 [IFO,App] RAMPS
2018-12-21T11:25:22.394082 tid6200 [IFO,App]    RAMPSXYStage, RAMPS XY stage
2018-12-21T11:25:22.394082 tid6200 [IFO,App]    RAMPSZStage, RAMPS Z stage
2018-12-21T11:25:22.394082 tid6200 [IFO,App]    RAMPSHub, RAMPS hub

Configuring RAMPS in Hardware Configuration Wizard:
2018-12-21T11:25:26.537319 tid6200 [IFO,Core] Did load device COM1 from
SerialManager; label = COM1
2018-12-21T11:25:26.538319 tid6200 [IFO,Core] Did load device COM3 from
SerialManager; label = COM3
2018-12-21T11:25:26.538319 tid6200 [IFO,Core] Did load device COM4 from
SerialManager; label = COM4
2018-12-21T11:25:26.538319 tid6200 [IFO,Core] Did load device TCP/IP serial
port adapter (1) from TCPIPPort; label = TCP/IP serial port adapter (1)
2018-12-21T11:25:35.818850 tid6200 [IFO,Core] Did load device RAMPSHub from
RAMPS; label = RAMPSHub
2018-12-21T11:25:48.673585 tid6200 [IFO,Core] Did load device COM4 from
SerialManager; label = COM4
2018-12-21T11:25:48.673585 tid6200 [IFO,Core] Will initialize device COM4
2018-12-21T11:25:48.682585 tid6200 [IFO,dev:COM4] Setting standard USB to
Serial settings
2018-12-21T11:25:48.727588 tid6200 [IFO,Core] Did initialize device COM4
2018-12-21T11:25:49.729645 tid6200 [IFO,Core] Will initialize device
RAMPSHub
2018-12-21T11:25:51.770762 tid6200 [IFO,Core] Did initialize device RAMPSHub
2018-12-21T11:25:58.048121 tid6200 [IFO,Core] Did load device RAMPSXYStage
from RAMPS; label = RAMPSXYStage
2018-12-21T11:25:58.048121 tid6200 [IFO,Core] Will initialize device
RAMPSXYStage
2018-12-21T11:25:58.048121 tid6200 [IFO,Core] Did initialize device
RAMPSXYStage
2018-12-21T11:25:58.048121 tid6200 [IFO,Core] Did load device RAMPSZStage
from RAMPS; label = RAMPSZStage
2018-12-21T11:25:58.049121 tid6200 [IFO,Core] Will initialize device
RAMPSZStage
2018-12-21T11:25:58.058122 tid6200 [IFO,Core] Did initialize device
RAMPSZStage
2018-12-21T11:26:07.312651 tid6200 [IFO,dev:RAMPSHub] busy expected OK,
didn't get it.
2018-12-21T11:26:07.312651 tid6200 [IFO,dev:RAMPSHub] ok
2018-12-21T11:26:07.312651 tid6200 [IFO,dev:RAMPSHub] debug string 1
2018-12-21T11:26:20.247391 tid6200 [IFO,Core] Did unload all devices
2018-12-21T11:26:20.314395 tid6200 [IFO,Core] Did unload all devices
2018-12-21T11:26:20.314395 tid6200 [IFO,Core] Did load device COM4 from
SerialManager; label = COM4
2018-12-21T11:26:20.314395 tid6200 [IFO,Core] Did load device RAMPSHub from
RAMPS; label = RAMPSHub
2018-12-21T11:26:20.314395 tid6200 [IFO,Core] Did load device RAMPSXYStage
from RAMPS; label = RAMPSXYStage
2018-12-21T11:26:20.314395 tid6200 [IFO,Core] Did load device RAMPSZStage
from RAMPS; label = RAMPSZStage
2018-12-21T11:26:20.314395 tid6200 [IFO,Core] Will initialize 4 devices
2018-12-21T11:26:20.314395 tid6200 [IFO,Core] Will initialize device COM4
2018-12-21T11:26:20.324395 tid6200 [IFO,dev:COM4] Setting standard USB to
Serial settings
2018-12-21T11:26:20.369398 tid6200 [IFO,Core] Did initialize device COM4
2018-12-21T11:26:20.369398 tid6200 [IFO,Core] Will initialize device
RAMPSHub
2018-12-21T11:26:22.403514 tid6200 [IFO,Core] Did initialize device RAMPSHub
2018-12-21T11:26:22.403514 tid6200 [IFO,Core] Will initialize device
RAMPSXYStage
2018-12-21T11:26:22.403514 tid6200 [IFO,Core] Did initialize device
RAMPSXYStage
2018-12-21T11:26:22.403514 tid6200 [IFO,Core] Default xy stage set to
RAMPSXYStage
2018-12-21T11:26:22.403514 tid6200 [IFO,Core] Will initialize device
RAMPSZStage
2018-12-21T11:26:22.411515 tid6200 [IFO,Core] Did initialize device
RAMPSZStage
2018-12-21T11:26:22.411515 tid6200 [IFO,Core] Finished initializing 4
devices
2018-12-21T11:26:22.411515 tid6200 [IFO,Core] Default stage set to
RAMPSZStage
2018-12-21T11:26:22.419515 tid6200 [IFO,dev:RAMPSHub] busy expected OK,
didn't get it.
2018-12-21T11:26:22.419515 tid6200 [IFO,dev:RAMPSHub] ok
2018-12-21T11:26:22.419515 tid6200 [IFO,dev:RAMPSHub] debug string 1
2018-12-21T11:26:22.429516 tid6200 [IFO,dev:RAMPSHub] busy expected OK,
didn't get it.
2018-12-21T11:26:22.429516 tid6200 [IFO,dev:RAMPSHub] ok
2018-12-21T11:26:22.429516 tid6200 [IFO,dev:RAMPSHub] debug string 1
2018-12-21T11:26:22.439516 tid6200 [IFO,dev:RAMPSHub] busy expected OK,
didn't get it.
2018-12-21T11:26:22.439516 tid6200 [IFO,dev:RAMPSHub] ok
2018-12-21T11:26:22.439516 tid6200 [IFO,dev:RAMPSHub] debug string 1
2018-12-21T11:26:22.449517 tid6200 [IFO,dev:RAMPSHub] busy expected OK,
didn't get it.
2018-12-21T11:26:22.449517 tid6200 [IFO,dev:RAMPSHub] ok
2018-12-21T11:26:22.449517 tid6200 [IFO,dev:RAMPSHub] debug string 1
2018-12-21T11:26:22.459517 tid6200 [IFO,dev:RAMPSHub] busy expected OK,
didn't get it.
2018-12-21T11:26:22.459517 tid6200 [IFO,dev:RAMPSHub] ok
2018-12-21T11:26:22.459517 tid6200 [IFO,dev:RAMPSHub] debug string 1
2018-12-21T11:26:22.459517 tid6200 [IFO,Core] Did update system state cache
2018-12-21T11:26:22.468518 tid6200 [IFO,dev:RAMPSHub] busy expected OK,
didn't get it.
2018-12-21T11:26:22.468518 tid6200 [IFO,dev:RAMPSHub] ok
2018-12-21T11:26:22.468518 tid6200 [IFO,dev:RAMPSHub] debug string 1
2018-12-21T11:26:22.477518 tid6200 [IFO,dev:RAMPSHub] answer get error!_
2018-12-21T11:26:22.477518 tid6200 [IFO,App] Updating GUI; config pad =
true; from cache = false
2018-12-21T11:26:22.481519 tid6200 [IFO,dev:RAMPSHub] busy expected OK,
didn't get it.
2018-12-21T11:26:22.481519 tid6200 [IFO,dev:RAMPSHub] ok
2018-12-21T11:26:22.481519 tid6200 [IFO,dev:RAMPSHub] debug string 1
2018-12-21T11:26:25.998720 tid5204 [IFO,App] EDTHangLogger: Missed
heartbeat; waiting to see if we are stuck on a single event
2018-12-21T11:26:27.000777 tid5204 [IFO,App] EDTHangLogger: Event handling
has exceeded at least 1001 ms (currently 5502 ms since heartbeat timebase)


Thank you once again!

David





--
Sent from: http://micro-manager.3463995.n2.nabble.com/


_______________________________________________
micro-manager-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/micro-manager-general
Simon Thibodeau
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: RAMPS Problem (DavidA.Moore)

Simon Thibodeau
In reply to this post by Nikita Vladimirov
Could you please tell me what version of Sprinter you are using ? I am having
similar issues with Marlin too



--
Sent from: http://micro-manager.3463995.n2.nabble.com/


_______________________________________________
micro-manager-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/micro-manager-general
Simon Thibodeau
Reply | Threaded
Open this post in threaded view
♦
♦
|

Re: RAMPS Problem (DavidA.Moore)

Simon Thibodeau
Update: I was able to make the adapter work when I uploaded the latest
version of Sprinter to my RAMPS.

Perhaps the adapter is just not compatible with Marlin?



--
Sent from: http://micro-manager.3463995.n2.nabble.com/


_______________________________________________
micro-manager-general mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/micro-manager-general
Free forum by Nabble Edit this page