Open Tuner 0.1 - Test Version

[zr6tg]

Hi All, thanks for all the feedback and comments. New version available (2023/03/20), adds lnb supply switching, basic settings to disable spectrum, set snapshot path, etc and also fixes a few small issues.

https://www.zr6tg.co.za/open-tuner/

73,
Tom

[Basil]

Up and running fine, thanks for the nice updates Tom!

Would there be any support for the snapshot, or a snapshot option to include the data in the LH panel? I sometimes upload screenshots from Minitiouner to include D and MER levels for DATV TX'ers to see their signal here, with data to the chat. I just send a link to the screenshot hosted on my server.

Very appreciative of your contributions to DATV Tom

[zr6tg]

Would there be any support for the snapshot, or a snapshot option to include the data in the LH panel? I sometimes upload screenshots from Minitiouner to include D and MER levels for DATV TX'ers to see their signal here, with data to the chat. I just send a link to the screenshot hosted on my server.

Thats an interesting idea, it should be very possible. Will add it to the list

T

[G3GJA]

I've run into a problem. It worked OK yesterday with the 20230317 release, but today I loaded 20230320 and now I get the error message below.
Using v2 Minitiouner. tried rebooting, different USB ports etc. Tuner works OK on F6DZP's software. Tried reloading 20230317 version; same result.

Clive





FTD2XX_NET.FTDI+FT_EXCEPTION: An unexpected error has occurred when trying to communicate with the FTDI device.
at FTD2XX_NET.FTDI.ErrorHandler(FT_STATUS ftStatus, FT_ERROR ftErrorCondition)
at FTD2XX_NET.FTDI.SetBitMode(Byte Mask, Byte BitMode)
at opentuner.ftdi.ftdi_set_mpsse_mode(FTDI ftdi) in C:\source\tuner_tests\open_tuner\ftdi.cs:line 167
at opentuner.ftdi.ftdi_init() in C:\source\tuner_tests\open_tuner\ftdi.cs:line 578
at opentuner.Form1.hardware_init() in C:\source\tuner_tests\open_tuner\Form1.cs:line 268
at opentuner.Form1.btnConnectTuner_Click(Object sender, EventArgs e) in C:\source\tuner_tests\open_tuner\Form1.cs:line 360
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9139.0 built by: NET481REL1LAST_B
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
opentuner
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/OpenTuner/opentuner.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9075.0 built by: NET481REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9139.0 built by: NET481REL1LAST_B
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9032.0 built by: NET481REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
LibVLCSharp
Assembly Version: 3.6.7.0
Win32 Version: 3.6.7.0
CodeBase: file:///C:/OpenTuner/LibVLCSharp.DLL
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9139.0 built by: NET481REL1LAST_B
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9032.0 built by: NET481REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9032.0 built by: NET481REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Accessibility
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9032.0 built by: NET481REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
LibVLCSharp.WinForms
Assembly Version: 3.6.7.0
Win32 Version: 3.6.7.0
CodeBase: file:///C:/OpenTuner/LibVLCSharp.WinForms.DLL
----------------------------------------
System.Xml.Linq
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9032.0 built by: NET481REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml.Linq/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.Linq.dll
----------------------------------------
websocket-sharp
Assembly Version: 1.0.2.59611
Win32 Version: 1.0.2.59611
CodeBase: file:///C:/OpenTuner/websocket-sharp.DLL
----------------------------------------
FTD2XX_NET
Assembly Version: 1.1.0.0
Win32 Version: 1.1.0.0
CodeBase: file:///C:/OpenTuner/FTD2XX_NET.DLL
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.


get:

[zr6tg]

I've run into a problem. It worked OK yesterday with the 20230317 release, but today I loaded 20230320 and now I get the error message below.
Using v2 Minitiouner. tried rebooting, different USB ports etc. Tuner works OK on F6DZP's software. Tried reloading 20230317 version; same result.

Hi Clive,

Can you check if it does still work with the 20230317 release?

T

[G8GYS]

Worked instantly with my MT-S, an excellent piece of software. Retunes really quickly. Thanks so much! Peter G8GYS

[G3GJA]

Tom

I've found the issue; I had another FTDI connected device plugged into my PC using COM5 virtual port.

Strange that it didn't affect Minitioune, but it's OK on all versions of Open Tuner released so far with the G7OCD USB power meter unplugged.

Clive

[zr6tg]

Tom

I've found the issue; I had another FTDI connected device plugged into my PC using COM5 virtual port.

Strange that it didn't affect Minitioune, but it's OK on all versions of Open Tuner released so far with the G7OCD USB power meter unplugged.

Clive

Yeah, that makes perfect sense. OT currently just grabs the first two devices and then assumes its the right ones. Minitioune does it smarter by actually detecting the ports. This is also why it works on some Pro 2's and not others, because the 2 ports enumerated in different orders. I have started on making it smarter so it will detect the correct ftdi devices to use. Should be done today. Thanks for the feedback

[zr6tg]

New updated version - 2023-03-21

- adds better ftdi detection handling, tries to identify the minitiouner type, a couple of visual changes and additions from Chris (dh3cs) to copy the tx freq to clipboard when right clicking on the qo-100 spectrum monitor.

You can grab it at : https://www.zr6tg.co.za/open-tuner/ as always.

btw - please let me know if your device is not being detected properly or there is an issue with the connection after the new changes. It will help if you provide me with the debug around the ftdi detection in the console part which looks something like this:

Code: Select all

**** FTDI Ports Detection ****
Number of FTDI Devices: 2
0: is a FT2232H device
Description:USB <-> NIM tuner A
A Fifo: False
B Fifo: True
Should be the i2c port for a BATC V2 Minitiouner
 ----
1: is a FT2232H device
Description:USB <-> NIM tuner B
A Fifo: False
B Fifo: True
Should be the ts port for a BATC V2 Minitiouner
 ----
 ****
Trying detected ports:
i2c port: 0
ts port: 1
Number of FTDI Devices: 2

Thanks for all the feedback, comments and coffees/beers, much appreciated.

T

[i4wrm]

It works great now..!! Good job. Thanks again for your patience and congratulations!! 73 de Ros i4wrm