Talk:Repic

From RepRap
Revision as of 03:57, 5 January 2012 by KalleP (talk | contribs) (Full speed ahead: new section)
Jump to: navigation, search

Regarding Firmware, you might want to have a look into Teacup_Firmware. Teacup is all plain C, compiles without Arduino libraries and has a plentitude of configuration options already. And it's compatible with official FiveD, of course. Traumflug 10:39, 5 March 2011 (UTC)

Thanks Traumflug, I'll check it out. I probably won't start working on the next version of Repic until Microchip come out with a 40-pin DIP PIC24F chip, but when they do that sounds like it'll be perfect for getting the firmware to run off USB memstick. Myndale 10:30, 7 March 2011 (UTC)

Full speed ahead

I love the idea of a through hole budget set of electronics, I'm also a PIC fan. I also love any ideas on reducing the cost of US$12/14 stepper boards with just a US$2/3 IC on them. The retail pricing is appropriate but there should be some way to get a hobby friendly pricing as well.

The other cheap mass produceable board (Melzi) has all the parts on the board and it adds in a option for a cooling fan that some people use, it could be for the extruder, heatsinks, cabinet heater or some other output, I believe one transistor to drive an optional feature will allow for quite a bit of experimentation. Also any spare pins still need to come out on a header to allow max flexibility.

A one wire serial LCD interface would be nice, it seems the 'g-codes' support debug and status messages, I suppose someone has done this already.

I also look forward to the free C compiler version that can integrate the G-code interpreter in the PIC.

Having a USB memory stick interface makes it more universal, memory cards come in so many flavours but USB is only one. Do you plan to allow both USB host and slave connected together or just one at a time?

Perhaps it is time soon to come up with a standard way to store the basic configuration parameters in a .INI file or something, not sure if this is the case yet but from reading is still seems that the numbers are standardised but they are not stored in any common form. A default set as RepRap.INI and one with the same filename as the G-codes like MotorMount1.INI for special parameters, possibly offering relative adjustments in % as well as absolute figures if you know which machine it will be printed on. KalleP 07:57, 5 January 2012 (UTC)