Welcome to Synthiam!

Program robots using technologies created from industry experts. ARC is our free-to-use robot programming software that makes features like vision recognition, navigation and artificial intelligence easy.

Get Started
United Kingdom
Asked — Edited

Ez-Builder Update + Firmware Issue

Hi,
Had a bit of a strange one and I hope you can shed some light on it.
I received my EZ-B from MakerShed, I downloaded the ARC and installed.
Tried to connect (after my previous issues with the Bluetooth!) and was informed that the firmware needed updating, I followed the tutorial and was up and running in no time :D
Then the ARC said it needed to update, which it did and now I was rocking and rolling.

Ok, here is the crunch, my kit came from EZ-Robot and the board that came with it said it needed a firmware update, but now when I launch the Firmware update tool I get an error, see the enclosed pdf.
Ok, so we can't attach a pdf......

I tried to download the latest ARC but it says that the one on my computer is newer than the latest one from the site.

Any ideas?

...........................................................................
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.IO.FileLoadException: Could not load file or assembly 'EZ_B, Version=2012.1.4.0, Culture=neutral, PublicKeyToken=839146fd54f35ea1' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
File name: 'EZ_B, Version=2012.1.4.0, Culture=neutral, PublicKeyToken=839146fd54f35ea1'
at EZ_B_Firmware_Update.Form1.Form1_Load(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.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)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5448 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
EZ-B Firmware Update
Assembly Version: 2011.11.29.0
Win32 Version: 2011.11.29.0
CodeBase: file:///C:/Program%20Files%20(x86)/EZ-Robot/EZ-Builder%20Installer/EZ-B%20Firmware%20Update.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5446 (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.5447 (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.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.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:





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.

AI Support Bot
Related Content
Synthiam
United Kingdom
#1  
What does all of that sh..... stuff mean?
*confused*

Just seen at the bottom of the tutorial page a message telling me to forward this info in the contact us, I therefore appologise that I did not see that bit before posting.

On a brighter note this is another good call for a delete post button *eyeroll*
United Kingdom
#3  
Hay DJ Sures,

Thanks for the quick reply, first I thought you were stating the obvious, yes I am trying to build a robot, but then I read it again and realised what you meant *blush* rebooted a couple of times and I still have:
Unhandled exception has occured in your application. If you click
Continue, the application will ignore this error and attempt to continue. If
you click Quit, the application will close immediately.

Could not load file or assembly 'EZ_B, version=2012.1.4.0.
Culture=neutral, PublicKey Token=83914fd54f35ea1' or one of its
dependancies. The located assembly's manifest definition does not match
the assembly reference. (Exception from HRESULT: 0x80131040).

If I click continue the program opens but I can not select a COM port, it is blank.

The question is, if i remove ARC and re install from scratch will it loose the set up I have done for my Wall-ter?

Kind regards
Darren
PRO
Synthiam
#4  
Your computer is confused:) it happens sometimes. Often in windows. You will not lose your project files if you uninstall:)
United Kingdom
#5  
it is only the firmware updater, I can connect to the other board and Wall-ter runs round till the batteries go flat, all of about 10 mins:D

Just did a system restore but it looks like a uninstall and fresh install.

Here we go....
United Kingdom
#6  
Improvement!
Firmware updater is now working in a way, it does not come up with the error, but the COM ports on both EZ and firmware start from COM50, 60, 70, 90

In ARC you can change the port simply by typing it in but on Firmware you only have the choices it gives you.

I think I am going to try and install on another PC just for the firmware update!
(my head hurts now!)