v1.3 release is updated to fix the problems that 200D (Orion) users have reported with the v1.2 release.
Many thanks to Rick, N1GP for his quick reaction to reports of problems on the forum and mailing lists.
https://github.com/TAPR/OpenHPSDR-Firmware/tree/master/Protocol%202/Orion%20(ANAN-200D)
73,
Scott
200D (Orion) users: P2 v1.3 released
Forum rules
Until such time as the New Protocol firmware goes into general release, all discussion will be concentrated here.
Until such time as the New Protocol firmware goes into general release, all discussion will be concentrated here.
Re: 200D (Orion) users: P2 v1.3 released
Good news! P2 v1.3 works with my 200D. Now, for the first time I have functioning PureSignal in Thetis. So it is looking good. so far. Will give it a thorough check over the weekend.
Thanks to the developers for fixing this so quickly.
73 Dave G3ZQH
Thanks to the developers for fixing this so quickly.
73 Dave G3ZQH
Re: 200D (Orion) users: P2 v1.3 released
This is changed from what I saw before v1.3:
I see "Seq=>8" in red below the panadapter which changes to "Seq=>10" when I activate PureSignal. I'm not sure if this is a warning (red colour) or information. Just reporting it in case it is relevant.
73 Dave G3ZQH
I see "Seq=>8" in red below the panadapter which changes to "Seq=>10" when I activate PureSignal. I'm not sure if this is a warning (red colour) or information. Just reporting it in case it is relevant.
73 Dave G3ZQH
Re: 200D (Orion) users: P2 v1.3 released
It is good to read that some people are now having success with the 200D/Orion.
The "Seq" error codes show dropped or missing data from the radio hardware coming into the client software. Each frame or packet of data contains a sequence number. If the sequence numbers are not sequential errors are generated. The number shown is the summation of the following possibilities:
1 - High priority command & control data
2 - DDC0 data
4 - DDC1 data
8 - DDC2 data
16 - DDC3 data
32 - Mic input data
A Seq error of 10 would indicate data sequence errors on DDC0 and DDC2 data.
What all this means is not entirely clear, but it would be good to keep track of it. I, myself, get Seq 2 errors when transmitting with PS ON, on an 8000.
Thanks,
Scott
The "Seq" error codes show dropped or missing data from the radio hardware coming into the client software. Each frame or packet of data contains a sequence number. If the sequence numbers are not sequential errors are generated. The number shown is the summation of the following possibilities:
1 - High priority command & control data
2 - DDC0 data
4 - DDC1 data
8 - DDC2 data
16 - DDC3 data
32 - Mic input data
A Seq error of 10 would indicate data sequence errors on DDC0 and DDC2 data.
What all this means is not entirely clear, but it would be good to keep track of it. I, myself, get Seq 2 errors when transmitting with PS ON, on an 8000.
Thanks,
Scott
Re: 200D (Orion) users: P2 v1.3 released
Thetis unstable with 200D/P2 v1.3
After several hours of working Thetis has now been crashing after just a few minutes of operation. The obvious problem I can see is to with the VAC audio, where there are many under/overflows. I attach screen shots. I tried ticking the VAC settings for 'manual' or 'force', but the problem was the same with either setting. I don't really understand these settings, but I can see that something is wrong.
Also, I was running WSJT-X and I noticed that the audio waterfall looked very smeared and not like it normally does. The waterfall on Thetis looks normal and the audio also sounds OK in my headphones. I also have been using SDRConsole with P2 v1.3, and this works fine and there is no problem with the VAC audio in/out.
I hope this is useful for the development team.
73 Dave G3ZQH
After several hours of working Thetis has now been crashing after just a few minutes of operation. The obvious problem I can see is to with the VAC audio, where there are many under/overflows. I attach screen shots. I tried ticking the VAC settings for 'manual' or 'force', but the problem was the same with either setting. I don't really understand these settings, but I can see that something is wrong.
Also, I was running WSJT-X and I noticed that the audio waterfall looked very smeared and not like it normally does. The waterfall on Thetis looks normal and the audio also sounds OK in my headphones. I also have been using SDRConsole with P2 v1.3, and this works fine and there is no problem with the VAC audio in/out.
I hope this is useful for the development team.
73 Dave G3ZQH
- Attachments
-
- Thetis Crash report.PNG (44.96 KiB) Viewed 7361 times
Re: 200D (Orion) users: P2 v1.3 released
It appears that those with 7000's and 8000's are faring better than those with 200D's. Not enough traffic from those with other radios to get a feel yet.
Re: 200D (Orion) users: P2 v1.3 released
Running 200D rev 24/Orion NP v1.3/Thetis v@.6.0. RF spectrum now stable, Predistortation now working. Remaining problems:
at 1536000 sample rate the audio "chatters". Predistortion appears slow to respond. When transmitting SSB Rx2 spectrum shows opposite SB.
L and R audio channels are swapped using front panel headset output. No Panafall is available. Some of these problems belong to NP and some
belong to Thetis.
Followup: After reverting to Thetis v2.3.11 and v2.5.3 and reinstalls of Orion NP v1.3 and back to Thetis v2.6.0, it is now running ok with exception of L/R audio reversal and audio "chatter" at 1536000 sample rate.. Predistortion now OK. SSB issues fixed. Still missing Panafall display.
NP an Thetis are now usable.
at 1536000 sample rate the audio "chatters". Predistortion appears slow to respond. When transmitting SSB Rx2 spectrum shows opposite SB.
L and R audio channels are swapped using front panel headset output. No Panafall is available. Some of these problems belong to NP and some
belong to Thetis.
Followup: After reverting to Thetis v2.3.11 and v2.5.3 and reinstalls of Orion NP v1.3 and back to Thetis v2.6.0, it is now running ok with exception of L/R audio reversal and audio "chatter" at 1536000 sample rate.. Predistortion now OK. SSB issues fixed. Still missing Panafall display.
NP an Thetis are now usable.
Re: 200D (Orion) users: P2 v1.3 released
P2 v1.3 can't find my 200D. Tried database reset, reboot, assigning reserved ip. Bootloader still finds the radio.
Buck ko0y
Buck ko0y