ANAN 7000 MK 3 - Ciclone V- P.2 issues
Posted: Sun Jan 29, 2023 6:20 pm
Edit 2024_02_12: With the new firmware 2.2.2 (for 5CEFA) it seems that the tx finally goes well, there were no more transmission gaps/glitch
RTX: Anan 7000Dle MK3 with Cyclone V FPGA connected via switching eth 1GB
PC: Intel i7 penultimate generation 3.6Ghz- 16GBram
It comes out of the box with fw P1: Everything seems to work fine
I make the comparison with Yaesu FT DX 101D, the weak signals on the 101D are more understandable, the difference is also noticed by friends to whom I sent some videos
Action: Load P.2 fw
At the beginning everything ok, now the difference with the 101D is small, even if the 101 is still slightly better on receiving weak signals in a noisy environment.
After a few minutes of transmission (cq dx cq dx etc..) alerts begin to appear:
SEQ ERROR 8 DDC2
SEQ ERROR 10 DDC0 DDC2
SEQ ERROR 267 CC DDC0 DDC2 Mic (this appears many times)
When this warning appears, my correspondent notices a lack of audio
Putting the radio in TX, even without a microphone connected (MOX only) there is a tone at about 600-700Hz which is not detected by the wattmeter but which is still transmitted if I listen to another nearby radio.
This tone remains even with the microphone inserted and is perceived in transmission. It looks like a larsen effect (digital redundancy maybe?), but I don't know.
By canceling the AM carrier from 100 to 0, returning to SSB the tone is not present, but reappears immediately on the second transmission.
Action: Turn off firewall. No result.
Action: Enable 0xffffffff in regedit as instructed. No result
Action: Enable static IP, no results
Action: I shut down all running software except thetis. No result.
Action: I disconnect ANAN from the switching and connect it to a second specially mounted eth pci card. The transmission tone disappears, the TX audio returns to being clean.
The SEQUENCE problems seem to reduce but only initially, after 15-20 minutes of transmission they return to an increasingly higher frequency up to 1-2 errors every 10/15 seconds of TX.
Action: Load P1 firmware. Everything works fine again, no errors in over two hours of intense activity.
I hope that this info can be of help to the developers, to whom all my respect and gratitude goes, and I hope to be able to have some indications to go back to running P.2 in a stable way.
RTX: Anan 7000Dle MK3 with Cyclone V FPGA connected via switching eth 1GB
PC: Intel i7 penultimate generation 3.6Ghz- 16GBram
It comes out of the box with fw P1: Everything seems to work fine
I make the comparison with Yaesu FT DX 101D, the weak signals on the 101D are more understandable, the difference is also noticed by friends to whom I sent some videos
Action: Load P.2 fw
At the beginning everything ok, now the difference with the 101D is small, even if the 101 is still slightly better on receiving weak signals in a noisy environment.
After a few minutes of transmission (cq dx cq dx etc..) alerts begin to appear:
SEQ ERROR 8 DDC2
SEQ ERROR 10 DDC0 DDC2
SEQ ERROR 267 CC DDC0 DDC2 Mic (this appears many times)
When this warning appears, my correspondent notices a lack of audio
Putting the radio in TX, even without a microphone connected (MOX only) there is a tone at about 600-700Hz which is not detected by the wattmeter but which is still transmitted if I listen to another nearby radio.
This tone remains even with the microphone inserted and is perceived in transmission. It looks like a larsen effect (digital redundancy maybe?), but I don't know.
By canceling the AM carrier from 100 to 0, returning to SSB the tone is not present, but reappears immediately on the second transmission.
Action: Turn off firewall. No result.
Action: Enable 0xffffffff in regedit as instructed. No result
Action: Enable static IP, no results
Action: I shut down all running software except thetis. No result.
Action: I disconnect ANAN from the switching and connect it to a second specially mounted eth pci card. The transmission tone disappears, the TX audio returns to being clean.
The SEQUENCE problems seem to reduce but only initially, after 15-20 minutes of transmission they return to an increasingly higher frequency up to 1-2 errors every 10/15 seconds of TX.
Action: Load P1 firmware. Everything works fine again, no errors in over two hours of intense activity.
I hope that this info can be of help to the developers, to whom all my respect and gratitude goes, and I hope to be able to have some indications to go back to running P.2 in a stable way.