[obdstart]

Change PIC18F458

[lukax8]

You know how your opcom was damaged or it never worked?

never worked

[jason19724]

Hi there I think I bricked my op-com v5 on the board I ute date the firmware it work for few mins then it now it struck on red light ..when I read it having error on it ..Number of interfaces: 1
Description: OP-COM USB V2
FTDI USB Serial: FTUTB55Q
FTDI-ChipID ChipID: 0x216526D9
FTDI-ChipID Location ID: 0x211
O***M Serial-Number (calculated): N85MDLV6
O***M FW UPdate Code (calculated): WN31L5C8
Interface opened. Handle: 95171536
Baudrate 500kBit/s
Dataformat 8N1
Flowcontrol NONE
SetChars
Timeout 5 seconds
Set DTR and RTS Low = PIC Reset
DTR low
RTS low
Wait 1 second for reset
Set RTS High = PIC running
RTS high
Wait 1.5 second, so bootloader can start FW...
RX Buffer clear... OK
FW Versions- and Interface ID- request send.
Timeout - is your PIC empty? No Firmware?
Timeout - is your PIC empty? No Firmware?
Set RTS to LOW = PIC Reset
RTS low
Communication closed. Handle: 95171536
any help please
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.ArgumentException: Length of argument 'String' must be greater than zero.
at Microsoft.VisualBasic.Strings.Asc(String String)
at OPCOMFUT.Main.FlashFirmware()
at OPCOMFUT.Main.FlashFirmwareToolStripMenuItem_Click(Object sender, EventArgs e)
at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ToolStrip.WndProc(Message& m)
at System.Windows.Forms.ToolStripDropDown.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: 2.0.0.0
Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
OPCOMFUT
Assembly Version: 2.9.0.0
Win32 Version: 2.9.0.0
CodeBase: file:///C:/Users//Pictures/Repair%20erased%20OP-COM/OPComFUT%20Check%20Bootloder%20Presence/OPCOMFUT%20V2.9.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5483 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.5483 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
Microsoft.VisualBasic.Compatibility
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.5483
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualBasic.Compatibility/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.Compatibility.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.

[Mauro-IT]

You know how your opcom was damaged or it never worked?

never worked

Carefully check for bad solder. After you need some electronic aknowledge. Check with schematic that all component are present and at right position.
If you have a pic programmer try upload firmware.

Or easy, buy new one.

[obdstart]

@jason19724
"Timeout - is your PIC empty? No Firmware?"
You have empty PIC, need to use external programmer to program PIC with bootloader/firmware.

[jason19724]

@jason19724
"Timeout - is your PIC empty? No Firmware?"
You have empty PIC, need to use external programmer to program PIC with bootloader/firmware.

thanks mate again for your help I throw it into the bin then ..

---

@jason19724
"Timeout - is your PIC empty? No Firmware?"
You have empty PIC, need to use external programmer to program PIC with bootloader/firmware.

thanks mate again for your help I throw it into the bin then ..

will this work for it to repair it please
http://www.ebay.co.uk/itm/USB-PIC-Automa...43af7c0a02

[obdstart]

@jason19724
"Timeout - is your PIC empty? No Firmware?"
You have empty PIC, need to use external programmer to program PIC with bootloader/firmware.

thanks mate again for your help I throw it into the bin then ..

---

@jason19724
"Timeout - is your PIC empty? No Firmware?"
You have empty PIC, need to use external programmer to program PIC with bootloader/firmware.

thanks mate again for your help I throw it into the bin then ..

will this work for it to repair it please
http://www.ebay.co.uk/itm/USB-PIC-Automa...43af7c0a02

See manual of this programmer. If support PIC 18Fxxx series then work.

[mattydr67]

I had this kind of programmer and it is working 100%
Good luck

[chippy0815]

I didn't quite understand is there now a way to get newer Version as 08/2010 on V5 PCB Version?
If yes, which languages are available?
And how can be upgraded?

[fantomel]

M8 read on forum, v5 has genuine pic and it can be upgraded. Look closer, you will see vauxcom 2012 and alos a vaux-com with mixed files that has even 2014. Look for ept to change ftdi and ocflash to flash newer firmware like 1.45 or 1.59.