Hi all

I am disappointed with the state of ham radio on HF (everyone, or almost, seems to be on FT8) so I am thinking of trying my hand again with amateur radio satellites. In the past I was on them with an FT847 rig, but I now have the 7000DLE so I am wondering if dual-transverter, full duplex ...

You can't make that assessment without trying at least 6 versions of the firmware. Not joking. The problem with all of the P2 firmware is that timing closure on the MAC to PHY interface is not guaranteed over all temperature ranges and serial numbers.
Well, I have gone through all the six ...

Hi

This morning all worked well right away. So more observation is needed for a final conclusion.

OK Scott

Now that you mention the possibility of the FPGA playing up, it could explain a couple of of things that I have been wondering about:
In the very beginning of this behavior, I could hear relays click even though the client app could not connect to the rig. I should have
realized this ...

I went back to v1.9 and the behavior of the rig changed, there is an alternation every 2-3 secs between
Speed: 1000Mb/s and Speed: Unknown! but after about 30 secs speed settles to 1000 Mb/s and my client works OK.
So there is a definite improvement.
Well, looks like I spoke too soon. Today I had ...

Did you try any of the other versions of the Rev. 2.0 firmware? I'm surprised you had to go all the way back to 1.9.
Actually no. I thought I had a better chance going all the way back to 1.9 to do a quick test. I am in the middle of a difficult phase in
the development of my home brew HPSDR ...

The change of the firmware brought a change of behaviour, but to speak of an improvement?
My radios are found quickly.
Well, mine was too, but this low temperature issue cropped up, and since I can't experiment with a new Ethernet tcvr chip,
I have to accept the best I can get with work rounds ...

It is entirely possible you may have to go back as far as version 1.9 to find P2 firmware that works properly on your hardware.
I went back to v1.9 and the behavior of the rig changed, there is an alternation every 2-3 secs between Speed: 1000Mb/s and
Speed: Unknown! but after about 30 secs speed ...

w-u-2-o wrote:Bottom line: it is way too early to be blaming the hardware for this problem.

Thank you Scott, that sounds good to me! I will try other firmware once I am done with some health trouble.

Hi,

have you ever used a high quality LAN cable?
Well, I bought the best I could find and I have already tried a different one but no improvement.

On a radio (7000DLE) I also had to replace the NET TRX chip, which had temperature problems like yours.
So it looks like a possible problem of the ...

Hi All

I am again experiencing failures with the Ethernet connection of my ANAN-7kDLE
MkII radio. In the morning when the rig is cold, an Ethernet connection with
the computer cannot be established. This I test using the "ethtool" in Linux
to display the properties of the Etherent port. The ...

DH1KLM wrote:Is there any DPI scaling active in Windows?
If yes, your error message should look like this, and points to combo.DisplayMode.

I assume that's the reason.
Try to set it back to default. (100%)

Yes! this was it. Now Thetis is building wisdom files...I plugged in the charger!

Thanks!

FM5GB wrote:Hi

Try to change Windows regional and date format settings.

73,s Phil FM5GB

No luck. Tried different settings but no difference.

Thanks anyway.

Hi,

I installed latest Thetis and PowerSDR mrx PS in Windows 7 on my laptop
but both fail to start with the error message:

"Object reference not set to an instance of an object"

I don't normally use Windows so have no experience of trouble shooting.
I would much appreciate some help here.

My ...

Hi Neoklis,

You may have better luck with that question over in the OpenHPSDR reflector.
Have you joined that yet?

Hi Bryan,

No, I will look it up and join.

Having looked into the Thetis source code, it seems that there is one more factor to take into account, the voltage divider ratio used to ...

w-u-2-o wrote:Are you writing software or firmware?

I am writing software, my own P2-based client for the 7000DLE. Its already functional in receive and I am trying to add a widget to display PSU volts. The decode of bytes 49 and 50 evaluates to about 1660 so 1660 / 4095 * 5 = 2.02

Hi,

I am writing some code to convert the PSU Voltage ADC readout (Protocol II, Hardware to PC, High Priority Status Packet, bytes 49-50) to actual PSU volts. I used the formula for the 200D in the Protocol II v3.8 PDF manual: Calibration constant for Supply V: V = ADC value /4095 * constant ...

Hi all

The fault was in the end the Ethernet controller chip. This was repaired by Doug Wigley W5WC - my thanks. Both the bootloader and programmer work well, although the programmer reports the rig as unknown. However it did successfully upgrade the P2 firmware to Pre8. My own client software ...

If you are booting into the normal P2 firmware, i.e. have not:
- loaded P1 firmware by accident
- forgotten to move the bootloader switch to the correct position
- forgotten to cycle the power after moving the bootloader switch
No, I made certain that I got the above right and several times.

So ...

Have you tried running Thetis?
No, but I could try if it runs in Linux, don't have windoze. However some tests I made a little while ago indicate that the Ethernet connection will not go up to 1000Mb speed. I used "ethtool" to set the computer's Ethernet controller to 1000Mb but it would not ...

As I said in my second post above, I recommend you use Bootloader. The web and command line programmer for P2 is not reliable at this time.
Yes, the Bootloader always seems to work successfully, uploading firmware and setting IP address.

Also, you should be trying and most likely using the ...

Did you not read the the link I posted above? If not, please do so.
Yes, I tried both the web and console versions but both failed to discover. I used Bootloader to upload the "Orion_MkII_Protocol_2_v1.9.rbf" (renamed to Metis_MkII_Protocol_2_v1.9.rbf) successfully, also set the IP address to 192 ...

The only reason that worked is because there was P1 firmware loaded first. Once you loaded P2 firmware that will not work anymore, not until you put P1 firmware back into the unit.
One more question - how do we use the new Bootloader/Programmer tools you mentioned earlier? Is it a matter of ...

I recommend you use HPSDR Bootloader to reinstall the P2 firmware you wish to use, then revisit your network and PC setup. Use a known good client to confirm operation before going back to your client.
Actually I made a mistake, I was trying HPSDRProgrammer_v2_nopcap. If I remember well it did ...

There are no LED indications that are very helpful other than the Ethernet link and traffic indicators.
Hi

I have some more clues that I believe indicate a partial failure (slow speed) of the KSZ9021RL Ethernet controller.
If I manually set the Ethernet speed to 100Mb (using "ethtool" in Linux ...

Is this the programming app you are trying to use:
https://github.com/TAPR/OpenHPSDR-Protocol2-Programmers ?
No, these are, if I understand correctly, in "Go" source code. I am using the compiled binaries that
I downloaded a few months ago to set up the static IP address: HPSDRProgrammer_v2 ...

Hi

My ANAN-7000DLE MkII S/N 7000DLEMKII-011 failed recently, while receiving a
broadcast station. The failure started with a short crackling noise and then
reception stopped. After this, attempts at restarting mostly failed since the
Transceiver would not respond to discovery. There were just a ...

W1AEX wrote:Hi Neoklis,

So, change the firmware filename from: Orion_MkII_Protocol_2_v1.9.rbf to: Metis_Mkll_Protocol_2v1.9.rbf and it should go right in.

73,

Rob W1AEX

Wow, thanks a lot Rob! I will be on it very soon!

Hi

I have been trying to upgrade my (very recently bought) 7000DLE MkII
to Protocol 2. I first tried to use the Protocol 1 Programmer (the rig
arrived with P1 v2.4 firmware) but it didn't work out. The programmer
discovered the 7000 (I had it and Ethernet port set up to static IP)
and managed to ...

Looking at ghpsdr at Github, it has not been updated in two years. This is probably not a good guide for development.

You should be looking at the clients that remain currently under development for guidance. That would be PowerSDR mRX for Protocol 1 firmware, and Thetis for Protocol 2 firmware ...