Visual Studio Ide for Arduino
https://www.visualmicro.com/forums/YaBB.pl
Visual Micro >> Visual Studio 2017, 2019 >> VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
https://www.visualmicro.com/forums/YaBB.pl?num=1562043788

Message started by Bob Jones on Jul 2nd, 2019 at 6:03am

Title: VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
Post by Bob Jones on Jul 2nd, 2019 at 6:03am
Is there any hope of getting rid of this garbage. I know that I can make it go away by compiling in Release mode, but then I can't see the Digital Pins. Here is what my Serial Monitor looks like when I compile in Debug mode:

ENTER COMMAND IN SERIAL MONITOR:
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:17:4:0:43:|||_VMDPR
VMDPR_|0:56:112:21:6:0:43:|||_VMDPR
VMDPR_|0:56:48:21:4:0:43:|||_VMDPR
VMDPR_|0:56:112:21:4:0:43:|||_VMDPR
VMDPR_|0:56:48:17:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
VMDPR_|0:56:48:16:4:0:43:|||_VMDPR

I know I have raised this issue before, but I have to ask again: Any hope?


Title: Re: VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
Post by Visual Micro on Jul 2nd, 2019 at 10:43pm
Is your own code sending serial? If so has it always got \r\n line terminator (println())

What does "ENTER COMMAND IN SERIAL MONITOR:" mean?


You can switch off digital report and add this to a breakpoint message

{@ReportDigital}

The benefit of this is the pins are refreshed when you want them to be and you will know when the refresh message is being sent so can ensure your own serial is terminated fully.

Alternatively use an FTDI cable of adapter to hook up a second serial port (or the software serial option) so that the debugger does not use the serial port you use in your code.

Finally, the latest release of visual micro supports hardware debugging for quite a few boards, more to come. Which board are you using?

Title: Re: VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
Post by Bob Jones on Jul 2nd, 2019 at 10:56pm
Tim,

Thanks for getting back to me. The "ENTER COMMAND IN SERIAL MONITOR:" message is my code letting me (the user) know that I can enter commands into the Serial Monitor to control the robot. Commands can also come from a WiFi connection, a Bluetooth connection or even from an internal module called Navigator that generates commands that avoid obstacles.

You state, "Alternatively use an FTDI cable of adapter to hook up a second serial port (or the software serial option) so that the debugger does not use the serial port you use in your code." I am not familiar with FTDI cables, but the idea of hooking up a second monitor for Serial.print and Serial.read has my interest. Any more documentation on how to do this?

Boards: I use MEGAand NANO boards and occasionally UNOs.

Title: Re: VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
Post by Visual Micro on Jul 2nd, 2019 at 11:08pm
Doing reads in your own code and many writes or writes without line terminator will be too much for the debugger to share the same serial port. So you are certainly in danger of needing to use a 2nd port.

We would normally expect the debug to be on the 2nd port so that your own serial command is always on the same port regardless of debug or not,

With the mega it is easy because it has more than one Serial port. So you can use the vMicro>Debugger menu to set the Remote port to Serial2 and Local port to the COM port that your FTDI is connected to. For the Uno and nano which only have one hardware Serial port you need to use the F$ project properties to set the Transport to SoftwareSerial and the LocalPort to the FTDI COM port and the Local/Remote speed to 57600 baud.

In both cases you need an FTDI cable or board that plugs into the PC as normal USB but on the other end you have capability to take wires to the respective pins on the circuit board.

You can read more here about debugging Arduino with different ports and pins here

The above page shows the FTDI board, this page shows an FTDI cable. (I searched google for the cable and picked a random so no recommendation about price or purchase. It looked expensive).

You only need two pins from the FTDI, RX,TX. Ignore power and other pins.

Title: Re: VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
Post by Bob Jones on Jul 2nd, 2019 at 11:21pm
SO I think I get it. I get an FTDI cable,plug that into a USB port and hook it to the Serial 2 pins on the Mega. Correct?

The only thing I need to know is what to buy. Is this what you are recommending? https://www.amazon.com/EZSync-serial-TTL-232R-5V-WE-compatible-EZsync009/dp/B010K5NC68/ref=sr_1_2?keywords=ftdi+cable+for+arduino+mega&qid=1562105744&s=gateway&sr=8-2

If so, it has 6 wires but Serial ports only need two. What are the other four?

Title: Re: VMDPR_|0:56:48:16:4:0:43:|||_VMDPR
Post by Visual Micro on Jul 3rd, 2019 at 12:04am
It's up to you if you buy a board or a cable and if the cable is male or female.

As I said the other pins can be ignored but they are explained in the picture I posted and on the web.

Visual Studio Ide for Arduino » Powered by YaBB 2.5.2!
YaBB Forum Software © 2000-2019. All Rights Reserved.