I think it's what you had there. But your pin numbers are all non-standard, so it can be confusing. You have my permission to use my pic. The board image came from Traumflug's Gen7 1.3.1 wiki. Check the the license there, too.by phord - Next Wave Electronics Working Group
Quoteterramir Sometimes you just got to do it yourself We are all here doing it ourselves. I appreciate the 'please', but your written tone sounds a little demanding or entitled. Maybe that's just my interpretation, though. I had to figure this connector out this weekend, also. See if this image helps clear it up for you.by phord - Next Wave Electronics Working Group
Cool. But the merge isn't clean yet. I'm working on it, and I got it to build now. But it won't drive my motors. I think there's an endstop config getting in the way. Haven't had time to dig that far yet.by phord - Next Wave Electronics Working Group
QuoteTraumflug Now I'm scratching my head what might be a proper solution. If I have the PSU on standby and pull the 220V plug, the standby LED takes several seconds to go dark. So, the capacitor flattening 5V Standby seems to be more oversized than undersized. Hmm. Buying a more modern PSU would solve the problem for me, but not for anybody else. This is what I did. I didn't realize my resetsby phord - Next Wave Electronics Working Group
Same problem here. The line that sets the BED temperature sensor as an input is where mine reboots. The boot code reports it was a brown-out reset. This suggests a short somewhere, but Teacup works fine on my board. Maybe that we shouldn't be setting that sensor pin up as an input. The specific trigger that causes the brown-out appears to be enabling a timer interrupt. I don't know enough abby phord - Next Wave Electronics Working Group
Thanks again for the code. But there's a typo around your HEATER_BED_PIN droftarts Wrote: > #define HEATER_0_PIN 4 > #define HEATER_1_PIN -1 > #define HEATER_2_PIN -1 > #define HEATER_BED_PIN I think you want a -1 there. In my case, I wanted the HEATER_BED_PIN active, so I set it to the normal value, which is 3. #define HEATER_BED_PINby phord - Next Wave Electronics Working Group
I've merged droftarts' config into pins.h now, but I haven't tested it beyond 'make'. You can pull my changes from github You might also want some of other changes on that 'phord' branch.by phord - Next Wave Electronics Working Group
Quotedroftarts 1. Temperature reporting seems to be unstable - it can suddenly jump up or down 10C. This may be due to crosstalk from the heater and/or motor wiring when they turn off and on - I was experiencing something similar with my Gen6. I have seen this, too, but mostly at the low end of the temperature range. I start out at "room temperature", but as soon as I apply power to the heater,by phord - Next Wave Electronics Working Group
Update: I ordered some IRF2804 MOSFETS from Mouser before you sent me new ones as well. I think the specs are similar to the IRF3803 you gave me, but maybe a little more generous. My temporary VCR-motor-controller-switch (some NEC transistor) was working without overheating, but I also had a huge heatsink and a fan on it. Also it limited my bed current so that my temp only reached about 70C.by phord - Next Wave Electronics Working Group
I'm still trying out different host software and slicers, and not too familiar with any of them yet. But I had so many problems with the ABSOLUTE_E setting being wrong for the slicer, so I implemented M82/M83 software configuration. I noticed these being generated by RepetierHost. I think it needs a little cleanup (tabs/spaces), and it's not based directly on master, but this should cherry-picby phord - Firmware - experimental, borrowed, and future
Are you sure it fixed the problem? Did you run the same gcode file again and it worked ok? I've seen similar behavior when my firmware thinks my extruder needs to move a lot faster than my x/y axes, for example. Like the extruder is in "absolute" coordinates mode, but the gcode is using "relative", so you send a "G1 E0" -- meaning, "don't extrude" -- but the extruder thinks it has to rewind alby phord - Repetier
I have calibrated my thermistor tables by reading the R2 values carefully and generating new custom tables for both the extruder and the heated bed. When I turn on the 12v power I can read both thermistors and they both show reasonable and similar values (about 22C). Looks good so far! Then I turn on the heater for the extruder. Immediately the temperature reading from both thermistors dropsby phord - Next Wave Electronics Working Group
QuoteTraumflug To get on/off behaviour, you can turn on BANG_BANG in Teacup's config.h and set BANG_BANG_ON to 255 and BANG_BANG_OFF to 0. I tried this but I didn't think I needed to change the ON/OFF values from their "defaults"; I thought they were hysteresis marks (inputs), but now I see they might be the ON and OFF output values. I'll give it a shot later to see if it helps. QuoteTraumflby phord - Next Wave Electronics Working Group
Traumflug Wrote: QuoteTraumflug It's right, PWM heats up the MOSFET more than occasional switching. One solution could be to reduce the PWM frequency, which currently defaults to the maximum of 65 kHz in Teacup. This can be divided by 2, 4, 8, 16 easily. Some people fear going into the audible range makes the MOSFET switching hearable. I didn't test this so far. I expect it could be divided byby phord - Next Wave Electronics Working Group