Lemonzap
About
- Username
- Lemonzap
- Joined
- Visits
- 10
- Last Active
- Roles
- Member
Comments
-
Eagerly trying to do this. Any help you can provide would be appreciated. Hope everything is going well.
-
Thank you for the help. The color changing and resizing is going quite well. One snag I'm having though is I can't seem to nail down where the color of the text on the temperature graph is set. I'm trying to change the background to something close …
-
I got it working. It turned out I was using something else called yarn from cmdtest. I removed that and found and installed the right kind of yarn. Now I was able to successfully change the colors in the touchscreen interface. I don't know much abou…
-
I still can't get it working. I updated node like you suggested and that got me past the error I was having. But now running gulp tells me it can't find node-sass. I've tried researching what to do about that and it seems like my best bet is to rein…
-
I just realized theres actually an error when I run yarn install. It says npmlog@6.0.0: The engine "node" is incompatible with this module. Expected version "^12.13.0 | ^14.15.0 || >=16". Got "10.24.0" Here's a screenshot of me running yarn inst…
-
I did run yarn install first. When I then run gulp I get "cannot find module 'gulp-sass'"
-
I have not increased the bit rate from 1000. Is there a bit rate you would recommend? 2000? 10000?
-
I was able to successfully install the 32 but armhf version.
-
The first move is always the homing action and it's during that homing action that it will crash because it will move the wrong direction. For Z-Min we have an inductive sensor on our carriage and Z-Max we have yet to implement since last time we tr…
-
Yes it does. 5 zip files and a readme. I did do the backup on windows and am trying to restore the backup on a new linux install. Could the operating system change be causing a problem?
-
I managed to stop it from doing the weird measurements every other time. I ended up commenting this if statement out of the runBedLeveling() function // if (!measureAutolevelPlane(plane)) { // Com::printErrorFLN( // …
-
I commented out this line "Printer::buildTransformationMatrix(plane);" and it started working better but it's still behaving odd. On repetitions every other time it goes to Y=304.8 rather than Y=0. Here's the log from what I just ran. 12:33:46.274: …
-
I'm not quite understanding what you're trying to say. I think maybe I didn't explain what's going on very well. I've drawn this diagram to help visualize the problem. The green arrows are the printer moving how I expect it to. It measures p0, p1, a…
-
So using that exact code I posted yielded unexpected results. The carriage crashed into the back wall because it moves the wrong direction for the last measurement point and I have no idea why. First it measures the front left corner, then moves to …
-
Ya those variables are the xmax/ymax and xmin/ymin. Trying to get as close to the screws as possible. I'll let you know how it works.
-
Alright, this is the code I've written then. Notice any problems? //move to h1 Printer::moveTo(EEPROM::zProbeX1(), EEPROM::zProbeY1(), IGNORE_COORDINATE, IGNORE_COORDINATE, EEPROM::zProbeXYSpeed()); //probe h1 float h1 = Printer::…
-
So would I replace the code block in your post with this? How do I tell it where to do the ZProbing? float h1 = Printer::runZProbe(true, true, Z_PROBE_REPETITIONS, true); float h2 = Printer::runZProbe(true, true, Z_PROBE_REPETITIONS, true); float h3…
-
As you can see here. After 10 leveling repetitions it shows a and b as zero but it clearly isn't level. Sometimes it does a spectacular job leveling but sometimes it gets into this loop where two pairs of values are level but not each pair to each o…
-
We've been continuing to work on this and we've got the 4 screw leveling working pretty good at this point with only one major problem. It does a good job leveling the bed most of the time but sometimes it gets stuck when the front edge is level and…
-
Why does it only make sense for direct extruders? What's wrong with bowden here?
-
So I tried my suggested change and it seems to be working now. It is making it more level rather than worse. However it stops short of the level I can usually achieve manually. I found where it was breaking out of the for loop early for reaching suf…
-
I did what you suggested and got this readout. 18:37:24.120 : Z-probe:9.249 X:50.00 Y:50.00 18:38:11.961 : Z-probe:6.865 X:50.00 Y:250.00 18:39:06.960 : Z-probe:10.036 X:250.00 Y:50.00 18:39:56.908 : Z-probe:7.909 X:250.00 Y:250.00 18:39:56.908…
-
I've been able to confirm the issue. I ran it twice in a row with no other changes and got these readouts in the log. 15:58:40.216 : Info:Autoleveling disabled 15:59:42.087 : Z-probe:9.566 X:50.00 Y:50.00 16:00:34.559 : Z-probe:9.175 X:50.00 Y:250.0…
-
Unfortunately I double and triple checked that they were using the same z invert settings. I'll do another test later and take a video to show how it's moving. In the meantime, I was reading through the leveling code but was having a hard time …
-
ah I got it. I had to add 3 of the z motor a second time in the features tab like you say. The code appears to be working now. When I send a g32 command it goes around and measures points in a 3x3 grid then begins adjusting the z motors, however I t…
-
I tried compiling but it seems I haven't defined my Motor Drivers properly since it's throwing me the "You need to define 3 motors for 4 screw motorized bed correction" error which used to be the "You need to define 2 motors for motorized bed correc…
-
I've begun setting up the system in the firmware configurator and I wanted to check back here to make sure what I'm assuming is correct so I don't mess anything up. We're using z motor mirroring as shown in this picture https://imgur.com/a/sM014fY. …
-
it's funny you say that because it already is 127 byte. Communication timeout is at 3 seconds. I have logging enabled but don't currently have a log saved with this issue in it so I'll post it here when it happens again. Thanks for all the help.
-
As for the checksum errors I get that I now believe are unrelated to my initial question. I just captured this screenshot that portrays what I see every so often. https://imgur.com/gSe3Cpz
-
alright. how is this code referenced? Do I need to change anything there or should I be able to replace this section of code in my firmware and reupload then run it? After enabling motorized correction of course.