Date   

Wow! I bricked my Odyssey-2! :-(

Neoklis Kyriazis
 

Guess I should have expected it, fiddling with it too much...

Anyhow, I tried upgrading the original Ody-2 from AOP-1.10 to AOP-1.11 using HPSDRProgrammer. The firmware file was (apparently) uploaded OK but the the Odyssey would remain dead, would not power-on the next time I switched it on. It also did not respond after the "upgrade".

With my limited knowledge, I suspect the problem may be the original boot loader will not boot the new firmware. I was afraid that might happen but didn't expect the device to go completely dead.

So (David), is there a way to recover from the bricked state? Perhaps getting hold of the programmers and re-flashing the boot loader and firmware?

Thanks in advance for helping.

--
Best Regards
Neoklis - Ham Radio Call:5B4AZ
http://www.5b4az.org/


Odyssey-2 in Linux - Report

Neoklis Kyriazis
 

Hi all,

Spent some spare time lately to continue my efforts to run the Odyssey-2 in Linux, with a direct connection to the Ethernet port. This is an unmodified unit with the original firmware as was supplied when it went into production. I has the original boot loader and AOP-1.10 firmware.

I first tried to run Ody-2 with a direct Ethernet connection but it would not work. I then connected it to my ISP's router and was able to access it via the WiFi connection and I used  HPSDRProgrammer-v2-nopcap to give Ody the default static IP of 192.168.2.160 and the computer's port the static IP of 192.168.2.100, as advised by David. However, every effort and every info I found on the Web failed to make it work. I could only get the ping tool to work successfully but not discovery by any software.

I then tried to connect with Ody using the direct Ethernet connection but with DHCP, so I used the programmer with a connection to the router to reset Ody-2 to work with DHCP. After much effort and experiment, I succeeded to have the Odyssey-2 respond to ping and be discovered by both the programmer and ghpsdr so that now I have a chance to actually run Ody-2.

There is however a catch - Odyssey-2 will only work with DHCP if the following sequence is followed:

1. Set up the O/S dhcpcd service to separately set up WiFi and Ethernet.

2. Use ethtool -s eth0 speed 100 duplex full autoneg off to set up the port.

3. Switch on Odyssey _after_ starting the computer (and the dhcp service) so that (apparently) Odyssey makes a DHCP request when the dhcpcd server is ready.

This is fair enough, better than having to work with a router or switch but I would prefer to make it all work without manual operations every time. I have added the ethtool command to the rc.local int script and that is done at boot time. Also set up Void Linux's "runit" init system to run dhcpcd separately at boot time so all that is left is the need to switch on Ody after boot is finished.

So, having got this far, I feel that I should try to upgrade Ody-2 to newer firmware but I rather not go as far as importing the needed hardware to reprogram with the new boot loader, since the necessary software will not run on Linux anyhow.

So I would like to ask, can I safely upgrade the AOP-1.10 firmware to the latest available, using only the HPSDRprogrammer and existing boot loader, and if so, will it work with a non-static IP address (under DHCP)? If not, will it be more likely to succeed with a static IP and with a direct Ethernet-to-Ethernet connection?

Apologies for the long post, but its been a much much longer effort to get this far! ;-)

Thanks!

--
Best Regards
Neoklis - Ham Radio Call:5B4AZ
http://www.5b4az.org/


Re: Ody II ANP 1.11 IP /Thetis configuration

David Fainitski
 

On Mon, Feb 25, 2019 at 11:31 PM, Jan Verduyn wrote:
This Ody II - IP address is shown as  169.254.106.213
Hello, Jan

This IP is show on ODY OLED display while starting ?
So you did programmed this IP Odyssey earlier, the default IP is 192.168.2.160
For direct connection to PC no sense to change the default IP 
Only if you use LAN switch and you are forced to use specific IP for other devices.

David


Re: Ody II ANP 1.11 IP /Thetis configuration

Jan Verduyn
 

David,

 

Thanks for our advice. It now works.

When reconfigured to your recommended settings for ANP 1.11 and with direct ethernet cable 1Gb ethernet works reliably on Windows 10 and Windows 7 Ps

Quote

ANP firmware works only with Gigabit Ethernet.
TCP/IP V4 connection should be set to static IP 192.168.2.100 and mask by default 255.255.255.0
unquote

 

Should the Static IP settings be the same for a second Ody II with ANP 1.10?


I am getting a reliable connection with  config set to  “Reuse last IP address” and “Network Watchdog” set

This Ody II - IP address is shown as  169.254.106.213  with IP4 connection IP address 169.254.207.146 and mask 255.255.0.0.   
Does this make sense?

I ask this in case it would help other Ody II owners with ANP1.10.

 

73

 

Jan


Re: Ody II ANP 1.11 IP /Thetis configuration

David Fainitski
 

On Tue, Feb 19, 2019 at 02:43 PM, Jan Verduyn wrote:
The Ethernet adapter is configured for 100 Mbps  and link enabled.
???
ANP firmware works only with Gigabit Ethernet.
TCP/IP V4 connection should be set to static IP 192.168.2.100 and mask by default 255.255.255.0

David


Re: Ody II ANP 1.11 IP /Thetis configuration

Neoklis Kyriazis
 

Hi

There is some information here that in general might be useful:


--
Best Regards
Neoklis - Ham Radio Call:5B4AZ
http://www.5b4az.org/


Re: Ody II ANP 1.11 IP /Thetis configuration

AA6I Stan
 

I just looked at mine as I also use Thetis. Mine is uses Anan 10E . I did a lot of fiddling to get mine going but as I recall I used a static address also on the PC adapter. You also need to be running at Gigabit speeds as I understand ODY II does not do 100Mbps .


AA6I

On 2/19/2019 2:43 PM, Jan Verduyn wrote:

I am attempting to configure a new Ody II for a friend on a Windows 7 PC.  Despite many hours of trying this has not been successful. 
This Ody II  has ANP 1.11 installed in slot 1 and when switching on it shows it's IP address is 192.168.2.160  
The PC runs windows 7 OS. Software is Thetis v2.6.0.   

A direct Ethernet cable connection between PC and Ody II is used.  The Ethernet adapter is configured for 100 Mbps  and link enabled.   LAN status shows that packets are being sent but no packets are being returned.
Thetis setup screen is configured  "Enabled Static IP Address"  "Anan-100D"  with IP address 192.168.2.160 entered.

When starting up Thetis  an error is shown  "Unhandled exception has occurred in your application"
A socket operation was attempted to an unreachable network.  
Changing Thetis configuration to "Use last IP address" and restarting Thetis shows

Pinging Ody's IP address gives response "unreachable network".
Can somebody please provide a screenshot what the correct configuration is for Thetis on Windows 7 for  ANP1.11.

 Many thanks  Jan


Ody II ANP 1.11 IP /Thetis configuration

Jan Verduyn
 

I am attempting to configure a new Ody II for a friend on a Windows 7 PC.  Despite many hours of trying this has not been successful. 
This Ody II  has ANP 1.11 installed in slot 1 and when switching on it shows it's IP address is 192.168.2.160  
The PC runs windows 7 OS. Software is Thetis v2.6.0.   

A direct Ethernet cable connection between PC and Ody II is used.  The Ethernet adapter is configured for 100 Mbps  and link enabled.   LAN status shows that packets are being sent but no packets are being returned.
Thetis setup screen is configured  "Enabled Static IP Address"  "Anan-100D"  with IP address 192.168.2.160 entered.

When starting up Thetis  an error is shown  "Unhandled exception has occurred in your application"
A socket operation was attempted to an unreachable network.  
Changing Thetis configuration to "Use last IP address" and restarting Thetis shows

Pinging Ody's IP address gives response "unreachable network".
Can somebody please provide a screenshot what the correct configuration is for Thetis on Windows 7 for  ANP1.11.

 Many thanks  Jan


Re: Odyssey-2 in Linux, some progress

Neoklis Kyriazis
 

Hello, Neoklis
Hello David

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.
Well, 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!

--
Best Regards
Neoklis - Ham Radio Call:5B4AZ
http://www.5b4az.org/


Re: Odyssey-2 in Linux, some progress

David Fainitski
 

Hello, Neoklis

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.

David 


Re: Odyssey-2 in Linux, some progress

Sid Boyce
 

Glad you have it running.
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:
Hi all,

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

Also by:
# 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
^C
--- 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
this!
--
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


Odyssey-2 in Linux, some progress

Neoklis Kyriazis
 

Hi all,

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

Also by:
# 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
^C
--- 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
this!


Re: Odyssey-2 on Linux

Neoklis Kyriazis
 

The default IP of Odyssey is 192.168.2.160
Thanks David. I will be trying again later once I am better prepared about
networking and finishing seasonal chores, and nursing my dog. Had an
operation to clear that large abscess on its cheek.

--
Best Regards
Neoklis - Ham Radio Call:5B4AZ
http://www.5b4az.org/


Re: Odyssey-2 on Linux

David Fainitski
 

The default IP of Odyssey is 192.168.2.160


Re: Odyssey-2 on Linux

Sid Boyce
 

OK. After using ethtool, check
ifconfig -a
ifconfig <interface> 192.168.100.1 up
ping 192.168.100.1   --- should show pings working.

ifconfig -- which should display something like this.
enp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.10.238  netmask 255.255.255.0  broadcast 192.168.10.255
        inet6 fe80::490f:3a27:6ac1:7f00  prefixlen 64  scopeid 0x20<link>
        ether 1c:6f:65:9f:5c:9e  txqueuelen 1000  (Ethernet)
        RX packets 32439609  bytes 41896916150 (41.8 GB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 14351411  bytes 9296515806 (9.2 GB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
73 ... Sid.

On 10/02/2019 07:11, Neoklis Kyriazis via Groups.Io wrote:
# ethtool -s <port> speed 100 duplex full autoneg off
73 ... Sid.
Thanks Sid, but still it didn't work. I think one problem is that I never had to do
much work on networking, save setting up WiFi, so I can't see what is wrong or
what I am doing wrong. And even if I could, I can't find the solution myself. So
giving up for now, I have a lot of chores waiting for me, so next time I have
spare time I will teach myself some networking and try again.

My thanks to all that chipped in help.

73's

--
Best Regards
Neoklis - Ham Radio Call:5B4AZ
http://www.5b4az.org/

--
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


Re: Odyssey-2 on Linux

Neoklis Kyriazis
 

# ethtool -s <port> speed 100 duplex full autoneg off
73 ... Sid.
Thanks Sid, but still it didn't work. I think one problem is that I never had to do
much work on networking, save setting up WiFi, so I can't see what is wrong or
what I am doing wrong. And even if I could, I can't find the solution myself. So
giving up for now, I have a lot of chores waiting for me, so next time I have
spare time I will teach myself some networking and try again.

My thanks to all that chipped in help.

73's

--
Best Regards
Neoklis - Ham Radio Call:5B4AZ
http://www.5b4az.org/


Re: Odyssey-2 on Linux

Sid Boyce
 

In Linux

# ethtool -s <port> speed 100 duplex full autoneg off
73 ... Sid.

On 09/02/2019 20:20, David Fainitski wrote:
Hello, Neoklis

For now you should set up your PC Ethernet connection to Static IP with 192.168.2.100 address and 255.255.255.0 subnet mask.

Also you should set the 100M Full Duplex  mode on your network card ( I don;t know how to in Linux).

After that your Odyssey will be visible for SDR programs with 192.168.2.160 IP (Static IP)

Read this document https://apache-labs.com/downloadsfiles/1003_ANAN-100-Users-Guide.pdf

If you have changed firmware to ANP version, this manual will be helpful
https://apache-labs.com/download_file.php?downloads_id=1010

David
--
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


Re: Odyssey-2 on Linux

Neoklis Kyriazis
 

Thanks David! I will try that tomorrow and see what happens. For now
I am watching over my little dog - she got a sting from something and
she has a huge bulge on her cheek. Luckily  my vet agreed to an
emergency call and she is getting better! :-)

--
Best Regards
Neoklis - Ham Radio Call:5B4AZ
http://www.5b4az.org/


Re: Odyssey-2 on Linux

David Fainitski
 

Hello, Neoklis

For now you should set up your PC Ethernet connection to Static IP with 192.168.2.100 address and 255.255.255.0 subnet mask.

Also you should set the 100M Full Duplex  mode on your network card ( I don;t know how to in Linux).

After that your Odyssey will be visible for SDR programs with 192.168.2.160 IP (Static IP)

Read this document https://apache-labs.com/downloadsfiles/1003_ANAN-100-Users-Guide.pdf

If you have changed firmware to ANP version, this manual will be helpful
https://apache-labs.com/download_file.php?downloads_id=1010

David 


Re: Odyssey-2 on Linux

Neoklis Kyriazis
 

Isaac

I already tried the boot loader under different settings etc but no joy.
There must be some fundamental problem that I don't understand
because of limited knowledge of networking.

--
Best Regards
Neoklis - Ham Radio Call:5B4AZ
http://www.5b4az.org/

761 - 780 of 1332