I will introduce the method of downloading and uploading the signals from
FalconSAT-3 via WiSP, SoundModem and VSP3 without using Hard_TNC and SDR,
on Windows10 (64bit) including examples that I did not succeed it.
I will introduce them in time series here.
----------------------------------------------------------------------------------
From: Andy UZ7HO
To: JE9PEL
Date: Sat, 7 Oct 2017 06:38:58 +0300
Finally I got it!
WISP32 does not work correctly with VSPE driver, I replaced it with
HW_VSP3. Soundmodem does not support KISS over COM port, only TCP/IP
operations. HW_VSP3 driver emulates a bridge between COM and TCP.
I added "Full-Duplex" option to the main version of HS_Soundmodem 019,
you can find the "Full-duplex mode" check box in the "Modem" settings.
This option is configured separately for two channels.
----------------------------------------------------------------------------------
I remembered that I previously used VSPM (VSP_Manager) on Windows 8.1 and installed VSPM
on Windows10 64bit as well. I could receive with HS_Soundmodem without using TNC and SDR.
But the received data does not enter into MSPE and it does not work the sending operation.
TS-790S
WiSP3215
VSP-Manager103
HS_SoundModem0.19b, Full-duplex mode
----------------------------------------------------------------------------------
Because there was an information that WiSP is incompatible with the virtual software
VSPE and VSPM, I uninstalled both of them. I reinstalled HW_VSP3 which is said to be
compatible only with WiSP. I can install and run it, but it's closed by an error message.
----------------------------------------------------------------------------------
HW_VSP3 was recognized without difficulty in another Windows10, 64 bit desktop PC.
It could generate a virtual COM port and it could generate the virtual COM port.
Why can not I install in My_Windows 10, 64 bit note type PC ?
Is this the security or firewall problem ?
----------------------------------------------------------------------------------
Received using "WiSP SoundModem and HW_VSP3" by JA0CAW on 11 Oct 2017.
I, JE9PEL theoretically should be able to receive and send in the same way.
----------------------------------------------------------------------------------
Successful "WiSP SoundModem and HW_VSP3"
Until now, I could not install HW_VSP3 in my equipment system: Windows 10, 64bit (English),
as I mentioned earlier, so I was always worrying. When the Japanese software often can not
be work on English version of Windows 10, I alwas was able to work these Japanese software
using the well-known "Locale Emulator(Japanese)".
HW_VSP3 driver is emulates a bridge between COM and TCP/IP. This HW_VSP3 had run brilliantly
in my system via this "Locale Emulator". This is an amazing thing. I will summarize here
because some more steps are necessary in order to link with WiSP, as the following.
1. Run HS_SoundModem Ver0.19 first.
Settings - Modems - Check "Full dupplex mode"
Settings - Devices - KISS Server Port: 8100
2. Run HW_VSP3 via Locale Emulator.
Right click - "Locale Emulator" - "Run with Application Profile".
3. Initialize HW_VSP3. This initial settings are only the beginning.
It will be effective automatically from next time.
Set in Virtual Serial Port
- Port Name: COM4, IP Address: 127.0.0.1, Port: 8100
Check in Settings Tab - Create VSP Port when HW VSP Start-up
Purge Buffers when Port is Opened
Connect to Device even if Virtual COM is closed
Check these three boxes and press "Connect Save Settings to INI file" button below.
After a while, it changes to "VSP Status: Created, LAN Status: Connected"
in the middle row, and the connection with HS_SoundModem Ver. 0.19 is completed.
4. Run WiSP(GSC) as "administrator authority" mode. (My_HP WiSP install update)
GSC - Setup - Satellite Setup - FalconSAT3 - Edit - TNC Settings
- Port: COM4, TNC Type: None
5. Setup completed. You will wait for the arrival of the satellite.
I used the saved wav file as "GSC - Tracking - Run Pass" in this experiment.
The followings are the flow chart explained above.
----------------------------------------------------------------------------------
"WiSP SoundModem and HW_VSP3" uploading
I could receive directly from FalconSAT-3 via only SoundModem and VSP3 without using
Hard_TNC and SDR. The signal data enters into MSPE and it is uploading operation.
However, the uploading signal does not enter the radio equipment.
I need to set something. (15 Oct 2017)
I could upload using the saved wav file !!!
I had forgotten to send a check in the device settings of SoundModem!
SoundModem - Settings - Devices - PTT Port - COM2
This COM 2 also is the same COM port that was set when uploading in UISS.
I probably can upload the signal directly to the satellite.
----------------------------------------------------------------------------------
VSP3 Uplink System
Subject: PTT COM port
From: Mineo Wakita
To: Andy UZ7HO
Date: Thu, 19 Oct 2017 19:34:48 +0900
I can now do transmission operation when I check "Dual PTT"
ie, "SoundModem - Settings - Devices - PTT port - Dual PTT".
When do you check "Swap COM pins for PTT" ?
Re: PTT COM port
From: Andy UZ7HO
To: Mineo Wakita
Date: Thu, 19 Oct 2017 14:11:28 +0300
Hi Mineo!
Normally for the port A the RTS pin is used, for port B is DTR pin.
The "Swap COM pins" option swaps these pins.
[Reference]
http://youtu.be/9spO1e8NVj0http://www.qsl.net/k/k4kdr//video/FS-3_demo.mp4http://www.qsl.net/k/k4kdr//video/FS-3_Settings.mp4http://www.qsl.net/py4zbz/falconsat.htmhttp://www.ne.jp/asahi/hamradio/je9pel/wispinsv.htmhttp://www.ne.jp/asahi/hamradio/je9pel/falcons3.htmhttp://www.ne.jp/asahi/hamradio/je9pel/wispvsp4.htmhttp://www.hw-group.com/products/hw_vsp/index_en.htmlhttp://www.amsat.org/wordpress/wp-content/uploads/2017/10/AMSAT-2005-WISP-guide.pdf
From: Andy UZ7HO To: JE9PEL Date: Sat, 7 Oct 2017 06:38:58 +0300 Finally I got it! WISP32 does not work correctly with VSPE driver, I replaced it with HW_VSP3. Soundmodem does not support KISS over COM port, only TCP/IP operations. HW_VSP3 driver emulates a bridge between COM and TCP. I added "Full-Duplex" option to the main version of HS_Soundmodem 019, you can find the "Full-duplex mode" check box in the "Modem" settings. This option is configured separately for two channels. ----------------------------------------------------------------------------------
I remembered that I previously used VSPM (VSP_Manager) on Windows 8.1 and installed VSPM on Windows10 64bit as well. I could receive with HS_Soundmodem without using TNC and SDR. But the received data does not enter into MSPE and it does not work the sending operation. TS-790S WiSP3215 VSP-Manager103 HS_SoundModem0.19b, Full-duplex mode ----------------------------------------------------------------------------------
Because there was an information that WiSP is incompatible with the virtual software VSPE and VSPM, I uninstalled both of them. I reinstalled HW_VSP3 which is said to be compatible only with WiSP. I can install and run it, but it's closed by an error message. ----------------------------------------------------------------------------------
HW_VSP3 was recognized without difficulty in another Windows10, 64 bit desktop PC. It could generate a virtual COM port and it could generate the virtual COM port. Why can not I install in My_Windows 10, 64 bit note type PC ? Is this the security or firewall problem ? ----------------------------------------------------------------------------------
Received using "WiSP SoundModem and HW_VSP3" by JA0CAW on 11 Oct 2017. I, JE9PEL theoretically should be able to receive and send in the same way. ---------------------------------------------------------------------------------- Successful "WiSP SoundModem and HW_VSP3"
Until now, I could not install HW_VSP3 in my equipment system: Windows 10, 64bit (English), as I mentioned earlier, so I was always worrying. When the Japanese software often can not be work on English version of Windows 10, I alwas was able to work these Japanese software using the well-known "Locale Emulator(Japanese)". HW_VSP3 driver is emulates a bridge between COM and TCP/IP. This HW_VSP3 had run brilliantly in my system via this "Locale Emulator". This is an amazing thing. I will summarize here because some more steps are necessary in order to link with WiSP, as the following. 1. Run HS_SoundModem Ver0.19 first. Settings - Modems - Check "Full dupplex mode" Settings - Devices - KISS Server Port: 8100 2. Run HW_VSP3 via Locale Emulator. Right click - "Locale Emulator" - "Run with Application Profile". 3. Initialize HW_VSP3. This initial settings are only the beginning. It will be effective automatically from next time. Set in Virtual Serial Port - Port Name: COM4, IP Address: 127.0.0.1, Port: 8100 Check in Settings Tab - Create VSP Port when HW VSP Start-up Purge Buffers when Port is Opened Connect to Device even if Virtual COM is closed Check these three boxes and press "Connect Save Settings to INI file" button below. After a while, it changes to "VSP Status: Created, LAN Status: Connected" in the middle row, and the connection with HS_SoundModem Ver. 0.19 is completed. 4. Run WiSP(GSC) as "administrator authority" mode. (My_HP WiSP install update) GSC - Setup - Satellite Setup - FalconSAT3 - Edit - TNC Settings - Port: COM4, TNC Type: None 5. Setup completed. You will wait for the arrival of the satellite. I used the saved wav file as "GSC - Tracking - Run Pass" in this experiment. The followings are the flow chart explained above.
---------------------------------------------------------------------------------- "WiSP SoundModem and HW_VSP3" uploading I could receive directly from FalconSAT-3 via only SoundModem and VSP3 without using Hard_TNC and SDR. The signal data enters into MSPE and it is uploading operation. However, the uploading signal does not enter the radio equipment. I need to set something. (15 Oct 2017) I could upload using the saved wav file !!! I had forgotten to send a check in the device settings of SoundModem! SoundModem - Settings - Devices - PTT Port - COM2 This COM 2 also is the same COM port that was set when uploading in UISS. I probably can upload the signal directly to the satellite.
---------------------------------------------------------------------------------- VSP3 Uplink System
Subject: PTT COM port From: Mineo Wakita To: Andy UZ7HO Date: Thu, 19 Oct 2017 19:34:48 +0900 I can now do transmission operation when I check "Dual PTT" ie, "SoundModem - Settings - Devices - PTT port - Dual PTT". When do you check "Swap COM pins for PTT" ? Re: PTT COM port From: Andy UZ7HO To: Mineo Wakita Date: Thu, 19 Oct 2017 14:11:28 +0300 Hi Mineo! Normally for the port A the RTS pin is used, for port B is DTR pin. The "Swap COM pins" option swaps these pins.
[Reference] http://youtu.be/9spO1e8NVj0 http://www.qsl.net/k/k4kdr//video/FS-3_demo.mp4 http://www.qsl.net/k/k4kdr//video/FS-3_Settings.mp4 http://www.qsl.net/py4zbz/falconsat.htm http://www.ne.jp/asahi/hamradio/je9pel/wispinsv.htm http://www.ne.jp/asahi/hamradio/je9pel/falcons3.htm http://www.ne.jp/asahi/hamradio/je9pel/wispvsp4.htm http://www.hw-group.com/products/hw_vsp/index_en.html http://www.amsat.org/wordpress/wp-content/uploads/2017/10/AMSAT-2005-WISP-guide.pdf
