So – following the advice I reconnected to the standalone ATmega through the FTP232 converter. Uploading worked fine, but PHD2 did not see the autoguider.The COM port was 4 and called something like “Serial Converter” when I was expecting to see “ArduinoST4 telescope driver (ASCOM)”. And then had uploaded the Arduino Autoguider sketch, probably with Board: Arduino UNO selected – I think. NOTE: I had burned a bootloader onto the Atmega328 earlier via the UNO board. “i had the same problem.i had a atmega328p and a cp2102 with dtr pin.i tried different ways.after spend of 3 days i found the solution.Īfter burn bootloader to raw atmega328p with arduino as isp or usbasp you must choose only arduino pro or pro mini as your board in tools menu and one of the avr isp or arduino as isp or avr isp mkll as programmer.and then upload your sketch.that’s it.” While I was writing up this post on the Arduino forum, I was prompted to look at this post “Standalone ATMEGA328 with CP2102 USB-Serial Converter”, which had not cropped up in my previous at the Arduino forum had the exact solution.

My question was: Should it be possible to communicate with the autoguider on the standalone Atmega328 via the FT232? The is no apparent clash between the autoguider and the FT232 drivers. If I instead programmed the Arduino Autoguider program into an UNO board, (which means that I am now using the UNO’s onboard USB-Serial converter), the Arduino Autoguider program works just fine. PHD2 cannot communicate with the Arduino Autoguider because the computer only sees the FT232 board. I am using an an autoguiding program called PHD2. I can download Blink to the standalone 328 - it works just fine. I can download an the Arduino Autoguider program to the chip. I communicate with it via an FT232 USB-Serial converter board. My implementation for a telescope autoguider uses a standalone Atmega328.

NOTE: I eventually found a solution to this problem (see below), but here is the scenario:

Stellarium telescope control g11