Need Help: moving from CW to NanoDLP

[Bob Houin]

I am in the process of converting my Muve3d 1.5 from CW to NanoDLP.  A couple of things have come up that I am hoping the group here might be able to help with:

1. when I do the "/printer/distro/change" process and select the Muve3d version it changes my web screen to "site cannot be reached" as it seems to be restarting the Rasp PI.  Once the PI is restarted I log back in and I don't see the Muve3d setup.  So I have manually added the G code information into the setup form.  Not sure if this is the right thing to do or not here.

2. I can manually move the printer z axis up and down.  There are a couple of querks however.  I can use the mm up and down buttons and the z axis responds accordingly.  However, when I press TOP the z axis moves down.  I also can't get the measure z-axis length button to do anything except ask me if I want this point to be the bottom (note: I start the process after homing the z).

Below are screen shots of the setup page and the z axis calibration page.  I appreciate in advance any help that the group might be able to offer here.  

Regards,

Bob

[mUVe 3D Admin]

Bob,

While you're on the mUVe 3D version, the disconnect/reboot is the proper response from the machine, nanoDLP won't overwrite your settings on the distribution change. If you head back to the same page, the Setup -> Tools page, press the "Restore Default machine/profiles/buttons Settings" button and it will do the reboot again. Upon this reboot you should have the settings as intended. You may need to check your RAMPS USB port settings and your RS232 settings if you have a projector controller.

Once you've done that, the buttons and assignments that are available should work fine, after you've home the Z axis.

mUVe 3D Support

[Bob Houin]

Thanks.  That solved my issue with #1.  I get the basic issue with #2.

I have most everything done and I am now trying to get the z-axis to move the height that it is commanded.  Example, if I home the machine, then tell it to go up 100mm from the z-axis calibration screen the z-axis will move up 60mm.  I am thinking that something is off in the "Actuator/Motor" section of the setup screen.  Right now I have angle set to 1.8 and microstep set to 8 and leadscrew pitch set to 3mm.  I have the middle jumper on under the driver boards on the RAMPS.  

Any recommendations/thoughts?

[mUVe 3D Admin]

Bob,

Leadscrew settings in nanoDLP aren't manipulating anything when you have a printer controller board. Those settings are only for when you have a single stepper motor hooked directly to the GPIO of the Raspberry Pi.

You'll need to make your changes in the RAMPS/Arduino Firmware, and upload it to the board, in order to change the stepping resolution and make the correction.

If you're not trying to adjust the leadscrew resolution because of a leadscrew change/swap on your part, the error with motion is likely related to the motor power POT adjustment screw, or perhaps a mechanical bind of some kind. You'd have to watch the rotation of the leadscrews as you make commands to the printer in order to make that determination. The motion only being 60mm when 100mm is requested signals that something other than jumpers is out of place. Otherwise it would be a perfect multiple of 100mm that the motion is off by, i.e. 50mm, 25mm etc.

mUVe 3D Support

[Bob Houin]

Thanks.  I found a setting in the marlin firmware for the 1.1 that needed to be uncommented and comment out the 1.5 line.  This seems to have solved the problem.  Apparently I have a 1.1 version muve3d.

Off to the next step to test a print.  Slowly but surely getting there.

Thanks for the help.

[Bob Houin]

I have a couple of additional questions that I can't seem to find in the manual.

I am able to move the z-axis up and down and home and set z just fine.  However, when I try to print the calibration plate using the Muve3d 75 futaba profile I get some initial movement to setup for the first layer, then it stops.  No layer image on the display and the z-axis doesn't move.  I verified that the printer profile has this g code for before each layer:

M650 D{([[LayerNumber]]<30)*1+1} S0.5

M651

G4 P1000

G1 Z[[LayerPosition]]

[[WaitForDoneMessage]]

M114

[[PositionSet [[LayerPosition]]]]

and this g-code for after each layer:

[[PositionChange [[ZLiftDistance]]]]

Here is what I end up seeing in terminal

G28 G91

ok ok

M114

X:144.00Y:0.00Z:0.00E:0.00 Count X: 144.00Y:0.00Z:0.00 ok

M650 D5 S5 R1 G28 G90

M280 P2 S10

ok

M650 D2.0000 S0.5 M651 G4 P1000 G1 Z0.1

ok ok ok ok ok ok ok

[mUVe 3D Admin]

Bob,

What does the log say on the homepage? It'll tell you what it's doing at all times so there should be some explanation if we start there. Based on the terminal output you've posted here there isn't any tell as to what the cause might be.

Another place to look is the projector warmup time. If you have that variable on the setting page set with a value, there will be a pause before the print starts.

mUVe 3D Support

[Bob Houin]

Here is what the log shows:

Level	Layer	Time	Module	Details
Info	1	2016-07-30 18:50:36.756914	Terminal	Data Received ok↵
Info	1	2016-07-30 18:50:36.756342	Terminal	Data Received ok↵
Info	1	2016-07-30 18:50:35.754659	Terminal	Data Received ok↵
Info	1	2016-07-30 18:50:26.415192	Terminal	Data Received ok↵
Info	1	2016-07-30 18:50:26.409974	Terminal	Data Received ok↵
Info	1	2016-07-30 18:50:26.408514	Terminal	Data Received ok↵
Info	1	2016-07-30 18:50:26.398023	Terminal	Data Received ok↵
Info	1	2016-07-30 18:50:26.37495	Gcode	Waiting for done message from controller
Debug	1	2016-07-30 18:50:26.369196	Gcode	Transfering Data M650 D2.0000 S0.5↵M651↵G4 P1000↵G1 Z0.1↵
Info	1	2016-07-30 18:50:26.367127	Terminal	Data Received ok↵
Debug	1	2016-07-30 18:50:26.365815	Pulsing	Moving to Layer
Warning	1	2016-07-30 18:50:26.36567	Calibration	Printing layer 1 from 30
Info	1	2016-07-30 18:50:26.365277	Projector	Projector on
Debug	1	2016-07-30 18:50:26.365066	Gcode	Transfering Data M280 P2 S10↵
Debug	1	2016-07-30 18:50:26.363901	Shutter	Shutter Close
Debug	1	2016-07-30 18:50:26.363679	Image	Clear screen
Info	1	2016-07-30 18:50:26.363572	Projector	Projector on
Info	1	2016-07-30 18:50:26.363374	Gcode	Position set to 0
Debug	1	2016-07-30 18:50:26.363089	Gcode	Transfering Data M650 D5 S5 R1↵G28↵G90↵
Warning	1	2016-07-30 18:50:26.3606	JSON	Skipping public/plates/0/info.json file. stat public/plates/0/info.json: no such file or directory
Info	1	2016-07-30 18:48:26.760888	Terminal	Data Received ok↵
Info	1	2016-07-30 18:48:26.75997	Terminal	Data Received X:144.00Y:0.00Z:0.00E:0.00 Count X: 144.00Y:0.00Z:0.00↵
Info	1	2016-07-30 18:48:26.759694	Terminal	Position Change 0
Debug	1	2016-07-30 18:48:26.752676	Gcode	Transfering Data M114↵
Info	1	2016-07-30 18:48:20.087158	Terminal	Data Received ok↵
Info	1	2016-07-30 18:48:20.086149	Terminal	Data Received ok↵
Debug	1	2016-07-30 18:48:20.044361	Gcode	Transfering Data G28↵G91↵
Info	1	2016-07-29 19:17:32.002829	Terminal	Data Received echo:SD init fail↵
Info	1	2016-07-29 19:17:28.705435	Terminal	Data Received echo: M301 P22.20 I1.08 D114.00↵
Info	1	2016-07-29 19:17:28.701736	Terminal	Data Received echo:PID settings:↵
Info	1	2016-07-29 19:17:28.700024	Terminal	Data Received echo: M206 X0.00 Y0.00 Z0.00↵
Info	1	2016-07-29 19:17:28.698034	Terminal	Data Received echo:Home offset (mm):↵
Info	1	2016-07-29 19:17:28.696234	Terminal	Data Received echo: M205 S0.00 T0.00 B20000 X40.00 Z0.40 E0.40↵
Info	1	2016-07-29 19:17:28.692607	Terminal	Data Received echo:Advanced variables: S=Min feedrate (mm/s), T=Min travel feedrate (mm/s), B=minimum segment time (ms), X=maximum XY jerk (mm/s), Z=maximum Z jerk (mm/s), E=maximum E jerk (mm/s)↵
Info	1	2016-07-29 19:17:28.675575	Terminal	Data Received echo: M204 S3000.00 T3000.00↵
Info	1	2016-07-29 19:17:28.673779	Terminal	Data Received echo:Acceleration: S=acceleration, T=retract acceleration↵
Info	1	2016-07-29 19:17:28.668302	Terminal	Data Received echo: M201 X4000 Y4000 Z4 E4↵
Info	1	2016-07-29 19:17:28.66632	Terminal	Data Received echo:Maximum Acceleration (mm/s2):↵
Info	1	2016-07-29 19:17:28.662558	Terminal	Data Received echo: M203 X600.00 Y600.00 Z8.00 E8.00↵
Info	1	2016-07-29 19:17:28.659144	Terminal	Data Received echo:Maximum feedrates (mm/s):↵
Info	1	2016-07-29 19:17:28.65714	Terminal	Data Received echo: M92 X36.36 Y36.36 Z640.00 E640.00↵
Info	1	2016-07-29 19:17:28.653484	Terminal	Data Received echo:Steps per unit:↵
Info	1	2016-07-29 19:17:28.651449	Terminal	Data Received echo:Hardcoded Default Settings Loaded↵
Info	1	2016-07-29 19:17:28.647847	Terminal	Data Received echo: Free Memory: 4014 PlannerBufferBytes: 1312↵
Info	1	2016-07-29 19:17:28.644182	Terminal	Data Received Compiled: Jul 29 2016↵
Info	1	2016-07-29 19:17:28.642262	Terminal	Data Received echo: Last Updated: Jul 29 2016 04:33:10 | Author: (none, default config)↵
Info	1	2016-07-29 19:17:28.636565	Terminal	Data Received Marlin 1.0.0↵
Info	1	2016-07-29 19:17:28.634728	Terminal	Data Received echo: External Reset↵
Info	1	2016-07-29 19:17:28.633339	Terminal	Data Received start↵
Debug	1	2016-07-29 19:17:27.745079	Gcode	Transfering Data M280 P2 S10↵
Info	1	2016-07-29 19:17:27.743898	Terminal	Terminal Reader Activated
Debug	1	2016-07-29 19:17:27.743667	Shutter	Shutter Close
Debug	1	2016-07-29 19:17:27.725639	Gcode	Transfering Data G90↵
Info	1	2016-07-29 19:17:27.701403	Hardware	Initializing build # 1107 - muve3d
Warning	1	2016-07-29 19:17:27.701249	JSON	Skipping db/custom-inputs.json file. stat db/custom-inputs.json: no such file or directory

[mUVe 3D Admin]

Bob,

It doesn't look like you're using our latest firmware, the nanoDLP software is waiting for the RAMPS system to respond that the motion was completed but it's not happening. If you download the latest running DLP firmware to you system you should be all set.

mUVe 3D Support

[Bob Houin]

Thanks for the help.  I downloaded and installed the latest Arduino IDE and redownloaded the firmware.  After reinstalling the firmware everything seems to be working fine now.  Just need to run a test cube and calibrate.

I thought that I had the latest firmware installed, however, I know that I used an older version of the IDE to install it as I already had it on my computer.  Not sure which was the issue but all seems to be good now.

Thanks again.

Bob

[mUVe 3D Admin]

Bob,

The change for the nanoDLP system was just a couple lines of code, but they were critical. It shouldn't matter which IDE version you use so long as it has the requisite libraries, etc. Basically if it compiles, the IDE is new enough for our needs. No reason to go get the latest version from the Arduino folks each time we release a firmware upgrade unless we state otherwise, or you want to. Most of those releases deal with bug fixes or new features/libraries. Since we're running a simple system we don't need most of the new stuff that's coming out.

mUVe 3D Support