Show Posts
Pages: 1 2 3 [4]
46  Using Arduino / Installation & Troubleshooting / Re: IDE 0022 Serial monitor bug? on: April 24, 2011, 05:12:26 pm
Just open new sketch, copy  the code from first message, upload and enjoy smiley
47  Using Arduino / Installation & Troubleshooting / Re: IDE 0022 Serial monitor bug? on: April 24, 2011, 05:06:58 pm
Can you try it yourself in similar environment?
48  Using Arduino / Installation & Troubleshooting / Re: IDE 0022 Serial monitor bug? on: April 24, 2011, 04:55:50 pm
Yessir!
As I said, I can see correct output on 14400 when using 'third party' serial port monitor.
This is obviously the bug of Arduino IDE.
49  Using Arduino / Installation & Troubleshooting / Re: IDE 0022 Serial monitor bug? on: April 24, 2011, 04:50:15 pm
No, no other speed settings  convert garbage into text.
But I have noticed that when I use Serial.begin(9600) (serial output is OK at IDE setting 9600), I still can see this output when I switch serial monitor to 14400. This happens _only_ on 9600. Any other board rates only produce correct output when serial monitor is set to matching speed.
Just tried the same on a different computer, Windows 7, IDE 0022. Same bug.
50  Using Arduino / Installation & Troubleshooting / Re: IDE 0022 Serial monitor bug? on: April 24, 2011, 03:41:39 pm
I am not aware of what 'modified IDE' is; I just downloaded arduino-0022.zip, unzipped it and ran arduino.exe
The same result I had with IDE 0017.
51  Using Arduino / Installation & Troubleshooting / Re: IDE 0022 Serial monitor bug? on: April 24, 2011, 01:15:42 pm
Switched to latest available FTDI driver 3/18/2011 2.8.14.0 with no result smiley-sad
52  Using Arduino / Installation & Troubleshooting / IDE 0022 Serial monitor bug? on: April 24, 2011, 05:17:42 am
14400 and 28800 shows garbage. All other settings are OK.
This is IDE issue, when monitoring serial port with other software, data looks normal.
Example sketch:

void setup() {
  Serial.begin(14400);
}

void loop() {
      Serial.println("Test");
      delay(20);
}

Example of garbage output:

f×n f×n f×n f×n f×n f×n f×n f×n f×n f×n f×n f×n f×n f×n f×n f×n f×n f×n f×n f×n f×n f×n f×n f×n f×n f×n f×n f×n f×n f×n f×n f×n f×n f×n f×n f×n f×n f×n f×n f×n f×n f×n f×n f×n f×n f×n f×n f×n f×n f×n f×n f×n f×n f×n

OS Windows XP SP3, processor Intel P4 2.8GHz, RAM 2 Gb; board Ard.Duemilanove, chip 328 (the same with 168)
FTDI Driver 5/19/2006 ver.2.0.0.0
53  Forum 2005-2010 (read only) / Frequently-Asked Questions / Re: LCD Display communication on: March 09, 2009, 12:28:07 am
OK, just in case if anybody is interested, seems like I solved the issue without extra hardware components.
The idea is to re-initialize backpack after bootloader is loaded.
Vss of backpack is connected to Ard.+5v, backpack ground is connected to pin2, backpack Rx connected to pin 1.
initialization code:  
void Setup(){  
  pinMode(1,OUTPUT);
  pinMode(2,INPUT);
  digitalWrite(1,LOW); //my idea was to ground backpack input
  digitalWrite(2,HIGH); //and turn off it's power
  delay(500);
  pinMode(2,OUTPUT);  
  digitalWrite(2,LOW);  //now pull down backpack ground=power it
  delay(3000);             //wait until splash screen disappears
  Serial.begin(9600);    //start communication
  Serial.print(<something>);
}
I do understand this is quite rough and probably not safe, but it works. No more garbage upon power up or program upload.
And, yes, backlight is set to value 140, that is, total backpack power current is about 12ma. I played with pins modes and LOW/HIGH states because initially backpack current was jumping for half a second up to 60 ma which is not safe at all. Seems like with this setup commands there is no such power jump; I found it rather intuitively  :-[
I can also see that backpack "ground" is not actually "0",it is rectangular shape pulse around 0.4 v and freq~100Hz, seems like it originates from backpack.
54  Forum 2005-2010 (read only) / Frequently-Asked Questions / Re: LCD Display communication on: March 02, 2009, 03:16:43 pm
Yes, Gordon, I was thinking the same way, some small relay with normally opened contacts.
The thing is, if LCD is in unknown state, resetting Arduino will not help, you need to reset backpack, and the only way to do is by switching of it's power.
What's interesting - it's like _there is_ some way of resetting backpack by some command, because when in "garbaged state" a couple of times I managed to reset it (initiate splash-screen) sending out some x7E combinations, but it never worked next time smiley
So I think there are some undocumented backpack commands that may invoke reboot.
55  Forum 2005-2010 (read only) / Frequently-Asked Questions / Re: LCD Display communication on: March 01, 2009, 05:11:43 pm
Thank you, this is basically correct, but I had in mind rather some hardware solution... like, connect/disconnect backpack Rx using some transistor or mosfet... just trying to save myself some time of googling on long forgotten electronics details...
56  Forum 2005-2010 (read only) / Frequently-Asked Questions / LCD Display communication on: March 01, 2009, 03:42:42 pm
I am working with 16x2 LCD with SparkFun SerLCD backpack.
I found that I have to disconnect backpack rx input from Arduino Tx
while uploading new sketch into Ard, as well while just applying power to Arduino board (that is, just connecting it to USB or battery). Otherwise there is a lot of garbage transmitted by board to backpack at boot time, which takes LCD into unknown state.
So, my question is:
what is the best way programmatically connect/disconnect backpack serial input from Ard?
I think it's not 'doable' without adding, say, transistor or something like that.
Please share your opinion!
Pages: 1 2 3 [4]