P.I. Engineering User Forum

Product Support, Technical Questions and Answers, and Examples for P.I. Engineering Products

You are not logged in.

#1 2018-12-05 18:36:31

jsmith
Member
Registered: 2018-12-05
Posts: 1

X-keys Basic Setup unhandled exception on write to device

Whenever I want to write *anything* to the X-keys desktop MWII I get the following exception:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.IndexOutOfRangeException: Index was outside the bounds of the array.
   at XkeysBasicSetup.Form1.writeDeviceToolStripMenuItem_Click(Object sender, EventArgs e)
   at XkeysBasicSetup.Form1.saveToolStripMenuItem_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: 4.0.0.0
    Win32 Version: 4.7.3221.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
XkeysBasic
    Assembly Version: 1.0.3.4
    Win32 Version: 1.0.3.4
    CodeBase: file:///C:/Program%20Files%20(x86)/PI%20Engineering/MacroWorks%20Hardware/XkeysBasic.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3221.0 built by: NET472REL1LAST_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.7.3190.0 built by: NET472REL1LAST_C
    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.7.3056.0 built by: NET472REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
PIEHid32Net
    Assembly Version: 2.2.4.21348
    Win32 Version: 2.0
    CodeBase: file:///C:/Program%20Files%20(x86)/PI%20Engineering/MacroWorks%20Hardware/PIEHid32Net.DLL
----------------------------------------
System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3056.0 built by: NET472REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3221.0 built by: NET472REL1LAST_C
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3056.0 built by: NET472REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Xml.Linq
    Assembly Version: 4.0.0.0
    Win32 Version: 4.7.3056.0 built by: NET472REL1
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml.Linq/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.Linq.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.


How can this be avoided?

Offline

#2 2018-12-06 09:24:24

PIE Liam
Technical Support Specialist
From: Williamston, MI
Registered: 2016-01-21
Posts: 165
Website

Re: X-keys Basic Setup unhandled exception on write to device

I'd suggest trying to use "Hardware" mode programming with the standard programming software MW3.1 found here http://xkeys.com/PISupport/SoftwareMacroWorks.php  , instead of X-Keys Basic. Basic is a more recent build and may behave a bit buggy on that legacy hardware.

Offline

#3 2018-12-06 10:12:25

jsmith1
Member
Registered: 2018-12-06
Posts: 1

Re: X-keys Basic Setup unhandled exception on write to device

Even with that software when trying to select the programming mode on the popup immediately after opening the software I'm getting a fatal error - something went wrong. Please contact the developers with the information in teh Error Log. There's no error log location given, nor have I been able to find it by hand.

Also what the hell is wrong with the logging in into the website? I had to create a new account because it kept saying I'm marked as "undesirable"?

Last edited by jsmith1 (2018-12-06 10:13:04)

Offline

#4 2018-12-06 11:04:49

PIE Liam
Technical Support Specialist
From: Williamston, MI
Registered: 2016-01-21
Posts: 165
Website

Re: X-keys Basic Setup unhandled exception on write to device

"Also what the hell is wrong with the logging in into the website? I had to create a new account because it kept saying I'm marked as "undesirable"?"

I have no idea what  that means, I've never had that reported before, never even knew that message existed, I'll check with it out with our webmaster.

Try this:
Unplug the unit.
Uninstall Macroworks 3.1 via control panel
Delete the “PI Engineering” folder you find here C:\Program Files (x86)
Delete the “PI Engineering” folder you find here C:\Users\YouUserNameHere\AppData\Local you’ll need to “Show Hidden Folders” to see the APPDATA folder.

Reinstall MW3.1 from here http://xkeys.com/PISupport/SoftwareMacroWorks.php
Plug in the device (put the switch to as far "Red as you can and leave it there) but before you launch MW3.1 go here C:\Program Files (x86)\PI Engineering\MacroWorks 3.1 and double click to launch the “EraseHWMacros” tool , this will clean off your device’s memory. Once finished launch MW3.1  via the icon on the desktop.

Choose Hardware mode
Double click onscreen the first key this will open the "Macro" window
In the Keystrokes tab enter via your qwerty "1"
Select "Save"
Select "File>Write to device"
When Finished select "File>Exit Macroworks"
open up Notepad to test the key you've just programmed.

This will factory reset your device so make sure to save any scripts you don't want to have to remake. If you are still getting an error attache the error log found here C:\Users\YourUserNameHere\AppData\Local\PI Engineering\MacroWorks 3

Offline

#5 2018-12-06 16:04:59

jsmith2
Member
Registered: 2018-12-06
Posts: 1

Re: X-keys Basic Setup unhandled exception on write to device

PIE Liam wrote:

"Also what the hell is wrong with the logging in into the website? I had to create a new account because it kept saying I'm marked as "undesirable"?"

I have no idea what  that means, I've never had that reported before, never even knew that message existed, I'll check with it out with our webmaster.

This is what i'm getting when trying to log in, on both accounts now (thus a new account again):

Info
You are identified as undesirable. RC : 1

As for the error I'm still getting the same even after following your procedure to the t.

Error log:

Source       : mscorlib
Method      : GetCultureTableRecord
Date          : 12/6/2018
Time          : 9:01:17 PM
Computer   : DESKTOP-IMFM9KF
Error          : Culture ID 8192 (0x2000) is not a supported culture.
Parameter name: culture
MW3          : v.1.1.2.1
Handled     : False
Stack Trace : at System.Globalization.CultureTableRecord.GetCultureTableRecord(Int32 cultureId, Boolean useUserOverride)
   at System.Globalization.CultureInfo..ctor(Int32 culture, Boolean useUserOverride)
   at System.Windows.Forms.InputLanguage.get_Culture()
   at MW3g.FormMain..ctor(String[] args)
   at MW3g.Program..ctor()
   at MW3g.Program.Main(String[] args)
Message : Culture ID 8192 (0x2000) is not a supported culture.
Parameter name: culture
<<--------------------------------------------------------------------------------------------------->>

Offline

#6 2018-12-06 16:28:16

PIE Liam
Technical Support Specialist
From: Williamston, MI
Registered: 2016-01-21
Posts: 165
Website

Re: X-keys Basic Setup unhandled exception on write to device

Is this a standard Windows installation, not an emulation or virtualization of some kind? You are receiving this error when you attempt to "File>Write to device"? The ErasHWmacros tool functioned correctly though?

I've sent the error onto our development department because I've never seen that before nor have had it reported. I've taken a MWII off the shelf and it is functioning as expected with MW3.1 and Windows 10.

I've reported the undesirable error as well, here again this is the first and only time I've had this reported.

How old is you're unit? When did it begin to show this error?

Can you confirm that you have .NET 3.5 installed and enabled?

Couple more ideas: Is Windows set up in English?

Offline

Board footer

Powered by FluxBB