Hi Jags,

Be sure the Arduino IDE is not running in the background while you start Proview in runtime.

I am 100% sure that arduino is not running at background.

What Arduino IDE do actually with ftdi chip when I send a character, as because after that arduino board started work with proview even pressing reset button.

Please note that if I toggle the power I must send a character through serial monitor before starting proview.

Please note that I have purchase arduino board from
www.embeddedmarket.com/products/Arduino-...atible-Freeduino-DU/
it is 100% compatible.

regards
jags

Ahummm,

Intresting.
If you are 100% sure your project is ok, no conflict with /dev/ttyUSB0 then the problem must be in the sketch.

Can you upload the sketch you are using?

Do you use any virtual machine ?

Personnaly I had very weird problem using arduino usb over VM. I have never understood exactly why as it works at proview runtime start.

But deconnection / reconnection was malfunctionning with a behaviour which is not always the same.

Perhaps you're in this case ?

Snarf

No I am not using ubuntu on VM, How ever using Ubuntu 10.04 LTS, and arduino-1.0.

I debug the sketch which I am using with LED on pin. During startup proview send config packet but arduino never get byte received = msgSize so never send config success message. When we send a char through arduino serial monitor before startup proview arduino get byte received = msgSize and send config success message accordingly.

The point what I notice that at first there is a mismatch of bit rate that is why arduino never get byte received = msgSize. It is may be due to improper initialization of ftdi chip & driver by proview.

After that when a char is sent by serial monitor ftdi chip & driver initialized properly and then at startup arduino get byte received = msgSize by proview. This is what I guess it may not be correct.

But if it is true then it is a big bug of proview of ftdi driver.

How ever I am sending the sketch attached here with.

Regards
jags