I tracked down a general bed-heating problem to a power-supply issue. I've been running my A8 off an ATX power supply. I ran the printer off the 8-pin ATX12V connector (and a Raspberry Pi off the 5VSB output, but that isn't relevant here). With the stock bed, all was well, but I think the connector was overloaded when I upgraded to a 200W bed. On an attempted test print today, I saw that theby salfter - Firmware - Marlin
I'm trying to enable bed PID in Marlin 2.0. I have PIDTEMPBED enabled in Configuration.h, and autotune yielded these constants: #define DEFAULT_bedKp 206.42 #define DEFAULT_bedKi 19.09 #define DEFAULT_bedKd 557.90 However, when I dial in a bed temperature, the heater never switches on. I also have PIDTEMP, PID_EDIT_MENU, and PID_AUTOTUNE_MENU defined, but this only provides access tby salfter - Firmware - Marlin
v0.2 allows TMC2130 SPI to be configured in point-to-point mode (which Marlin currently requires) or in daisy-chain mode. Five jumpers next to the Teensy determine whether one or six CS lines are needed, while the 10 3-pin jumpers next to the stepper drivers determine whether SDI and SDO are connected in parallel or daisy-chained. If you're using "dumb" drivers (A4988, DRV8825, etc.), all of thby salfter - Developers
Quotedc42 Quotesalfter You can't configure TMC2130s without it. Each SPI slave needs its own CS line. You can use a common CS for all the stepper drivers if you daisy chain the SPI signals. This means that you have to write to/read from all the drivers in every transaction. Marlin doesn't support that AFAICT, except for some not-commonly-used hardware that doesn't work any other way. I took aby salfter - Developers
Getting all those connections out from under the Teensy was a bit of a challenge, leading to a somewhat large (150x120mm) board. I started out by laying out subsections: power and heaters, stepper drivers, thermistor inputs, LCD connector, etc. I rearranged pinout usage extensively on the Teensy to get like signals (that needed to be routed together) as close as possible. While there is a chunby salfter - Developers
Quotefrankvdh Quotesalfter Is there enough I/O on a Teensy 3.1 to drive even a single-extruder configuration? Each extruder needs three digital outputs (step, direction, chip select), a PWM output (heater), and an analog input (thermistor). Axis steppers need three digital outputs each. Do you really need a Chip Select on every stepper? So long as you aren't actually sending step pulses, notby salfter - Developers
Quoteorbitalair How is this coming? Doing PCB layout, working in sections. I have a power-and-heaters section with ridiculously fat traces, multiple stepper sections that are all alike (except for three connectors on Z to allow single, parallel, or series hookup), etc. I'm thinking I'll rearrange the signals coming out of the Teensy to group like signals together for easier routing: all SPI siby salfter - Developers
I started work on this a little while ago, aiming to produce a modular 3D printer board with something faster than an Arduino Due: https://gitlab.com/salfter/TeensyPrinter There's just enough I/O to handle three axes, three extruders, four heaters, five thermistors (bed, 3 hotends, and an enclosure), and a few other things. It borrows the emergency-stop feature from RAMPS-FD and extends it toby salfter - Developers
QuoteAntscran I know development has ceased on the RAMPS+FD v2, but can see the Gerber files are available, was this every built and tested? I had Elecrow make some boards from those files a few months ago. I just recently got the board completed and tested. It's not yet in a printer (I'm building a Hypercube 300), but I've verified that the various inputs and outputs do what they're supposedby salfter - Controllers