OpenGD77 can not communicate with MD-1801

OpenGD77CPS
Post Reply
PD5JOS
Posts: 8
Joined: Tue Dec 19, 2023 10:01 am

OpenGD77 can not communicate with MD-1801

Post by PD5JOS » Tue Dec 19, 2023 3:53 pm

Hello,

I have had OpenGD77 on my Baofeng DM-1801 for years without any problem. Until today no problem at all. Only now I want to change eea in the code plug and can no longer communicate with OpenGD77 to the Porto.

Situation:
- Windows 10 is up-to-date, Com14 in use with 9600bps, 8, N, 1. Driver is called OpenGD77 (Com14) in devicemanager
- Using the correct cable (not for analogue Porto)
- In Porto loaded Software OpenDM 1801, Built 06:28:11, Oct 1 2020
- OpenGD77 CPS version R2023.11.26.01

When I try to connect to the CPS, an error comes up: Unexpected exception occurred in the application, the opject reference is not set to an instance of an object (See below, it was not possible to add .txt file) When we click continue on the OpenGD77 Support screen comes up where I can then do nothing either.

I myself feel that this may be because this was written away with an older version CPS (2019-2020) and is not compatible with the current release.

Who can help me with this problem, or possibly has an older version of OpenGD77 (2019-2020) to give this a try. On the Forum I have not been able to find any archive with old versions.

73, Jos

Details of te error:
************* Exception text **************
System.NullReferenceException: The object reference is not set to an instance of an object.
On DMR.OpenGD77Form.readOpenGD77RadioInfoAndUpdateUSBBufferSize(SerialPort port, Boolean stealth)
bij DMR.OpenGD77Form.probeRadioModel(Boolean stealth)
bij DMR.OpenGD77Form.OpenGD77Form_Load(Object sender, EventArgs e)
bij System.Windows.Forms.Form.OnLoad(EventArgs e)
bij System.Windows.Forms.Form.OnCreateControl()
bij System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
bij System.Windows.Forms.Control.CreateControl()
bij System.Windows.Forms.Control.WmShowWindow(Message& m)
bij System.Windows.Forms.Control.WndProc(Message& m)
bij System.Windows.Forms.ScrollableControl.WndProc(Message& m)
bij System.Windows.Forms.ContainerControl.WndProc(Message& m)
bij System.Windows.Forms.Form.WmShowWindow(Message& m)
bij System.Windows.Forms.Form.WndProc(Message& m)
bij System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
bij System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
bij System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded assembly's **************
mscorlib
Assembly-versie: 4.0.0.0
Win32-versie: 4.8.9181.0 built by: NET481REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
OpenGD77CPS
Assembly-versie: 1.2.8730.16616
Win32-versie: 1.0.0.0
CodeBase: file:///C:/Program%20Files%20(x86)/OpenGD77CPS/OpenGD77CPS.exe
----------------------------------------
System.Windows.Forms
Assembly-versie: 4.0.0.0
Win32-versie: 4.8.9181.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-versie: 4.0.0.0
Win32-versie: 4.8.9206.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-versie: 4.0.0.0
Win32-versie: 4.8.9037.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
----------------------------------------
WeifenLuo.WinFormsUI.Docking
Assembly-versie: 3.0.4.0
Win32-versie: 3.0.4.0
CodeBase: file:///C:/Program%20Files%20(x86)/OpenGD77CPS/WeifenLuo.WinFormsUI.Docking.DLL
----------------------------------------
System.Data
Assembly-versie: 4.0.0.0
Win32-versie: 4.8.9191.0 built by: NET481REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_32/System.Data/v4.0_4.0.0.0__b77a5c561934e089/System.Data.dll
----------------------------------------
System.Xml
Assembly-versie: 4.0.0.0
Win32-versie: 4.8.9037.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
----------------------------------------
System.Configuration
Assembly-versie: 4.0.0.0
Win32-versie: 4.8.9037.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.Core
Assembly-versie: 4.0.0.0
Win32-versie: 4.8.9200.0 built by: NET481REL1LAST_C
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
Accessibility
Assembly-versie: 4.0.0.0
Win32-versie: 4.8.9037.0 built by: NET481REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
mscorlib.resources
Assembly-versie: 4.0.0.0
Win32-versie: 4.8.9037.0 built by: NET481REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/mscorlib.resources/v4.0_4.0.0.0_nl_b77a5c561934e089/mscorlib.resources.dll
----------------------------------------
System.Windows.Forms.resources
Assembly-versie: 4.0.0.0
Win32-versie: 4.8.9037.0 built by: NET481REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.resources/v4.0_4.0.0.0_nl_b77a5c561934e089/System.Windows.Forms.resources.dll
----------------------------------------
System.Numerics
Assembly-versie: 4.0.0.0
Win32-versie: 4.8.9037.0 built by: NET481REL1
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Numerics/v4.0_4.0.0.0__b77a5c561934e089/System.Numerics.dll
----------------------------------------

*************** JIT Debugging ***************
To enable JIT debugging, the configuration file for this must be in
application or computer (machine.config) value
jitDebugging in the system.windows.forms section are set.
The application must also be compiled while debugging
was enabled

Eample:

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

When JIT debugging is enabled, unhandled exceptions are thrown
sent to the JIT debugger registered on the computer
and are not processed by this dialog.

73, Jos

User avatar
F1RMB
Posts: 2626
Joined: Sat Nov 16, 2019 5:42 am
Location: Grenoble, France

Re: OpenGD77 can not communicate with MD-1801

Post by F1RMB » Tue Dec 19, 2023 4:44 pm

Hi,

You're using a three year old firmware with a brand new CPS (from last month).
I suggest you to flash a matching firmware first (get latest CPS and latest Beta firmware).

PD5JOS
Posts: 8
Joined: Tue Dec 19, 2023 10:01 am

Re: OpenGD77 can not communicate with MD-1801

Post by PD5JOS » Wed Dec 20, 2023 8:20 am

Hi F1RMB,

Thanks for your reply, Found the Update procedure and the file. Before i start can you tell me if the current codeplug is lost? Or is there another way to save it without before upgrading the porto.

Thanks, Jos

VK3KYY
Posts: 7590
Joined: Sat Nov 16, 2019 3:25 am
Location: Melbourne, Australia

Re: OpenGD77 can not communicate with MD-1801

Post by VK3KYY » Wed Dec 20, 2023 8:48 am

PD5JOS wrote:
Wed Dec 20, 2023 8:20 am
Hi F1RMB,

Thanks for your reply, Found the Update procedure and the file. Before i start can you tell me if the current codeplug is lost? Or is there another way to save it without before upgrading the porto.

Thanks, Jos
Codeplug format has not changed, but some functionality has been added in the last 2 or 3 years, so some new settings like TS1/2 TA Tx and FM APRS configuation setting for each channel may be incorrect, and also FM APRS configuation section has been added, which may contain incompatible data in your very old codeplug.

Generally, its best to keep the CPS updated if possible.

PD5JOS
Posts: 8
Joined: Tue Dec 19, 2023 10:01 am

Re: OpenGD77 can not communicate with MD-1801

Post by PD5JOS » Wed Dec 20, 2023 9:14 am

Hi F1RMB,

Ok, totally succeeded. After downloading the sql file and in combination with the new Bin file everything works fine again. FW in the Porto is now March 4 2023. I managed to find another old .g77 file but didn't need it, after the upgrade everything was still in the Porto. It can read and write the DM-1801 again. I will check the new settings.

Thanks for the quick respone and support.
Jos, PD5JOS, 73

Post Reply