![]() ![]() I once used a 10k NTC with unknown Beta thermistor in a setup that required a 10k NTC 3950B thermistor - the result was that at room temperature it was accurate, however when the display read 50C it was actually close to 100C -> very dangerous.Īlso remember that a laser/IR thermometer is not accurate on 3d printers (for various reasons already explained a lot). Most of the temperature sensors that are configured in the firmware, are 100k NTC thermistors - this simply means that at 25C they are 100kOhm resistors, yet the differences come in with the graphs/tables for each. So while it may appear to have correct temperatures now, that might not actually be the case at higher temperatures. The 97 is for the firmware to generate a reference table from custom settings (like this reference resistor). Usually this resistor is 4.7K, however the Melzi uses a 10K resistor. The Di3 with a stock Melzi mainboard have a few changes compared to other boards, specific to the Voltage divider's reference resistor. The sensor type you changed should match the actual sensor type and setup the printer uses. I'll continue to test.ġ4:14:41.068 : Printed filament:0.00m Printing time:0 days 0 hours 0 minġ4:16:39.995 : Printed filament:0.00m Printing time:0 days 0 hours 0 min I'm not sure how critical these are, because I seem to have basic functionality. So Repetier Host now connects, but there are some errors at the start, see below for a dump. Perhaps I have a flakey USB cable that is generating some errors at 115K? I really don't know what this is about, because the 115200 coms in my test app seem to work fine. I changed the 16mhz upload speed to 57600 and the upload worked straight away. I noticed that the 'upload.speed' setting for the 16mhz board was 115200, while the 8mhz board was 57600. I examined the boards.txt file in the board support folders for the sanguino. Thanks in advance for any advice you can give me.įor those of you who can't wait to hear the next installment in my saga: However, all my attempts to compile the 0.91 code for this board have also failed, and you seem to know what you're doing. At this point I'm not really concerned about getting the latest and greatest code, just something that works like my old board did. I added support for the board by copying the Sanguino folder from the Repetier GitHub repo.Īny idea what I'm doing wrong? Ultimately, all I'm trying to do is get a replacement Mezi board up and running in my Maker Select (Duplicator i3). The board selected in the IDE is "Melzi 1284p 16mhz". I'm using Arduino IDE 1.0.6 (because of all the posts I saw about only using this version). text will not fit in region textĭ:/programs/arduino/hardware/tools/avr/bin/./lib/gcc/avr/4.3.2/././././avr/bin/ld.exe: region text overflowed by 4520 bytes Are there any logs outputted anywhere or can I somehow enable them? Or I wouldn't even mind getting you a snapshot of the application when it is in it's broken state if there is a way of doing it.ġ6:18:29.I'm trying to compile your version and I'm getting an error indicating it's too big:ĭ:/programs/arduino/hardware/tools/avr/bin/./lib/gcc/avr/4.3.2/././././avr/bin/ld.exe: section. net, I would love to say send me the solution and let me debug it, but I get it. net, and being a software engineer that works primarily with C# and. I believe I read the application is written in. I also realized that I am running 2 monitors at 1920x1080 and one at 1920x1200, I tried disconnecting the 1920x1200 thinking maybe the 1 off resolution was the issue, but it wasn't, it would still freeze. If it helps, I am running an Intel Core i7-6700K, 16GB ram, and a GeForce GTX 970, I can get more detailed specs later if desired. And if it freezes while not maximized it behaves the same, just not maximized. Here it is in the state when it freezes, unfortunately you don't see the splash screen in this screenshot, but it is on my main display and always in front. Multiple monitors has to have something to do with it, maybe some combination of drivers or something? I can open and close it on my main display all day long and it works fine, but if I put it on another monitor and close it even once, it breaks. ![]() FYI, i have a WIN10 3 Monitor System working as expected so the 3 Monitors seem to be no problem
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |