My first Build - Voron 2.4 R2 RevD

[PFarm]

@NewGradRN Love how you routed the umbilical do you have STLs to share?

Edited February 15 by PFarm

[NewGradRN]

Absolutely, I’ll post it when I get home..

[mvdveer]

4 hours ago, NewGradRN said:

More pressing issue for me is that I tried to find info on how to attach the PFTE tube to the toolhead

Looks like you printed the Non-Ecas toolhead extruder. The PTFE tube just press fits into this.

Yours - No ECAS                                                     vs                      Mine - ECAS

                   

[NewGradRN]

I see, Thanks Mr. mvdveer. I will press fit to the one I have now so I can get it going. I'll build one with ECAS to replace it later if that is available as option for this printer.  Is there any specific length of PFTE that needs to go down? Thanks for the help again...

Here are the stls for the umbilical top mount... 

Voron 2.4 Umbilical top Mount.stl

Voron 2.4 Umbilical drill and cutout Templte.stl

Voron 2.4 Cable Clamp.stl

[mvdveer]

1 hour ago, NewGradRN said:

 Is there any specific length of PFTE that needs to go down?

No, just push it down till it meets resistance.

[mvdveer]

1 hour ago, NewGradRN said:

Thanks Mr. mvdveer.

No need for formalities, and always a pleasure

[NewGradRN]

Almost done then this...

 

Looked up in the forum and seems that few had the same issue but no posted solution yet. 

[claudermilk]

Does a restart clear it? Sometimes it does. If not, what do the logs say?

[NewGradRN]

Thanks, I found the device IDs and plugged them in to the printer.cfg. I uploaded the premade printer.cfg for the 2.4 RevD but can't fully use it because of the mods I made including the Beacon and placement of the endstops. I am trying to figure out what to do to fix subsequent errors. Finally, seems to be no more error and my the Voron is still alive and seems ready to run. I,m just too scared to press home key. Additionally, I don't think I have completely made a proper config for beacon because looking at their config at beacon documentation, they have much more info than they have on their quick start. They also have macros which I'm not quite sure how to insert in the printer.cfg. Could I possibly have a look at someone's config with beacon? thanks

Edited February 26 by NewGradRN
Added 1 image

[NewGradRN]

This is what is in my printer.cfg.. Is it safe.... Thanks..

 

 

Voron Printer Config 1.txt

[mvdveer]

I would start here before pushing any buttons. This is the recommended Voron Start up checks.

For beacon to work, you need the initial startup section and calibrate the probe. DO NOT HOME without doing this first.

Once they are all completed and "passed", then you can go ahead and home. 

If you are going to use the contact function of beacon, then move onto this section.

Let me know how you go

[Penatr8tor]

13 hours ago, NewGradRN said:

I,m just too scared to press home key.

Hahahaha I just did that last night.

And having errors when you first power up the machine is pretty normal.

My usual routine is to get the printer.cfg as close as I can get it then as the errors come in you make your changes, reboot and repeat until everything runs.

Here's something I did when I first built my 2.4 and it came in handy when I tested the steppers. When you do a STEPPER_BUZZ... you have to look to see if the motor rotates clockwise then back. And a line drawn with a sharpie can be a real help.

[NewGradRN]

I followed Voron startup 1) temp check: extruder get to set temp (not cal) and parts fan comes on. Bed temp get to set temp (not cal) and exhaust fan comes on. 2) Motor check: all motors movement check good. 

Next was endstop check and failed: y shows open while z and x shows activated. I put pressure on X and Z to activate them then check, they still shows activated and now also shows y as activated.

I have the beacon as the virtual Z endstop

          ## Z0    

               step_pin: PD4
               dir_pin: !PD3
               enable_pin: !PD7
                rotation_distance: 40
                gear_ratio: 80:16  
                 microsteps: 32
                 endstop_pin: probe:z_virtual_endstop
                #   Configure z homing to use beacon as a virtual endstop
                 homing_retract_dist: 0

[NewGradRN]

I also did not realize I have to do some software work on the Nitehawk so I was following the instruction then came with a problem in that there is no Raspberry pi option on the Klipper Klipper configuration menu.

[NewGradRN]

I made a mark like you did and did the test again, sure enough it was easier to determine the movement.. Thanks

[NewGradRN]

Figured it out, guess I have to work harder printer software installations. But still, the options on the instructions are different. For example, Communication interface: it want USB, there's two USB option USBSERIAL and USB to CAN bus Bridge. Which should I choose. ay yay yay

[NewGradRN]

Before I go any further with the Nitehawk instruction on software installation and mess up everything, DO I need to do this? I followed the LDO Voron 2.4 RevD instruction down the line and it did not mention anything about loading katapult or anything about uploading anything to the Nitehawk. It also seems that everything in the tool head is working except the Y endstop (open) will not trigger when pressed. this same for the the other two which is showing triggered when they are open and will not untrigger even when pressed. I unplug both z and x endstops from the MCB and they are still showing triggered. I put the "dir_pin: !PB11" to reverse but it just changed to won"t trigger... 

[Penatr8tor]

1 hour ago, NewGradRN said:

Which should I choose. ay yay yay

If you're connecting the nighthawk directly to your Pi with a USB cable then, USBSERIAL

If you have a USB to CAN adapter board with a CAN cable going to the toolhead and the USB going to the Pi then, USB to CAN

[Penatr8tor]

10 minutes ago, NewGradRN said:

Before I go any further with the Nitehawk instruction on software installation and mess up everything, DO I need to do this?

If you're already able to run all of the stuff on the hotend... Then no. That's generally a onetime process or maybe that's the way they handle firmware updates.

[NewGradRN]

So far so good except two endstop problems. 1) My Y-endstop is connected to the Nitehawk GPIO13-GND. and I can't figure out how to configure it in the Klipper. I read in one of the post here "Nighthawk-SB Toolboard" that The pin assignment just needed to be changed in the Klipper. SO I changed it to GPIO13 but no go... 2) Beacon is being used as Z and already reporting activated. So I am stuck before I can send this toolhead home... Still searching.....

[mvdveer]

45 minutes ago, NewGradRN said:

So far so good except two endstop problems. 1) My Y-endstop is connected to the Nitehawk GPIO13-GND. and I can't figure out how to configure it in the Klipper. I read in one of the post here "Nighthawk-SB Toolboard" that The pin assignment just needed to be changed in the Klipper. SO I changed it to GPIO13 but no go... 2) Beacon is being used as Z and already reporting activated. So I am stuck before I can send this toolhead home... Still searching.....

pin should be nhk:gpio13 in the relevant section:

The reason: Your Nighthawk mcu is defined as [mcu nhk]. Klipper needs to know it is not connected to the main mcu which is just defined as [mcu]

[mvdveer]

1 hour ago, NewGradRN said:

Beacon is being used as Z and already reporting activated.

That is correct. Now you need to calibrate it:

 

 

[NewGradRN]

Thank you, endstop problem has been solved. Homed x and y without problem. Lowered and centered the nozzle and conducted manual paper calibration as per Beacon instruction. I think this build is about to come into conclusion thanks to everyone's help. Perfectly, my Clicky-Clack door just arrived so I'll be installing it once everything is done 

[NewGradRN]

 

7:52 PM

Might have spoken too soon about being done ha ha. Sent bed mesh calibrate command and it send this error "Move out of range: 20.000 -5.000 2.000 [0.000]"

 

[mvdveer]

2 hours ago, NewGradRN said:

7:52 PM

Might have spoken too soon about being done ha ha. Sent bed mesh calibrate command and it send this error "Move out of range: 20.000 -5.000 2.000 [0.000]"

In your [stepper_z] section set your position min to -10 to start with.

position_min: -10

Once you got everything tuned in, you can change this, but the error shows your position min is outside of the range of movement.