All:
Still getting the Wisp error message: "Directory request error NO -5" after uninstalling the program. There must be traces of Wisp left in the registry so the next step is to do a thorough deletion.
The only reference to this error in the amsat-bb archives points to the "Test for SMACK" setting which is unchecked. Apparently, the nature of the error has something to do with directory requests so I'm wondering if there's a way to solve the problem via Wisp housekeeping?
Any suggestions before I go through a tedious deletion process?
Tony -K2MO
All:
Wisp is showing the following error when accessing Falconsat-3: "Directory request error NO -5 K2MO"
I searched the archives and it seems this error takes place if the parameter "Test for SMACK TNC" is checked which is not the case here.
Any suggestions?
Tony -K2MO
Edson sent this to the list back on 10/20:
"Thank you to everyone that has contacted me privately.
Last night I installed Windows 7 32-bits and WISP on a virtual machine and to my surprise, the problem I have been having persisted. After a lot of hair pulling (not much left anyway) and investigation, I found that the culprit was neither Windows nor WISP. It was the serial to TCP bridge HW VSP software. If the NVT option of HW VSP is enabled, it inserts some control data in the data stream when it finds some pattern on the input data stream. In the case of a dir fill, it was introducing three 0xFF bytes right in middle of the KISS frame. This was being sent over AX.25 to Falconsat-3 and was the cause of the "NO -5" error.
I've tested requesting a dir fill during the last pass here and Falconsat-3 replied with a nice "OK PY2SDR"! Now let's grab some headers and try to upload a small file.
73, Edson PY2SDR"
Hope this helps.
73, Drew KO4MA
-----Original Message----- From: AMSAT-BB [mailto:amsat-bb-bounces@amsat.org] On Behalf Of Tony Sent: Wednesday, December 27, 2017 2:39 PM To: amsat-bb@amsat.org Subject: [amsat-bb] Update: Falconsat-3 Wisp Error NO -5
All:
Still getting the Wisp error message: "Directory request error NO -5" after uninstalling the program. There must be traces of Wisp left in the registry so the next step is to do a thorough deletion.
The only reference to this error in the amsat-bb archives points to the "Test for SMACK" setting which is unchecked. Apparently, the nature of the error has something to do with directory requests so I'm wondering if there's a way to solve the problem via Wisp housekeeping?
Any suggestions before I go through a tedious deletion process?
Tony -K2MO
All:
Wisp is showing the following error when accessing Falconsat-3: "Directory request error NO -5 K2MO"
I searched the archives and it seems this error takes place if the
parameter "Test for SMACK TNC" is checked which is not the case here.
Any suggestions?
Tony -K2MO
_______________________________________________ Sent via AMSAT-BB@amsat.org. AMSAT-NA makes this open forum available to all interested persons worldwide without requiring membership. Opinions expressed are solely those of the author, and do not reflect the official views of AMSAT-NA. Not an AMSAT-NA member? Join now to support the amateur satellite program! Subscription settings: http://www.amsat.org/mailman/listinfo/amsat-bb
Andrew:
If the NVT option of HW VSP is enabled, it inserts some control data in the data stream
Talk about coincidence...
I was comparing my notes and going over the UZ7HO modem setup as well as VSP setup when your message came through -- just worked a Falconsat with the VSP NVT disabled and all is fine.
Thanks, Tony -K2MO
All:
Just a reminder for those using Wisp, HW VSP and the UZ7HO modem to work Falconsat:
Make sure NVT is disabled under the VSP settings tab. If enabled, it will send unwanted data to the satellite causing the directory request error no -5 that I was experiencing.
Tony -K2MO
Glad you got it going Tony. It's good to see you on the PB :-)
73 Jeff kb2m
-----Original Message----- From: AMSAT-BB [mailto:amsat-bb-bounces@amsat.org] On Behalf Of Tony Sent: Wednesday, December 27, 2017 5:03 PM To: amsat-bb@amsat.org Subject: [amsat-bb] Falconsat-3 Wisp Error NO -5: Solved
All:
Just a reminder for those using Wisp, HW VSP and the UZ7HO modem to work Falconsat:
Make sure NVT is disabled under the VSP settings tab. If enabled, it will send unwanted data to the satellite causing the directory request error no -5 that I was experiencing.
Tony -K2MO
participants (3)
-
Andrew Glasbrenner
-
jeff griffin
-
Tony