Hi,

It monitors okay for me regardless of a project being open. 

Can you confirm the correct port is selected and send a screen shot of the serial monitor open wide enough to see the options that are selected from "connected" to "speed"?

Thanks

Great. 

Maybe the "connect" button had been unchecked or baud was wrong.

Anyway good to hear its working, let me know if it doesn't.

Thanks

Okay, a few questions to try to narrow things down. I can't see it being connected to the selected board.

• If you click "connect" so that it disconnects then click again to connect, do you see any output or an error
• Does the problem happen if you use "View>Other Windows>Arduino Port Monitor"?
• Are there any new line chars in the expected output (serial.println() or \n)?

Thanks

Ah you are switching port? I thought when you said switch board you meant just using the toolbar but you actually have two different boards connected.

First off please answer the three questions in my previous post. 

Then do the following:-

Select the Yun port
Close the ide
Reopen the ide
Open the serial monitor

any data?

If no do this

Switch on Dtr
Uncheck and recheck Connect

any data?

If no, close the serial monitor and then re-open.

any data?

The idea is to take the Uno out of the equation so we can have a clean view of the connection to the Yun

Okay please leave dtr on. It should have been on by default anyway. The arduino ide has dtr always on.

Q: With dtr on can you confirm Visual Micro reliably shows the serial output in all situations?

I have to remind myself of the difference between Uno and Yun/Leonardo.

Q: Does your Yun code have while(!Serial){} in the Setup() or does it not use Serial if no Serial was detected during Setup?

Thanks

Hi,

Great.

As far as I recall the Yun is a Leonardo type of board. They normally have a while(!Serial){} wait or a delay of a couple of seconds before they are allowed to progress through the Setup() method. 

This is because the usb port and Serial are handled by a more flexible type of "virtual/dynamic" Serial port. The Serial object is only created when a device connects to the port so if Serial is to be used some checks should be made.

I am still not entirely clear about why connecting without causing a reset should fail considering we know the mcu had been reset by the arduino ide in many of your tests.

When I get a mo I will, for my own sanity, have a play and try to understand what happens without a reset (dtr). It might be that the Leonardo detects a port close and frees the serial. 

Maybe you can blink the led but leave the serial print statements working as they have been. See if the arduino carries on running when you disconnect the serial. Does the led continue to blink?