Odyssey-2 in Linux, some progress
Looks like my home work has paid off some, but not all! ;-)
With the help from this group and my distro's forum, I was able to connect
with Ody-2 and to give it a static IP of 192.168.2.160/24, the default. I
got this far by connecting Ody into my ISP's router and accessing it via my
WIFI connection. I used HPSRProgrammer_v2_nopcap to discover Ody and to give
it its default static IP address, which is now permanently stored in it.
I was also able to comm with it using both ghpsdr and linhpsdr apps which
discovered it OK but I didn't try to work Ody because ghpsdr crashes with
a segfault, apparently due to some bug in the GUI, and the streaming rate
apparently not high enough via my WIFI.
Anyhow, the important thing is that I got somewhere! :-)
I then tried a direct connection to my computer's Ethernet port. After some
experimentation with settings, I can ping Ody OK and it is also listed by:
# nmap -sT 192.168.2.100/24
Starting Nmap 7.70 ( https://nmap.org ) at 2019-02-17 09:09 EET
Nmap scan report for 192.168.2.160 (192.168.2.160)
Host is up (0.00013s latency).
All 1000 scanned ports on 192.168.2.160 (192.168.2.160) are filtered
MAC Address: 00:1E:C0:A5:F4:7E (Microchip Technology)
Nmap scan report for 192.168.2.100 (192.168.2.100)
Host is up (0.00035s latency).
Not shown: 999 closed ports
PORT STATE SERVICE
22/tcp open ssh
Nmap done: 256 IP addresses (2 hosts up) scanned in 31.27 seconds
# ping 192.168.2.160
PING 192.168.2.160 (192.168.2.160) 56(84) bytes of data.
64 bytes from 192.168.2.160: icmp_seq=1 ttl=128 time=0.101 ms
64 bytes from 192.168.2.160: icmp_seq=2 ttl=128 time=0.190 ms
64 bytes from 192.168.2.160: icmp_seq=3 ttl=128 time=0.194 ms
64 bytes from 192.168.2.160: icmp_seq=4 ttl=128 time=0.165 ms
64 bytes from 192.168.2.160: icmp_seq=5 ttl=128 time=0.166 ms
64 bytes from 192.168.2.160: icmp_seq=6 ttl=128 time=0.192 ms
--- 192.168.2.160 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 143ms
rtt min/avg/max/mdev = 0.101/0.168/0.194/0.032 ms
However, alas, all above apps (HPSRProgrammer, ghpsdr, linhpsdr) will not
discover Ody so again I am stuck.
So, any new hints/advise will be much appreciated, I just can't give up on
Glad you have it running.toggle quoted messageShow quoted text
I use mine with linhpsdr on x86_64 openSUSE at 1536K samplerate with ANP firmware. I used pihpsdr on aarch64 nanoPi Fire3 as linhpsdr crashed.
If and when quisk supports Gigabit Ethernet, it would be my preferred application for Hermes, Hermes-Lite2 and ODY-2.
73 ... Sid.
On 17/02/2019 07:20, Neoklis Kyriazis via Groups.Io wrote:
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support
Senior Staff Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks
According to openHPSDR protocol, programs will search Odyssey with non-direction broadcast packets and this will not to work trough Wi-Fi and non-Wi-Fi routers.
For approach the result you should connect your Odyssey directly to your PC.
At least for the first time.
Hello, NeoklisHello David
According to openHPSDR protocol, programs will search Odyssey withWell, actually for me it worked the other way round: I have the Ody as it
was shipped, with the AOP 1.10 firmware and I could not get it to work with
a direct connection to my PC. Of course it could have been my mistakes to
blame. But when I connected the Ody to my ISP's router, I was able to access
Ody with the HPSDRProgrammer_v2_nopcap and gave Ody the default static
IP of 192.168.2.160. I could also access Ody with both ghpsdr and linhpsdr, via
the router and through the WIFI connection of my PC to the router.
Now with the static IP I was able to access Ody with the ping command, after
I followed your instructions: I gave the PC's Ethernet port a static IP of
192.168.2.100/24 and 100Mb/Full Duplex setting. ping 192.168.2.160 now
works well but the other apps don't discover Ody. I think ping works because
I specify the IP address but other apps have to do discovery and this is where
I have the problem, I don't know what else I have to do to make discovery
work over the direct Ethernet connection.
Anyhow, I have learned a few things about LANs at least!
Neoklis - Ham Radio Call:5B4AZ