Date   

wsjt-x and Odyssey 2

Kurt Poulsen
 

Hi All
Have anybody used the Ody 2 with wjst-x / FT8 and found a way to interface. I have only seen a possibility to use a second sound card (USB) and vox controlled operation.
I use SDR Console which work great with Ody2
Kind regards
Kurt de OZ7OU


Re: Ody II ANP 1.11 IP problem

David Fainitski
 

Hello, Kurt

3.3 Votls is full scale.

For power 100 Watt and less just copy the schematic HFPU-100.

David


Re: Ody II ANP 1.11 IP problem

Kurt Poulsen
 

Hello David

Problem solved. You wrote Python 2.xx needed but it is Phyton 2.7.x which is needed. I noticed in you document about the boot loaded was written in Phyton 2.7.h so that got my “brain to tick”. The windows installer for Phyton 2.7.8 was the one I used and the everything went smooth the Odyssey 2 wat found clicking on test and the default IP programmed subsequently successfully.
I have maybe a hint why the fault happened. I probably did not disconnected the Odyssey 2 via the center key on the microphone or the power on/switch on the radio but abruptly took the AC power to the 220V AC to 12V DC adaptor.

Thank you for your support David to get me “back in space”.

By the way.. what is the nominal / max input voltage for ADC1 and ADC2 as I want to make a SWR/Power detector like the one you have in the HFPU-100 PA stage

Kind regards

Kurt

 

Fra: ody-sdr@groups.io <ody-sdr@groups.io> På vegne af David Fainitski
Sendt: 21. marts 2019 15:06
Til: ody-sdr@groups.io
Emne: Re: [ody-sdr] Ody II ANP 1.11 IP problem

 

Hello, Kurt
Connect headphones to KEY connector and turn a power on.
bootloader 2.0 should indicate on the display all the time
after that the default IP will be valid.

David


Re: Ody II ANP 1.11 IP problem

Kurt Poulsen
 

Hi David

Thank you, the Odyssey run alright in Bootloader mode, but to get the Bootloader_2.0.pyw up and running is quite a challenge. The Python 2.3.5 installed (windows installer version) but clocking on the Bootloader_2.0.pyw does not get it to start. Opening with Pythonw dos not help either. What is the catch. Sorry I am a window guy so a bit helpless

Kind regards

Kurt

 

Fra: ody-sdr@groups.io <ody-sdr@groups.io> På vegne af David Fainitski
Sendt: 21. marts 2019 15:06
Til: ody-sdr@groups.io
Emne: Re: [ody-sdr] Ody II ANP 1.11 IP problem

 

Hello, Kurt
Connect headphones to KEY connector and turn a power on.
bootloader 2.0 should indicate on the display all the time
after that the default IP will be valid.

David


Re: Ody II ANP 1.11 IP problem

David Fainitski
 

Hello, Kurt
Connect headphones to KEY connector and turn a power on.
bootloader 2.0 should indicate on the display all the time
after that the default IP will be valid.

David


Re: Ody II ANP 1.11 IP problem

Kurt Poulsen
 

Hello David

Thank for a prompt reply. How do I run the Odyssey in Bootloader mode 😊

Kind regards

Kurt

 

Fra: ody-sdr@groups.io <ody-sdr@groups.io> På vegne af David Fainitski
Sendt: 21. marts 2019 04:32
Til: ody-sdr@groups.io
Emne: Re: [ody-sdr] Ody II ANP 1.11 IP problem

 

Hello, Kurt

The IP address was reset to zero and I don't know why at this moment.

Bootloader starts with the default IP 192.168.2.160 but for working firmwares zero IP meaning that DHCP is enabled.

For resolve this problem run your Odyssey in bootloader mode and change IP address with the Bootloader_2.0.pyw program (Python 2.xx needed)

You should change the IP even if you use default 192.168.2.160 IP address. Just rewrite it.

Will look forward to news.

David


Re: Ody II ANP 1.11 IP problem

David Fainitski
 

Hello, Kurt

The IP address was reset to zero and I don't know why at this moment.

Bootloader starts with the default IP 192.168.2.160 but for working firmwares zero IP meaning that DHCP is enabled.

For resolve this problem run your Odyssey in bootloader mode and change IP address with the Bootloader_2.0.pyw program (Python 2.xx needed)

You should change the IP even if you use default 192.168.2.160 IP address. Just rewrite it.

Will look forward to news.

David


Ody II ANP 1.11 IP problem

Kurt Poulsen
 

After having enjoyed my new Ody 2 for a week with both OpenHPSDR Thetis and SDR Console v.3.06 both with RX and TX functioning I suddenly experience the none of the two application can initiate the radio. Switching power on Ody 2 reports ANP 1.11 and IP 192.168.2.160 and trying to ping 192.168.2.160 from a command prompt I get the message "Reply from 192.168.2.100: Destination host unreachable" but also the 4 packet sent and 4  packets received Lost=0 (I use CAT6 LAN cable between PC and Ody 2 and as said it worked earlier to day  with my fixed IP pc at 192.168.2.200 I just changed  to 192.168.2.100 to see if it made any change.

So a good hint what to do is appreciated

Kind regards
Kurt de OZ7OU 


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

Neoklis Kyriazis
 

OK David, thanks. I will get the gadgets and restore the device later.

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


Re: Odyssey-2 in Linux - Report

Neoklis Kyriazis
 

Hello, Neoklis.
Hello David,

. 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.
No, this configuration works only with direct connection to PC. If you are
using router's connection, you should install parameters defined router's
settings.
Well, it actually worked, via the WiFi router, with both static IP and DHCP,
e.g. I had discovery from my computer with both cases.

I then tried to connect with Ody using the direct Ethernet connection
but with DHCP
For what ? With direct connection easier to work with static IP .
Well, I could never get it to work with a static IP and direct connection, and
I just could not find out why. Must be something I was not configuring right.
I could get ping to work but not discovery.

It is not necessary but preferably. The hardware are cheap.
I am not concerned about the cost, its the trouble I always have with
customs and couriers, when importing anything other than bananas or
bathroom scales.... Someone here knows what I am talking about, still!

But I will now have to do this and I presume install Windows somewhere so
that I can use the relevant software tools to do the job.

No, you can't. The bootloader and firmware should be the same versions.
Yeah, I think this is why I bricked the Ody. Can I expect it to recover if I flash
the right boot loader and firmware?

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


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

David Fainitski
 

Sorry

This happened because you have destroyed  Bootloader in FPGA firmware.

The MCU wait for an answer from Bootloader but nothing receives.

You need restore old bootloader with  Altera Byte Blaster

David


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

David Fainitski
 

Hello, Neoklis

That is funny.

Odyssey is power on now but OLED is clear because bootloader, MCU fw and the main FW are different.

Now you should use Altera Byteblaster programmer for return the main firmware to previous version.

Also, if you would have Pickit 3 programmer you could update MCU FW and use Bootloader 2.0 and the latest firmware.

Read my previous reply in other topic

David


Re: Odyssey-2 in Linux - Report

David Fainitski
 


Hello, Neoklis.

. 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.
No, this configuration works only with direct connection to PC. If you are using router's connection, you should install parameters defined router's settings.

I then tried to connect with Ody using the direct Ethernet connection but with DHCP

For what ? With direct connection easier to work with static IP .

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.

It is not necessary but preferably.
the hardware are cheap.
https://www.ebay.com/itm/5EC9-Universal-PICkit3-PICkit2-USB-Debugger-Programmer-Emulator-PIC-Controller/163431362801?hash=item260d44b0f1:m:mpX6FhOvpNoQj3crh9LEAnA:rk:1:pf:0

https://www.ebay.com/itm/USB-Blaster-ByteBlaster-Cable-Kit-For-Altera-CPLD-FPGA-Programmer/113314595538?hash=item1a621382d2:g:y6sAAOSwq9RbxvN6:rk:2:pf:0

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

No, you can't. The bootloader and firmware should be the same versions.

 If not, will it be more likely to succeed with a static IP and with a direct Ethernet-to-Ethernet connection?

You can use  DHCP or static IP addressing with any firmware versions.
Just use correct settings for success.

Best regards, David.


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

841 - 860 of 1425