Hi Don,

I looked at your log file and saw the timeouts but the driver recovered in each case. It doesn't look like there was a
significant problem.

-Ray

-----Original Message-----
From: ap-gto@... [mailto:ap-gto@...] On Behalf Of Don
Sent: Wednesday, December 30, 2009 10:07 PM
To: ap-gto@...
Subject: [ap-gto] Re:New ASCOM Driver .48



Hi Ray
I have been following this thread re communication error in Ver.48 of the ASCOM driver. I reviewed my files and see

they contain

what appears to be a com errors interspersed throughout the file. Not sure if this is what Yves and Sam are referring

to or not but I

thought I would upload one of my shorter files for your review.
It is located in Files\New AP ASCOM Driver\ASCOM Log Files\Don's Log Files.
Hope this helps
Happy New Year
Don

--- In ap-gto@... <mailto:ap-gto%40yahoogroups.com> , Yves Laroche <yves.laroche@> wrote:

Thank you very much Sam for your fast response. You did exactly what I
asked you before. Thanks.



I really don't know what to think about your results. I thought that your
problem was the same as mine but it seems not. According to your results, I
will have to try version 0.47 to see if my port 2 connection may behave
differently. However, by memory I always got retransmit communication
errors.



The best way to help to pinpoint your problem is to send your logs to Ray.



Best wishes to you all. Happy New Year 2010!



Regards,

Yves





_____

De : ap-gto@... <mailto:ap-gto%40yahoogroups.com> [mailto:ap-gto@... <mailto:ap-

gto%40yahoogroups.com> ] De la part de

Sam
Envoyé : 30 décembre 2009 20:51
À : ap-gto@... <mailto:ap-gto%40yahoogroups.com>
Objet : [ap-gto] Re:New ASCOM Driver .48





Good Evening Yves,

Tonight I loaded driver version .48 and moved the serial port connection to
port 2 (the lower connection). Unfortunately, I did not see a change in the
behavior of version .48 of the driver. Whan I returned to version .47 either
port worked flawlessly. I hope this is what you asked me to test and that
the results (good or bad) are presented here effectively for your needs. I
have noticed that the number of errors reported by the .48 driver is about
1/4 of the resends. I see no errors with the .47 driver. I will try to send
a log file in the next few days to the AP files site to see if Ray can tell
me what I am doing wrong (as I truly suspect that I am doing something silly
either in the settings or in the program loading method).

My best regards to you and all AP users for a joyous holiday season and a
prosperous New Year!

Sam

--- In ap-gto@yahoogroups. <mailto:ap-gto%40yahoogroups.com> com, Yves
Laroche <yves.laroche@> wrote:

Hi Sam,



Last night I decided to investigate about my communication errors. I found
that the lower serial connection of my GTOCP3 was faulty.



Please would you try to connect your serial cable to the other serial
connection and try in using version 0.48 of the driver? Let me know about
your results. Thanks.



Regards,

Yves





_____

De : ap-gto@yahoogroups. <mailto:ap-gto%40yahoogroups.com> com

[mailto:ap-gto@yahoogroups. <mailto:ap-gto%40yahoogroups.com> com] De la
part de

Samuel Bruce
Envoyé : 30 décembre 2009 09:54
À : ap-gto@yahoogroups. <mailto:ap-gto%40yahoogroups.com> com
Objet : [ap-gto] Re:New ASCOM Driver .48





Yves,

I have experienced many problems with version .48 which I did not have

with

prior versions. I am currently running .47 and everything is perfect!

There

are communications errors and missed commands. I have reset the timeout to
500 but see no improvement. I use a Mach1GTO with GTOPC3. The results with
version .47 are excellent and the driver is so versatile and effective. I
am so appreciative of Ray and AP for this new driver work.

Thanks,

Sam Bruce







__________ NOD32 4730 (20091230) Information __________

This message was checked by NOD32 antivirus system.
http://www.eset. <http://www.eset.com <http://www.eset.com> > com



[Non-text portions of this message have been removed]

__________ NOD32 4730 (20091230) Information __________

This message was checked by NOD32 antivirus system.
http://www.eset.com <http://www.eset.com>



[Non-text portions of this message have been removed]