k2po
New Member
Posts: 2
|
Post by k2po on Apr 21, 2009 10:24:23 GMT -5
I'd not used my AIM 4170C for a while. Today I got it out. Laptop recognized its port OK, and last scan came up. But when I tried to do a scan, I got "No signal at <start frequency> Error Code= 13270 ***"
'Anyone know: what's that about?
/Bill, K2PO
|
|
|
Post by Bob on Apr 21, 2009 16:31:32 GMT -5
This indicates the data from the AIM appeared to be invalid (maybe all zeros). This can be caused by a communication problem. Check the version info (Help -> About) to see if that looks reasonable. It should show the firmware version, date and time in the dialog window.
-73/Bob
|
|
k2po
New Member
Posts: 2
|
Post by k2po on Apr 21, 2009 21:37:08 GMT -5
The Help menu gives valid-looking data, i.e., 4170c ver 5.6 date=dec 12 2008 10:47:13 ID= 72435542
But I still get the "No signal at 3.400 Error Code= 13270***" message when I try to do a scan.
If I select Calibrate/Analyzer and start, I get "Error Code = 13272" and "**** There is no reference signal from the AIM ****"
I'm thinking it might be time to box it up and ship it back for some qualified trouble-shooting...
/Bill
|
|
f6gnz
New Member
Posts: 9
|
Post by f6gnz on May 9, 2009 11:20:41 GMT -5
I have exactly the same problem: "No data from I/O port, Error code 13272, reference signal is too low=0 There is no reference signal from AIM" , very often, but not everytime. S/w version 684a and AIM4170C s/n 3106 !
|
|
|
Post by kb7vms on Jul 21, 2009 9:38:26 GMT -5
That is exactly the same problem i see. Have tried 4 different usb to serial interfaces, 3 computers. currently working to get my Dell Studio computer running vista Pro 64 bit and Aim 4170 s/n 3046 running. Manual control using a terminal program called Putty works ok at 57600 baud. Just seems I am so close.......
|
|
w0qe
Junior Member
Posts: 67
|
Post by w0qe on Jul 22, 2009 0:32:12 GMT -5
I also have seen the "reference signal too low" message many times. I had bought 10 Prolific chip set USB to RS-232 adapters when CompUSA closed their local store. The driver that I used was the problem even though the driver was for the correct operating system. It took a while to figure this out but small amounts of data (Help->about) seemed to work fine but larger amounts (such as a scan) occasionally failed with the error message. I ended up buying some FTDI chip set adapters and the problem went away. However recently I found a new driver for the Prolific chip set adapters and now those adapters work flawlessly.
I did some snooping around with a scope and it appeared that when transferring small amounts of data the "remainder" data that is smaller that the buffer gets dumped quickly but when transferring larger amounts of data this this partial buffer sometimes did not get dumped to the PC for a few hundred ms. The old 8250/16550 type UARTS would always dump the buffer after something like 8 or 16 characters worth of time. Perhaps there is something in the 4170 software that times out but this is just a guess. Bottom line is look for a new driver before boxing up the 4170.
73, Larry, W0QE
|
|
g3nrw
Junior Member
Posts: 54
|
Post by g3nrw on Jul 23, 2009 3:37:58 GMT -5
However recently I found a new driver for the Prolific chip set adapters and now those adapters work flawlessly. Larry, I too have had occasional malfunction of the Prolific USB/serial port. Where did you find the driver? -- 73 Ian, G3NRW
|
|
w0qe
Junior Member
Posts: 67
|
Post by w0qe on Jul 23, 2009 21:06:46 GMT -5
|
|
ne8r
New Member
Posts: 2
|
Post by ne8r on Aug 8, 2010 11:25:15 GMT -5
Just loaded AIM_700B.exe after a 2 year hiatus on a different computer. Fired up the AIM 4170c and received the Error 13270 intermittently during calibration. After several attempts, calibration was complete but not error free. While scanning, again I received the error intermittently. I dug into the comm 1 port speed set at 9600 (default) and first slowed to 4800 (no good), then up to 57,600. All was good for a while. Unfortunately, the problem restarted after many scans. I ended up purchasing a USB to RS-232 adapter. Installed drivers (not smoothly) and plugged in the unit. All is good now after repeated scans, restarts on the AIM software, and reboots. I'll add specifics on the adapter later. I post my scans at antennagraphs.comRobert, NE8R Dell D610, Win XP
|
|