Hi,

my setup is: Visual Studio 2012 + Olimexino32u4 (Arduino Leonardo clone) + Visual Micro 1.1212.30 + Debugger

I can compile and upload, but serial monitor does not work properly. No problem at all with Arduino IDE Serial Monitor.

Any advice?
Thank you

Tim@Visual Micro wrote on Jan 20^th, 2013 at 12:24pm:

Serial.println("TEST"); 

Sometime writes "TES" without "T", most of the times writes nothing.

On Arduino Ide works ok.

Bye

Tim@Visual Micro wrote on Jan 20^th, 2013 at 1:55pm:


115200

Tim@Visual Micro wrote on Jan 20^th, 2013 at 1:55pm:


Nothing

// the loop routine runs over and over again forever:
void loop() {
  digitalWrite(led, HIGH);   // turn the LED on (HIGH is the voltage level)
  delay(500);               // wait for a second
  digitalWrite(led, LOW);    // turn the LED off by making the voltage LOW
  delay(500);               // wait for a second
 
  Serial.println("TEST");
} 

Tim@Visual Micro wrote on Jan 20^th, 2013 at 1:55pm:


Not installed (Uninstalled).

I have tested this with a Leonardo and it works fine for me. 

Another test I made with 1ms delay also works



The only thing I can think that would be different is to look at the usb driver in Device Manager (Ports (COM & LPT). 

The usb drivers for the Teensy kit are the same as Arduino. I notice that with my Leonardo plugged in my driver shows a manufacturer of "PJRC.COM, LLC". The driver also has the name "USB Serial (Communication Class, Abstract Controls Model)". pjrc.com make the teensy stuff.

Which driver is showing for your board? 

If you can't find a better driver then there is a post of how to update your usb drivers in this forum somewhere. I'll dig it out if needed.

Thanks

ps: If the debugger is installed or not it does not affect the serial reader unless you set (Micro Debug)=Full

Was that with Leonardo?

Okay Teensy is probably classed as the same.

This smacks of usb issues, I know vm could be more efficient with the serial reader but I never get problems and run the same system as you. 

Here is a simple example that works for me. Can you please try this, lets work up from here to find when it goes wrong. BUT, LuiginoRM is only sending a small serial packet once per second so we know the buffers are not being blown, the problem has to be something obvious.

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

void loop() {
  Serial.println("TEST123456789012345678901234567890TEST");
  Serial.println("TEST123456789012345678901234567890TEST");
  Serial.println("TEST123456789012345678901234567890TEST");
  Serial.println("TEST123456789012345678901234567890TEST");
}
 

Which usb driver shows when your board is plugged in?

Yes you were hammering it. I think it's a different issue, this one is unable to handle 4 characters per second.

Yes but the java serial system uses a very different method for serial comms so how it interacts with the drivers might vary quite a bit.

I have a question, is the last char or every message missing or just the first message after the arduino starts up?

I've just checked vm serial reader and it just reads and displays whatever windows gives it so it is quite simple. 

I have found that the window layout was being disabled prior to writing text to the serial monitor text box. It's a temporary setting that vs resumes when it requires so should not be part of this problem. This was old code that is no longer required so I have removed it. But I am clutching at straws in a very simple system. 

I don't want to waste your time more than this has already but, trying the usb drivers from pjrc who produce the similar Teensy board might be worth a try. There must be a reason why they decided not to use the drivers supplied with the arduino ide. Again clutching at straws, sorry.

The teensy windows/xp/vista/7 installer should create a Teensyduino folder. 

http://www.pjrc.com/teensy/td_download.html

Teensyduino is just a slightly adapted version of the arduino. The drivers folder below the ide should contain all the usb drivers.

Thanks for trying. I don't think a clean install will help. The product is just a few dlls in the Visual micro program folder.

I guess you have all windows and vs service packs applied?

I'll try to add a serial trace facility over the next few days so that we can see if this is a serial/usb or UI issue.

I will also create a little c# app that reads the serial port just to prove that vm/vs is struggling and not windows/usb

Thanks for the update