Welcome, Guest
Username: Password: Remember me
*****PLEASE, CHECK ALL PREVIOUS TOPICS, BEFORE CREATING A NEW ONE! DUPLICATED TOPICS WILL BE DELETED!*****
  • Page:
  • 1
  • 2

TOPIC: Wishes/Software/Hardware

Wishes/Software/Hardware 27 Jul 2016 08:30 #1

  • g0cgl
  • g0cgl's Avatar
  • OFFLINE
  • Erik EI4KF / G0CGL
  • Posts: 736
  • Thank you received: 287
Instead of separating out 'Wishes', 'Software', 'Hardware' I have constructed a single list. Written with the sole aim of making the MB1 better and no criticism is implied and nor should it be taken.

SOFTWARE

TX B: does not work.

M.IN and M.RD: do not work

S-Meter: with no antenna connected, reads S2 on 160m-10m. On 6m, the S-Meter reads S6 with no antenna connected. The S-Meter scale on 6m goes to +100 whereas it is +80 on all other bands. On my other radios, no signal input gives S0 on their S-meters which I consider to be more normal.

Skimmer: with CW Skimmer running and 'Tune frequency from CW Skimmer' enabled, the MB1 frequency wanders and changes of its own accord.

Vox: vox adjustment is too critical with a sharp threshold between not enough gain and too much.

Vox: addition of anti-vox is needed.

Vox: system is defective and does not always return to receive.

Vox: any adjustment of Vox settings results intermittent receive audio until the MB1 is restarted.

Latency: too long even with settings optimised.

Filter shift: adjustment affects filter width - shifting a filter and then having to readjust the width is abnormal in comparison to my other radios.

Drive and Tone: need to be completely independent. Tone can be set differently from Drive but as soon as Drive is adjusted by front panel control, Tone unfortunately follows suit.

RX Equaliser: default settings are too far from the median and give too much bass response and not enough treble.

RX & TX Equalisers: the scale +15 to -15 is not defined and there are too many iterations throughout the audio scale for accurate adjustment. 18 x 31 makes it too hard to optimise.

Power Out Meter: at low levels, reads too low and is inaccurate. At up to 5 watts out, it still reads zero.

SWR Meter: under-reads and even at SWR of 2:1, it still reads 1.0

Sample rate: 156 khz and 312 khz sample rate introduce background receiver noise, especially in CW mode.

PC Audio: when on introduces background receiver noise, especially in CW mode.

WISHES

Split: a pre-defined or user defined QSY in KHz needs adding - enabling Split would make the 2nd VFO move up 5 KHz, for example.

Skimmer: spot display on spectrum requires filtering, by Continent would be a start - as a European, I do not need the display cluttered by European spots.

Skimmer: adjustable persistence value - currently spot display on spectrum persists forever so a user setting for 5 or 10 or 15 minutes would be better + a 'clear spots' button to erase all spots on spectrum and start afresh.

Skimmer: duplication checking in that as Skimmer sweeps the spectrum, it currently posts all it hears even if it posted the same station(s) 5 minutes earlier. This unnecessarily fills a telnet or DX Cluster window with repeat spots.

Filter width save: The 3 frequency per band stack does not independently save filter width, instead only by mode.

MB1 GUI: needs additional display of Tone %.

Desktop GUI: needs a more visible indication of when Split is active. A little red 'TX' in VFO B and a separated red line are insufficient to show that transmissions will be away from the DX frequency or not.

User Manual:

In the above, I have omitted non-working functions that are known to be forthcoming as programming of the ExpertSDR2 software is developed: ALC from amp, TNF, etc. But there are omissions, discrepancies and inaccuracies that lead to frustration and disappointment:

Many options get a vague description but no definition. The scales of adjustment are often meaningless since they are lacking information about what they do and the effect of increasing or decreasing the levels. Examples include, but are not limited to: Taps, Filter Taps, Rate, Leak, Quality, NB Threshold. Also, it is unclear if the Filter Taps on the DSP tab are the same as those on the TX tab.

A separate dialogue should be given to help with getting the best performance: what settings affect latency for example. The user would be even more greatly helped if the default settings were better optimised.

Description of external PA control is too vague. Instruction is needed for connecting to the CAT system and to set up port splitting if rig control software is also used. Adjustment of switching delay is claimed in Local Panels but what that setting is, if it exists, is not described. It seems the instruction should point to Options>PA>RX/TX & TX/RX.

HARDWARE

Technical Characteristics: the MB1 is advertised as having an Intel i5 processor running at 3.0GHz. In actuality it seems to be 2.2GHz overclocked to 2.5Ghz.

Power out on key-down, with mic agc off, is 87 watts and not 100 watts.
The administrator has disabled public write access.

Wishes/Software/Hardware 06 Aug 2016 09:46 #2

  • g0cgl
  • g0cgl's Avatar
  • OFFLINE
  • Erik EI4KF / G0CGL
  • Posts: 736
  • Thank you received: 287
1. In Beta 11, all of the above are still current. The release claims artifacts in CW mode is solved. But actually they are now worse, especially when PC Audio is ON. I can provide another audio file if required.

2. Additional information on the problem of the S-Meter, especially on 6 meters where its minimum level is S6. I thought initially that the MB1 was generating noise on 6m but in fact it is a problem of the scaling of the meter. See screenshots:


Attachment Capture.png not found




Attachment Capture2.png not found



At 29.999999 Mhz the scale is 0 to +80 but at 30.000001 it is 0 to + 100

The effect is that exactly the same level of noise shows as under S3 below 30MHz and over S6 above 30MHz. Something wrong there.

3. On a related issue, I should add that I have no external noise, my other radios show S0 on no signal, so there is also something amiss with the MB1 S-Meter as it will always be above 0, usually S2, even with no antenna connected.
Last Edit: 06 Aug 2016 09:50 by g0cgl.
The administrator has disabled public write access.

Wishes/Software/Hardware 06 Aug 2016 10:45 #3

  • g0cgl
  • g0cgl's Avatar
  • OFFLINE
  • Erik EI4KF / G0CGL
  • Posts: 736
  • Thank you received: 287
In Beta 11, NB1 has a fault. When using either front panel knob or DSP/NB1 level in Options, moving the level down below 1.20 results in ExpertSDR2 crash:


Attachment Capture3_2016-08-06.png not found

The administrator has disabled public write access.

Wishes/Software/Hardware 07 Aug 2016 06:24 #4

  • g0cgl
  • g0cgl's Avatar
  • OFFLINE
  • Erik EI4KF / G0CGL
  • Posts: 736
  • Thank you received: 287
Another problem (may have pre-existed, discovered yesterday): In Options, Expert tab, the Power Correction does not work for any band. If the figures are changed and even if 'Write' or 'Apply' (or both) are pressed, the output is still at full power.


Attachment Capture4.png not found



12m power correction is at 1.0 but full power is being transmitted.

Full power from the MB1 on 12m is 56 watts but 1.0 should be nearer 1% of 100 or around 1 watt. Please correct this because, if it was properly working, it would help to avoid excessive input to the amplifier in lieu of the missing ALC.
Last Edit: 07 Aug 2016 06:36 by g0cgl. Reason: spelling error
The administrator has disabled public write access.

Wishes/Software/Hardware 26 Aug 2016 17:11 #5

  • f4bwj
  • f4bwj's Avatar
  • OFFLINE
  • Posts: 61
  • Thank you received: 11
Hi,

I've tried beta11 too and I'have found the same kind of bugs that g0cgl has mentioned.

Concerning power correction it appears that it doesn't work correctly and, in addition, power seems to be not very stable, at least in VHF.
In remote operation it appears that I get problems with my 2m amplifier (Linear Amp UK Gemini 2) as it indicates me High SWR and pass in protection mode after a couple of transmission (PA PTT 1 is enabled on ExpertSDR2 on my MB1 and on ExpertSDR2 on my remote computer as it appears it must be enabled on both computers, MB1 and remote computer).
With beta 9 I don't have this kind of problem. The 2m amplifier never indicate me High SWR and never pass to protection mode.
Anyway, power is more stable on beta 9 as in beta 11 for the same drive setting (e.g. 50%) I never get the same power and my 2M amplier can be overloaded and pass in protection mode. It can be very annoying during remote operation and for the amplifier itself.

And, I insist, I don't have this kind of problem with beta 9.

I edit my post because I've forgotten to mention that mic level are weaker in beta 11 than in beta 9, I'm obliged to increase mic level (MIC 1 , MIC 2 and PC MIC) in beta 11 compared to beta 9.

Another point but common to beta 9 and beta 11 and other previous beta, I find that the NFM BF level is weak compared to SSB BF level, for example, I have to icrease the volume a lot and some radio ham I've contacted on 2m in this mode have found that my modulation was weaker than they used to listen from my part with my Icom IC9100 or IC910H, for example.
Last Edit: 26 Aug 2016 17:21 by f4bwj. Reason: I've added some comments.
The administrator has disabled public write access.

Wishes/Software/Hardware 29 Aug 2016 10:43 #6

  • f4bwj
  • f4bwj's Avatar
  • OFFLINE
  • Posts: 61
  • Thank you received: 11
Hi,

concerning high SWR with my 2m Linear Amp amplifier I may have discovered a rather amazing thing.
Indeed, with beta 9 of ExpertSDR2 It appeared that the problem of high SWR occurred too but it just resulted by a SWR LED of the amplifier according to modulation and it has just passed in protection mode only if I toggled the PTT of the MIC without speaking. :mrgreen:
So I've take a look to my installation to discover what has been changed on it especially before going to the beta 11. The sole thing I've changed is the place where the power cord of my amplifier has been connected. So I've plugged the power cord of my amplifier on the plug where it was previously connected and, by miracle no more problem with SWR LED blinking and switching to protection mode.
I'will try to see if it works when with beta 11 again when I will have the time.
The sole thing I don't understand by now is why the effect of bad SWR was more important with beta 11 than beta 9. Perhaps it's due to the lack of power control in beta 11.
.
The administrator has disabled public write access.

Wishes/Software/Hardware 29 Aug 2016 14:14 #7

  • f4bwj
  • f4bwj's Avatar
  • OFFLINE
  • Posts: 61
  • Thank you received: 11
Well, SWR problem on 2M seems solved even in beta 11 and with remote operation after changing of power outlet for my 2M amplifier in my shack.
Concerning power stability problem in beta 11, the solution to get it stable (at least on 2M, I've not tried on other band) using drive level, is to let the power correction as it is in beta 9 and on condition that not press "Write" in Options -> Device -> Expert.
So I must imperatively not touch the power correction and press "Write" in beta 11 and keep the same settings as in beta 9.

Note that I need to set power correction to 7,5 instead of 25 to get 25W with drive level at 100% in ExpertSDR2 in beta 9.
Last Edit: 29 Aug 2016 14:16 by f4bwj.
The administrator has disabled public write access.

Wishes/Software/Hardware 29 Aug 2016 16:07 #8

  • g0cgl
  • g0cgl's Avatar
  • OFFLINE
  • Erik EI4KF / G0CGL
  • Posts: 736
  • Thank you received: 287
Your workaround solution of not pressing 'Write' does not seem to work on the other bands. At least I cannot make it do it. No matter what the power coefficient, full power is transmitted.

A fail-safe is available in Beta 11 as you can uncheck 'Don't Save Drive by Band and Mode' so that your power level per band/mode is fixed unless you manually change it. It is at least some safeguard against damaging the PA. Hopefully on the next update we will have PA ALC.
Last Edit: 29 Aug 2016 16:08 by g0cgl. Reason: typo
The administrator has disabled public write access.
The following user(s) said Thank You: Anti

Wishes/Software/Hardware 29 Aug 2016 16:19 #9

  • f4bwj
  • f4bwj's Avatar
  • OFFLINE
  • Posts: 61
  • Thank you received: 11
Well after some tries finally it appears very erratic even on 2m band.
First of all as it has been done in beta 9 theoretically power is settled to 25W max on 2m via Power correction
After some time without transmitting, at the first call, power is too high and my 2m amplifier is over driven and I must decrease the power from 100% to 50/60% to get my amplifier correctly driven. After three or four successive transmissions power decreases by itself and I can set the power level progressively to 100% again to recover full power on my amplifier. It's very annoying.

This problem doesn't occur with beta 9.
Last Edit: 29 Aug 2016 16:24 by f4bwj.
The administrator has disabled public write access.
The following user(s) said Thank You: Anti

Wishes/Software/Hardware 01 Sep 2016 15:23 #10

  • VassiL
  • VassiL's Avatar
  • OFFLINE
  • Разработчик SDR-техники, Developer of SDR
  • Posts: 1299
  • Thank you received: 247
Hi All,
Thank you for the information about bugs and sugestions. We are working on it.
Today was released the new version of ExpertSDR2 1.1.3 RC2. Please check it and inform about bugs by e-mail.
Василий, Vasily,
Expert Electronics
The administrator has disabled public write access.

Wishes/Software/Hardware 01 Sep 2016 15:43 #11

  • f4bwj
  • f4bwj's Avatar
  • OFFLINE
  • Posts: 61
  • Thank you received: 11
Hi Vasily,

many thanks for the info concerning the new version of ExpertSDR2 1.1.3 RC2.
I will download and try it as soon as possible.

I've noticed that bugs reports may be reported by e-mail.
The administrator has disabled public write access.

Wishes/Software/Hardware 01 Sep 2016 15:52 #12

  • VassiL
  • VassiL's Avatar
  • OFFLINE
  • Разработчик SDR-техники, Developer of SDR
  • Posts: 1299
  • Thank you received: 247
Yes, bug reports more efective because managers receives e-mails and imidiately forward it to programmer.
Василий, Vasily,
Expert Electronics
The administrator has disabled public write access.

Wishes/Software/Hardware 01 Sep 2016 16:03 #13

  • f4bwj
  • f4bwj's Avatar
  • OFFLINE
  • Posts: 61
  • Thank you received: 11
Ok, but if there is things that work well with this RC2 I will report it on the forum ;)
The administrator has disabled public write access.

Wishes/Software/Hardware 01 Sep 2016 16:23 #14

  • g0cgl
  • g0cgl's Avatar
  • OFFLINE
  • Erik EI4KF / G0CGL
  • Posts: 736
  • Thank you received: 287
There are some problems with 1.1.3 RC2. I cannot find any fixes for bugs from Beta 11. And some new ones are very troubling:

Not only does Power Correction not work and ALC not work but now there is an issue with SWR protection. I'm not sure if it is completely not working or just that this version doesn't accurately detect the SWR. I don't like to test beyond 3:1 in case I damage the MB1 - but power doesn't fold back even though that is my setting.

Also, be careful if you wear headphones and change from CW to SSB. What is normal volume in CW is blasting out in SSB. The same real volume is -32dB in CW and -57db in SSB.

I have emailed a long list of bugs this afternoon but meanwhile, because 1.1.3 RC2 has too many issues, can I revert to 1.1.3 Beta 11 even though I updated the firmware or is it not possible to roll back?
The administrator has disabled public write access.

Wishes/Software/Hardware 01 Sep 2016 21:48 #15

  • g0cgl
  • g0cgl's Avatar
  • OFFLINE
  • Erik EI4KF / G0CGL
  • Posts: 736
  • Thank you received: 287
Ok - with someone's help I managed to go back to Beta 11.

I cannot honestly believe this was a "Release Candidate". Surely there was a mistake and the wrong version was issued. There could not have been any testing. All previous bugs still exist. It is obvious just by listening to the radio there is a volume problem. It is obvious just by visual observation that the MB1 GUI s-meter doesn't function. For the high financial cost of the MB1, to have so many problems that increase on each software release and to be treated in this manner is not good enough.
The administrator has disabled public write access.
  • Page:
  • 1
  • 2
Time to create page: 0.234 seconds