Cannot connect to 410
Closed this issue · 2 comments
When I try to connect to my 410 device, I get the following errors:
[MainThread] 2012-05-12 13:32:33,686 WARNING Retryable error. 5 try(s) remaining. No reply to command. RESET_SYSTEM()
[MainThread] 2012-05-12 13:32:33,702 INFO Searching for ANT devices.
[MainThread] 2012-05-12 13:32:57,655 DEBUG Got ANT-FS Beacon. device_number=0xabae Beacon{'auth_type': 3, 'pairing_enabled': 0, 'device_state': 0, 'period': 4, 'data_availible': 32, 'descriptor': 131073, 'upload_enabled': 0, 'data_page_id': 67, 'data': '', 'status_2': 0, 'status_1': 36}
[MainThread] 2012-05-12 13:32:57,655 INFO Device has data. Linking.
[MainThread] 2012-05-12 13:32:57,655 DEBUG Setting period to match device, hz=8
[MainThread] 2012-05-12 13:32:57,663 DEBUG Linking with device. freq=2420mhz
[Thread-1] 2012-05-12 13:32:57,860 WARNING Failed to receive RF beacon at expected period. channel_number=0
[MainThread] 2012-05-12 13:32:58,039 INFO Pairing with device.
[MainThread] 2012-05-12 13:32:58,279 DEBUG Got client auth string. Auth{'auth_string': '', 'beacon': <antd.antfs.Beacon object at 0xd5eed0>, 'op_id': None, 'response_type': 1, 'client_id': 3841895342, 'host_id': 2986, 'data_page_id': 68, 'command_id': 132}
[MainThread] 2012-05-12 13:32:58,279 DEBUG Device unkown, requesting pairing.
[Thread-1] 2012-05-12 13:33:00,235 WARNING Failed to receive RF beacon at expected period. channel_number=0
[Thread-1] 2012-05-12 13:33:00,360 WARNING Failed to receive RF beacon at expected period. channel_number=0
[Thread-1] 2012-05-12 13:33:00,485 WARNING Failed to receive RF beacon at expected period. channel_number=0
[Thread-1] 2012-05-12 13:33:00,610 WARNING Failed to receive RF beacon at expected period. channel_number=0
[Thread-1] 2012-05-12 13:33:00,735 WARNING Failed to receive RF beacon at expected period. channel_number=0
[Thread-1] 2012-05-12 13:33:00,860 WARNING Failed to receive RF beacon at expected period. channel_number=0
[Thread-1] 2012-05-12 13:33:00,985 WARNING Failed to receive RF beacon at expected period. channel_number=0
[Thread-1] 2012-05-12 13:33:01,110 WARNING Failed to receive RF beacon at expected period. channel_number=0
[Thread-1] 2012-05-12 13:33:01,235 WARNING Failed to receive RF beacon at expected period. channel_number=0
[Thread-1] 2012-05-12 13:33:01,360 WARNING Failed to receive RF beacon at expected period. channel_number=0
[Thread-1] 2012-05-12 13:33:01,485 WARNING Failed to receive RF beacon at expected period. channel_number=0
[Thread-1] 2012-05-12 13:33:01,610 WARNING Failed to receive RF beacon at expected period. channel_number=0
[Thread-1] 2012-05-12 13:33:01,735 WARNING Failed to receive RF beacon at expected period. channel_number=0
[Thread-1] 2012-05-12 13:33:01,860 WARNING Failed to receive RF beacon at expected period. channel_number=0
[Thread-1] 2012-05-12 13:33:01,985 WARNING Failed to receive RF beacon at expected period. channel_number=0
[Thread-1] 2012-05-12 13:33:02,111 WARNING Channel dropped to search do to too many dropped messages. channel_number=0
[Thread-1] 2012-05-12 13:33:12,001 WARNING RF channel timed out searching for device. channel_number=0
[MainThread] 2012-05-12 13:33:12,024 WARNING Caught error while communicating with device, will retry.
Traceback (most recent call last):
File "/home/dragor/src/python-ant-downloader/antd/main.py", line 89, in downloader
client_id = host.auth(pair=not args.daemon)
File "/home/dragor/src/python-ant-downloader/antd/antfs.py", line 386, in auth
auth_reply = Auth.unpack(self.channel.read(timeout))
File "/home/dragor/src/python-ant-downloader/antd/ant.py", line 883, in read
return self._session._send(ReadData(self.channel_number, ReadData), timeout=timeout).data
File "/home/dragor/src/python-ant-downloader/antd/ant.py", line 645, in _send
raise cmd.error
AntChannelClosedError: Channel closed. CHANNEL_EVENT(channel_number=0, msg_id=1, msg_code=7)
This just repeats 5 times and the program exits. I've tried this on two different systems and I get the same errors.
Hi,
First thing to try: make sure the gps watch is awake (press a button), at least my watch will not accept pairing requests while its asleep.
If that doesn't work, re-run with verbose (-v) option and reply with results.
Regards,
I am happy to report that this issue is invalid. I was able to connect to the device and download all of the data. I'm guessing that it wasn't on, or was just too far to connect to it.
Thanks for writing this software! It's very useful.