Pin 'VF4' is not a valid pin name on mcu 'mcu' & pin PB14 is reserved for spi2
getting the error since upgrading to 2.1. Same Pins are working fine on 2.0
Using the BTT Manta M8P 2.0 with the BTT SB2240 1.0
57 Replies
upload your debug.zip please
Can't believe the 4-pin fans are still wrong in that m8p-20 definition. sigh. Fix on the way. VF4 is not a pin though, never has been, never will be. It's used in the m8p diagram to indicate the voltage from the fan voltage selector. It's not a gpio. That's a mistake in the M8P RatOS definition.
and about the PB14/15 on the SB2240? I have the same pins running on 2.0.1.
Looking into it right now, more pin goofs i'm sure
I also get the error "tmc2240 extruder: spi pins must be on same mcu" which i fixed with:
[tmc2240 extruder]
spi_software_sclk_pin: toolboard_t0:adxl345_clk
spi_software_mosi_pin: toolboard_t0:adxl345_mosi
spi_software_miso_pin: toolboard_t0:adxl345_miso
will check that out too
Hmm this is strange
You said this worked on the in 2.0 ?
Yes. let me change the sd card on the printer and i can send you the files
No need, it's in the manual, so i would assume you're right
But the chip used on SB2240 has that pin reserved for hardware spi
Which is confusing me right now
Ah!
@Hopfenschorsch https://github.com/Klipper3d/klipper/commit/434770eaf9d382cccba203a3475ace2dc0653d7b
Klipper broke that pin
GitHub
stm32: Add new spi2 on stm32g0 chips (#6569) · Klipper3d/klipper@4...
Signed-off-by: Donald A. Cupp Jr
R.I.P 4-pin fans on SB2240
I'm guessing it's not that common to use the 4-pin port on the SB2240 since nobody has called that out yet?
I think so.
I´m on Klipper Version v0.12.0-208-g49c0ad63
you have your fan configured as a 4-pin fan on a 2-pin header in the configurator, you could just hook it up that way. But you woulnd't get the tach signal.
Yeah they broke it 2 months ago
almost 3 months actually
I guess you can argue that the board design is flawed, they shouldn't be using SPI pins for the 4-pin fan.
eitherway, to use your 4-pin fan, connect the PWM to the negative terminal of the 2-pin hotend fan port and remove your override.
then it should "just work"
Leave the power wires on the 4-pin header
Looking into the extruder issue now
I checked on the 2.0 SD card and i have the newest Version of Klipper installed and it doesn´t give me the same error.
This is the config I use on RatOS 2.0.2
which version specifically?
v0.12.0-208-g49c0ad63
Same Version as on 2.1 RC1
Now i'm really confused
are you sure the "toolboard.cfg" file was included in printer.cfg?
And not overriden later or something
Because PB14 and PB15 shouldn't work for anything but SPI
@Hopfenschorsch can i see your printer.cfg from 2.0?
[include Custom/Fans/Hotend_Lüfter.cfg]
is included afterwards.
What's in that?nothing crucial
This doesn't make sense
Those pins are reserved by klipper on initialization of the toolboard
Have pushed the fix for both the VF4 pin goof and the toolboard spi pins for the extruder. The configurator is compiling.
Will try it when its done
But why does PF14/15 work on 2.0.2 and not on 2.1? What did i change to make it work?
PF14/15 are different pins. PB14/15 should not work.
There's nothing you can change to make them work
You would have to modify klipper
meant PB14/15 was a spelling mistake. Is it maybe because i run an older Version of Klipper on the Board it self? Version: v0.12.0-86-gdaf875e6. But then it shoul work on 2.1 because it is the same Hardware
Wait.. That's not true, they're only reserved if you configure a device that uses SPI on the particular MCU
gimme a sec
Yes that changes things
the firmware would have to be compiled within the last 3 months for the error to happen
Yeah except you flashed it with the newest klipper when installing 2.1
So yes it should indeed break on 2.0 now as well, unless you don't have an SPI device on the toolboard configured, which you don't
(you don't have the ADXL345 configured)
haven´t flashed the toolhead for 2.1. I can change the two SD card with out changing sth in the software/reflashing
Hmm.. actually you do.
[adxl345 toolboard]
cs_pin: toolboard:adxl345_cs_pin
spi_software_sclk_pin: toolboard: adxl345_clk
spi_software_mosi_pin: toolboard: adxl345_mosi
spi_software_miso_pin: toolboard: adxl345_miso
axes_map: z,-y,x
The toolboard needs a different chip name to work in 2.1
it uses toolboard_t0 or toolboard_t1 instead of toolboard
Ah... Canbus
Will go with USB when i change to the new SB2209 USB
The one you have already works with USB
Pop a 3DO usb-c cable in your machine and you're off to the races
Physical not really because the motor of the Galileo 2 is to close to the 90 deg USB C
But you'd still have problems with PB14/PB15 😂... God damn i'm confused about how it works on 2.0
Aah i see
I think i have to stay on 2.0.2 or buy a new Board.
or hope you find the Problem
Btw, the modifications you're making to RatOS.cfg will be overwritten. That file is managed by the configurator.
hence this:
WARNING. THIS FILE IS GENERATED BY THE RATOS CONFIGURATOR.
CHANGES YOU MAKE HERE WILL BE OVERWRITTEN. KEEP YOUR CHANGES IN PRINTER.CFG.
Which will kill your canbus
So you'd have to make a copy of it and use that instead
I see that you're using a different casing, so maybe that's enough (but then you need to manually port the updates from RatOS.cfg when it changes).
Helge said that to me in the morning
unfortunately it's one of the consequences of the config generation in 2.1
Oooh
that would be fine with me changing it manual to use CAN.
I found the difference that makes it work on 2.0
you're using different spi bus for the adxl configuration in 2.0
No.. i'm just blind
I confused it with the controlboard adxl
:facepalm:
on 2.1 I use Beacon for the adxl
yeah but the toolboard adxl is still configured
The option you pick in the hardware configurator determines what get's put into [resonance_tester]
all adxl's are still configured (so you can access them with the realtime analysis tool, or swap between them with macros)
ah okay
sensor_type:MAX31865
The plot thickens
Solution
You're missing this from your 2.0 config:
It's attempting to use spi2
That's why you're getting the error
Jesus christ that almost killed me 😂
Perfekt. Thank you. Are you planning to support MAX31865 in the Configurator?
I'm considering it, but so far the position is that it doesn't make much sense unless you're using a PT100
Will try it as soon as possible. chainging the SD card again
And you can always configure it manually (just pick a different thermistor from PT1000).
i find it useful because u could use the normal Port for a sensor to check the temperature of the Toolhead or sth.
true, or you could use the MAX31685 for that 😄
Dindn´t know you could use the MAX with sth diffrent then PT100/0
But you're right that it can be useful for things, however RatOS exists to make choices for users to simplify the whole setup process, if i added support for everything you'd just have vanilla klipper with a confusing interface 😂
Everything is balancing act, but i will keep your usecase for the MAX in mind.
Maybe it makes sense.
No you would still need a PT1000 but they come in the same form factors as other thermistors
So it's just a matter of putting a PT1000 in whatever else you want to measure
which imo, should probably be the standard.
It's just better
and they're not that expensive anymore
didn´t had a pt1000 laying around
@miklschmidt Updated RatOS, the Configurator, made a New RatOS.cfg, added this and it is working now.