Anyone got a printer.cfg for...

[MichaelOToole]

Printer Model

Voron 2.4

Extruder Type

Clockwork 2

Cooling Type

Stealthburner

Reference: I'm building from LDO Kit, using an Octopus V1.1 ... will add Stealthburner, Tap, CANBus later...

I've connected all the electronics adding thermistors to prevent errors (I have not connected the Bed or Hotend yet).
Fired up Firefox and connected to the printer (using Mainsail)... so far everything looks good...
As I'm aiming for sensor-less homing for X and Y I added the diag jumpers for X & Y on J16 & J17...

For the next step, I'm looking to compare my printer.cfg file for errors or omissions, I have found some but there are differences causing me some confusion. Has anyone got a working printer.cfg file for a similar setup I could compare?

I've configured X & Y in UART mode but what about the rest, I'm guessing everything in UART mode Yes?

Any help appreciated... Mike

 

[viddi87]

You can check out my config, i have canbus, tap and sensorless xy homing

GitHub - viddi87/V2.3223

Contribute to viddi87/V2.3223 development by creating an account on GitHub.

github.com

 

[MichaelOToole]

Many many thanks, much appreciated Viddi

My X and Y were almost identical with one line difference, I must be on on the right track, but my Z is quite different, I best check those setting again.
Just to confirm, when using Tap we use (endstop_pin: tmc2209_stepper_y:virtual_endstop and diag) ?
Mike

 

[viddi87]

When using TAP u have endstop_pin: probe:z_virtual_endstop in stepper_z

Voron-Tap/config/tap_klipper_instructions.md at main · VoronDesign/Voron-Tap

Contribute to VoronDesign/Voron-Tap development by creating an account on GitHub.

github.com

 

[NoGuru]

My 2.4 config backups in case you want to review https://github.com/NoGuru2/VoronV2.4

 

[MichaelOToole]

Thanks NoGuru...

 

[MichaelOToole]

I have followed a lot of tutorials, stumbled through countless pages, programmed the canbus boards many times but after 20 hours... finally... got it working... No errors and no smoke....
Now the fun bit begins... do I have things connected correctly? That will have to wait for the morning I'm shattered




Thanks

 

[MichaelOToole]

A question re ifconfig

1: When running ifconfig, it reports can0 has txqueuelen of 10 but I set txqueuelen to 1024 in /etc/network/interfaces.d/can0

pi@mainsailos:~ $ ip -s -d link show can0
3: can0: <NOARP,UP,LOWER_UP,ECHO> mtu 16 qdisc pfifo_fast state UP mode DEFAULT group default qlen 10
    link/can  promiscuity 0 minmtu 0 maxmtu 0 
    can state ERROR-ACTIVE restart-ms 0 
      bitrate 1000000 sample-point 0.750 
      tq 62 prop-seg 5 phase-seg1 6 phase-seg2 4 sjw 1
      gs_usb: tseg1 1..16 tseg2 1..8 sjw 1..4 brp 1..1024 brp-inc 1
      clock 64000000 
      re-started bus-errors arbit-lost error-warn error-pass bus-off
      0          0          0          0          0          0         numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535 
    RX: bytes  packets  errors  dropped missed  mcast   
    656156     87240    0       0       0       0       
    TX: bytes  packets  errors  dropped carrier collsns 
    34855      5839     0       0       0       0

File: (/etc/network/interfaces.d/can0)

allow-hotplug can0
auto can0
iface can0 can static
bitrate 1000000
#up ifconfig $IFACE txqueuelen 1024 # suggested code... 
up ip link set can0 txqueuelen 1024  # tried this as txqueuelen was reported as 10 and not 1024 but no difference...

A fix is to set it manually: sudo ip link set can0 txqueuelen 1024.

 

[viddi87]

This is my can config:

allow-hotplug can0
iface can0 can static
    bitrate 1000000
    up ifconfig $IFACE txqueuelen 1000

and ifconfig reports:

can0: <NOARP,UP,LOWER_UP,ECHO> mtu 16 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
    link/can  promiscuity 0 minmtu 0 maxmtu 0
    can state ERROR-ACTIVE restart-ms 0
          bitrate 1000000 sample-point 0.750
          tq 62 prop-seg 5 phase-seg1 6 phase-seg2 4 sjw 1
          gs_usb: tseg1 1..16 tseg2 1..8 sjw 1..4 brp 1..1024 brp-inc 1
          clock 48000000
          re-started bus-errors arbit-lost error-warn error-pass bus-off
          0          0          0          0          0          0         numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535
    RX: bytes  packets  errors  dropped missed  mcast
    1003146    161570   0       0       0       0
    TX: bytes  packets  errors  dropped carrier collsns
    1326510    190611   0       0       0       0

 

[MichaelOToole]

@viddi87, your code is exactly the same as my first attempt except for transmit queue length, I used 1024... but, no matter what I enter for txqueuelen, it reports 10...
Just tried your exact code again and it's still reports txqueuelen as 10 not 1000...

After more searching, it appears this is a know issue... didn't find a solution yet, even tried reinstalling net tools...
For the moment, my fix is to run

sudo ip link set can0 txqueuelen 1024

as it works, resulting in...

3: can0: <NOARP,UP,LOWER_UP,ECHO> mtu 16 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1024
    link/can  promiscuity 0 minmtu 0 maxmtu 0
    can state ERROR-ACTIVE restart-ms 0
      bitrate 1000000 sample-point 0.750
      tq 62 prop-seg 5 phase-seg1 6 phase-seg2 4 sjw 1
      gs_usb: tseg1 1..16 tseg2 1..8 sjw 1..4 brp 1..1024 brp-inc 1
      clock 64000000
      re-started bus-errors arbit-lost error-warn error-pass bus-off
      0          0          0          0          0          0         numtxqueues 1 numrxqueues 1 gso_max_size 65536 gso_max_segs 65535
    RX: bytes  packets  errors  dropped missed  mcast
    14721      1960     0       0       0       0
    TX: bytes  packets  errors  dropped carrier collsns
    1878       342

After more reading and testing...
I tried setting to 100 and that worked once but next boot it defaulted back to 10... a few boots later I noticed it was back to 100
Also noticed the clock is 64000000 in mine and 48000000 in your but as other peoples code have clocks of 64000000 and with len 1024 and they work, it's probably not an issue

Anything to avoid the next part of the setup

Something must have bee updated...
I set qlen to 1024 and it's not reporting 1024... I guess this issue is now solved...

Apologies for I should posted about in a separate post...