Show Posts
Pages: [1] 2
1  Using Arduino / Installation & Troubleshooting / Re: Tools menu very slow on: July 01, 2013, 12:22:31 pm
Quote
Once I disabled ALL other virtual COM ports in windows device manager the Arduino IDE worked perfectly.

Yes, I have found this also. However, my current project involves communicating with the Arduino itself via Bluetooth, so I am looking for a way to make them compatible.
2  Using Arduino / Installation & Troubleshooting / Re: Tools menu very slow on: July 01, 2013, 08:47:32 am
Eried: Thank you for your help.
Can I use this: http://servicios.ried.cl/arduino/temp/rxtxSerial-2.2_fixed_2009-03-17.rar
to replace the rxtxSerial.dll in the Arduino IDE version 1.5.2?
Thank you.
3  Using Arduino / Installation & Troubleshooting / Re: Tools menu very slow on: June 30, 2013, 08:37:16 pm
Thanks Eried.
Your installer looks impressive. Does it install Arduino IDE version 1.5.2 ? (I have a Due)
I will work through the thread about what can be done about the slow Tools menu problem, but it looks like it will take a bit of time and thought.
Does using your installer take care of this problem?
If I use it, will it be confused by the fact that I already have installed a driver for one Uno board?
4  Using Arduino / Installation & Troubleshooting / Re: Tools menu very slow on: June 29, 2013, 11:11:36 pm
Update:
I installed the Arduino software on another (desktop) Windows 8 computer, and the Tools menu works fine.
I have deleted and reinstalled it on the Surface Pro, and the same thing happens. It takes a LONG time for the tools menu to drop down. But everything seems to work.
This is very frustrating. Does anyone have any suggestions?
5  Using Arduino / Installation & Troubleshooting / Tools menu very slow on: June 29, 2013, 04:29:40 pm
I have downloaded the Arduino IDE 1.5.2 on my Windows 8 Surface Pro.
I have successfully setup my Uno with driver, and used the IDE to compile and upload the Blink test example.
I have not yet done the same with my Due, but it should work.
The problem is that the Tools menu takes a very long (frustrating) time to show the drop down menu. I have been using the IDE with my Windows XP for some months, without any problem. Is there an issue with Windows 8 and the Arduino software?
6  General Category / General Discussion / Re: Arduino Due (released Oct 22, 2012) Compatibility on: March 30, 2013, 03:35:24 pm
"You think i can use a DUE on my project of a spaceship to go to the Moon ?!
PS- My Arduino UNO didnt had enough Sram ..."

http://downloadsquad.switched.com/2009/07/20/how-powerful-was-the-apollo-11-computer


7  Using Arduino / Programming Questions / Re: analogWrite incompatable with digitalWrite on: March 27, 2013, 09:10:10 pm
The serial port conflict with pin 0 is well documented:
" Serial. It communicates on digital pins 0 (RX) and 1 (TX) as well as with the computer via USB. Thus, if you use these functions, you cannot also use pins 0 and 1 for digital input or output."
I hope that something like "Once PWM, always PWM" will also be well documented.
Perhaps a cancelPWM(int pin) function would be useful.
8  Using Arduino / Programming Questions / Re: analogWrite incompatable with digitalWrite on: March 27, 2013, 06:05:00 pm
The Due board incorporates a sophisticated CPU, and people will write sophisticated and complex code for it. If setting a pin HIGH or LOW succeeds or fails depending on a something done a thousand lines of code earlier, perhaps in a function written by someone else, bugs will be essentially impossible to diagnose.
Possible suggestions:
1: Basic functions should cause as few side effects as possible. Those that are unavoidable should be documented.
2: Functions that set states could return a value to indicate success or failure.
3: Pins could be queried to determine their state. For example, isDigitalOut(9) would return true if pin 9 were able to accept a call to digitalWrite(9, LOW). (Or a library could define C++ Pin objects with an interface to allow for this.)

It is important that I make clear that I started this thread to ask for help with a problem I had trouble with. People who answered have been helpful and courteous. Furthermore, I have great respect for those who have created the Arduino project, and for their immense amount of work coding and testing it all. Any suggestions I may have are made in that spirit.
Thank you.
9  Using Arduino / Programming Questions / Re: analogWrite incompatable with digitalWrite on: March 26, 2013, 05:58:08 pm
The original problem that prompted this thread was unexpected behaviour of a robot using the Solarbotics CMDR motor drive shield. The CMDR shield uses pins 3, 5, 6, and 11 for outputs to the motor drive chip. Those pins do in fact exhibit this problem. I chose pin 9 to do further testing and to frame the question in a simpler form because it is a PMW chip on both the Uno and the Due, and it is not used by the motor shield.
I have not tested the other 7 PMW chips on the Due, but I will do so.
10  Using Arduino / Programming Questions / Re: analogWrite incompatable with digitalWrite on: March 26, 2013, 09:55:02 am
"a call to analogWrite() should not affect a subsequent call to digitalWrite()"
I agree. It is difficult to believe that this is the intended behaviour.
If it is unavoidable for technical reasons, this should be documented clearly.
11  Using Arduino / Programming Questions / analogWrite incompatable with digitalWrite on: March 25, 2013, 12:29:00 pm
I posted this to the Due forum. Perhaps it is more appropriate here.

With the Arduino 1.5 software, the following code blinks an LED using the Uno board, but not with the Due:

int led = 9; //PWM
void setup() {               
  pinMode(led, OUTPUT);     
}

void loop() {
  analogWrite(led, 220);
  delay(1000);
  digitalWrite(led, LOW);
  delay(1000);
}

However, the following works with both boards:

int led = 9; //PWM
void setup() {               
  pinMode(led, OUTPUT);     
}

void loop() {
  analogWrite(led, 220);
  delay(1000);
  analogWrite(led, 0);
  delay(1000);   
}

Does the Due not allow a call to digitalWrite if analogWrite has already been called?

The reason I ask this question is that such behavior is not only non-intuitive, but also breaks many lines of useful existing code. See the attachment for an example of motor driving code (for the Solarbotics Brutusbot robot) that works for the Uno board, but not for the Due board.

I have modified the robot code successfully. But this behavior of the analogWrite() and digitalWrite() seems to be a serious problem that should be addressed. 

Am I missing something?
12  Products / Arduino Due / Re: digitalWrite following analogWrite on: March 24, 2013, 12:29:50 pm
The reason I ask this question is that such behavior is not only non-intuitive, but also breaks many lines of useful existing code. See the attachment for an example of motor driving code (for the Solarbotics Brutusbot robot) that works for the Uno board, but not for the Due board.

I have modified the robot code successfully. But this behavior of the analogWrite() and digitalWrite() seems to be a serious problem that should be addressed. 
13  Products / Arduino Due / digitalWrite following analogWrite on: March 23, 2013, 04:53:42 pm
I am new to the Due. Here is my question:
The following code blinks an LED using the Uno board, but not with the Due.

int led = 9;
void setup() {               
  pinMode(led, OUTPUT);     
}

void loop() {
  analogWrite(led, 220);
  delay(1000); 
  digitalWrite(led, LOW);
  delay(1000); 
}

However, the following works with both boards:

int led = 9;
void setup() {               
  pinMode(led, OUTPUT);     
}

void loop() {
  analogWrite(led, 220);
  delay(1000); 
  analogWrite(led, 0);
  delay(1000);   
}

Does the Due not allow a call to digitalWrite if analogWrite has already been called?
14  Using Arduino / Installation & Troubleshooting / Re: DUE not recognized in Device Manager on: March 06, 2013, 06:45:09 pm
OK. A new (and presumably better) USB cable did the trick.
Thank you for the help.
15  Using Arduino / Installation & Troubleshooting / Re: DUE not recognized in Device Manager on: March 05, 2013, 08:32:11 pm
On the XP:
Connecting the DUE programming port:
1: The green LED lights, and the amber LED flashes
2: In Device Manager, "Unknown device" appears under the heading of "Universal Serial Bus Controllers" (not "Ports")
The Device Instance ID is USB\VID_0000&PID_0000\5&3AD6B64D&0&1
All attempts to update the driver by browsing to the DUE software Drivers folder fail
Pages: [1] 2