Q-Link connecting problem
#1
Connecting to Q-Link was working before I upgraded to Firmware 2.93.  It is odd because I can get a connect response by issuing the command (in ccgms): ATDT 5551212, but running Q-Link never finishes connecting.  I've attached a photo of the results of commands ati, atdt 5551212 and at&v.
   
Reply
#2
You can go back to the previous version using AT*DOWNGRADE, but it is unlikely this will fix the issue.  This is a common periodic problem with Q-Lonk.
Reply
#3
(08-07-2018, 10:24 PM)admin Wrote: You can go back to the previous version using AT*DOWNGRADE, but it is unlikely this will fix the issue.  This is a common periodic problem with Q-Lonk.

When I connect to Q-link using ATDT 5551212 in a terminal program, the WiModem OLED indicates that it is connected to Q-link.  When I try with the Q-Link software, it never connects and OLED status never changes.

I downgraded and that did not work.  I upgraded back to 2.94 and that doesn't work either.  I will try an unvalidated Q-Link disk image and see if that works.
Reply
#4
Did you follow the Q-Link information below?

http://www.cbmstuff.com/forum/showthread.php?tid=329

A lot of people miss the fact that DCD must be set to on or Q-Link will ignore the connection, just like what you describe.
Reply
#5
(08-22-2018, 05:49 PM)admin Wrote: Did you follow the Q-Link information below?

http://www.cbmstuff.com/forum/showthread.php?tid=329

A lot of people miss the fact that DCD must be set to on or Q-Link will ignore the connection, just like what you describe.

I did follow that information, and in the first post here I included the results of AT&V  which shows a status of "&C0" which I believe from the manual and the post you linked to mean that DCD is always on.  Also Baud rate is shown to be 1200 and using the spoofed number a successful connect is shown. 

For the next step I will try an unvalidated Q-Link disk.  Thank you for your help as I trouble-shoot this problem.
Reply
#6
If you are getting a connection to the server, then the issue has to be on the Q-link/server side of things. At that point the WiModem has done everything it can do to. It's just a dumb device at that point, waiting on data.
Reply
#7
(08-27-2018, 06:55 PM)Sprite9 Wrote:
(08-22-2018, 05:49 PM)admin Wrote: Did you follow the Q-Link information below?

http://www.cbmstuff.com/forum/showthread.php?tid=329

A lot of people miss the fact that DCD must be set to on or Q-Link will ignore the connection, just like what you describe.

I did follow that information, and in the first post here I included the results of AT&V  which shows a status of "&C0" which I believe from the manual and the post you linked to mean that DCD is always on.  Also Baud rate is shown to be 1200 and using the spoofed number a successful connect is shown. 

For the next step I will try an unvalidated Q-Link disk.  Thank you for your help as I trouble-shoot this problem.

Turns out that AT&C1 is needed to connect to Q-Link, which is contrary to: http://www.cbmstuff.com/forum/showthread.php?tid=329 as well as some old notes I had.
Setting AT&C1 solved my problem and works with the 3.0 wimodem software.
Reply
#8
I tested this tonight and find that it does not work with AT&C1 set, but does work with AT&C0. This would mean that you have the polarity switched (AT*D).
Reply




Users browsing this thread: 1 Guest(s)