MicroCode Studio+ with Sony Vaio and USB/RS232 converter

[andrewwaack]

the usb to com converter dose not assign it self as a true comport it is a virtural com port i have this exact problem i use the velliman programer with picprog2 as the loader i first write the code in mcs+ then compile using pic basic pro then start picprog2 load hex file and every time i write or erase tothe pic i have to reselect the com port for it to work
check systems properties on the vaio to see what com port is assighed to the converter

[Josuetas]

OK here is how it works, first of all you can change the port number you want to use with your USB-RS232 conversor, for this go to Control Panel->System-> Hardware->Device Manager. In the ports section you might find your serial port with the port it is using between () . i.e. Serial Port(COM4).

By double clicking and going to Port Configuration (i have it on spanish so i dont know the exact words) -> Advanced. There you will find a combo-box to select the number of port you want to be used by the device. Choose one tha is not Used.

On the other hand. MCSP always shows the ports to be used in a combo box (i have MCS 3.0) if the port is in use when MCS is opened it will not be shown in the combo box. Try closing all previous used programs and then open MCS, most surely.. if the port is not an option it doesn´t exist or it is in use, not being possible to be used by MCS.

I have worked with my Vaio C140G/B with this conversors with no problems before, and you should have no problem since this devices are based on the same chip.

I hope you find my post useful.

DJC

[BrianT]

Thanks Josuetas, I think I understand what you are saying.

What I found very confusing was that parts of MCS worked on the Sony Vaio but other parts of MCS did not work. For example, the MCS Serial Communicator worked as did TeraTerm which is my preferred serial terminal emulator program but the MCS Loader did not work at all.

I think I am right in saying that MCS Serial Communicator and TeraTerm do not check what ports are available, they just assume COM1 will always be available and mostly it is.

MCS Loader on the other hand uses a windows API call to access a COM port. Windows manages the VCP BUT not all USB to Serial adapters handle the com port assignment correctly.

I had an IT guy look at my Sony Vaio problem. A search through Registry showed only COM4 and COM5 had entries - not COM1 or COM2. He added a new registry key as follows.

In Hkey_local_machine\hardware\devicemap\serialcom was added a string "COM1"

The USB to Serial converter I have is by "Magic Communications Technology" - a dodgy name if nothing else.

It now works but only after a manual entry for COM1 was added to registry and one further gotcha is covered.

There appears to be another problem with the Sony Vaio. If there is any activity on the USB/Serial port during boot up, the Sony will interpret this as mouse activity and then assigns the mouse to the USB port. Any attempts to use the serial port sends the cursor scurrying all over the screen. What I must do at boot up is remove the USB connector, let the machine complete the boot, then attach the USB/Serial adapter, then start MCS.

Not quite plug and play but eventually workable.

Thanks to those that sent me suggestions.

Cheers
Brian

[Ioannis]

If you change the COM1 manually entered in Registry to COM2, does it still interpret data on USB as mouse?

Ioannis