Show all posts by user
Page 1 of 1 Pages: 1
Results 1 — 9 of 9
My only guess now would be that the software was made with the FTDI controller in mind and is having problems with the CH340. But the way it's behaving now is very similar to how it was behaving when i was having problems with the firmware upload, that time it turned out to be a Baud issue.
by
scrub
-
General
QuoteTraumflug
Having Debug turned on just shows what happens anyways.
There should be lines starting with RECV, too. Not having them indicates communications not working. Baud rate mismatch, Arduino unpowered, such stuff. Also make sure CPU Clock Rate (Configtool -> Board -> CPU) matches your Arduino.
Checked the clock and it's 16meg, same as in config, in fact 16meg it the only available
by
scrub
-
General
QuoteTraumflug
Quotescrub
does not have these menu options, rather in the settings tab it has "macros", "options", "slicing settings" and "debug communications". In options i can't find anything resembling "debug g-code".
Take "debug communications" ... and edit the wiki to reflect this change in Pronterface wording.
Quotescrub
Maybe i'm not waiting long enough for my arduino nano to connect? H
by
scrub
-
General
Looks like not all of my problems are solved. I'm a newbie when it comes to 3D printer software and i don't know what works best.
After successfully uploading the teacup firmware i tried testing it out with Pronterface, mainly because it was mentioned in the teacup wiki. The problem i'm having is that Pronterface does not get any response from my arduino nano.
I've read that with pronterface you
by
scrub
-
General
I've recently decided to retry uploading Teacup firmware to my arduino nano. One problem that previously stopped me dead in the tracks was that after i build the file and want to upload it it just won't do it. Stk500v2 says timeout and "arduino" as my programmer says:
avrdude.exe: stk500_recv(): programmer is not responding
avrdude.exe: stk500_getsync() attempt 10 of 10: not in sync: resp=0x81
W
by
scrub
-
General
QuoteTraumflug
QuotescrubFrom what i know arduino works by the bootloader taking data and saving it into EEPROM and then execute the commands that are in the EEPROM, but here i see that the teacup firmware mostly takes up flash, which can only be programmed externally, so that tells me that when i upload i reflash the bootloader and it's not a sketch that i'm uploading, d-oh !
So i'll have to dig
by
scrub
-
Firmware - mainstream and related support
Just had an "eureka" moment, as i was thinking of what could be wrong with the arduino i glanced and looked at the build message.
QuoteLink completed normally.
ATmega... '168 '328(P) '644(P) '1280
FLASH: 19732 bytes 137.64% 64.23% 31.08% 15.29%
RAM: 1267 bytes 123.73% 61.87% 30.93% 15.47%
EEPROM: 32 bytes 3.
by
scrub
-
Firmware - mainstream and related support
Well i fixed and rather easily, just by uninstalling the newest version of arduino IDE and installing 1.0.6, but some other problems have surfaced and that has to do with communicating with arduino nano, now it builds fine but when i hit upload i get "timeout communicating with programmer" message.
What makes this very unusual in my opinion is that i can upload arduino sketches without any proble
by
scrub
-
Firmware - mainstream and related support
I'm about as smart as a bag of rocks when it comes to firmware/software trouble-shooting.
I'm making myself my first 3D printer and decided to use the Teacup firmware, all went well untill i tried to build.
My settings look exactly the same as the ones here : . The only diffence being that i have my arduino directory field empty, in which case it should find the needed files automatically.
I did
by
scrub
-
Firmware - mainstream and related support