MCS+5 generates obsolete Visual C++ v6 in 32bit mode

[Robert Hedan]

I asked Mecanique

Hello,
Do you have any plans/timetable to convert the 32bit C++ version 6 code generated by EasyHID?
32bit is no longer supported by many applications, making the generated code useless in VS2022 (to me since I can't convert it on my own).
Thanks!

Has anyone a way of converting 32bit C++ to useable 64-bit code for Visual Studio 2022? I'm interfacing with SimConnect for MSFS 2020 and it requires 64-bit C++.

Unless someone knows of a tool that replaces EasyHID but in 64-bit C++?

Robert

[mpgmike]

It costs some money, but take a look at HIDmaker. I've used it for about 7 years now, but the latest Visual Studio was 2015. I'm using v2017, but for other stuff. It may or may not work on v2022.

[Robert Hedan]

I have it. Haven't even tried it since it's dated 2005.

Now this is interesting, but damn, $600...

[Robert Hedan]

I emailed them asking if there was an upgrade package to HIDmaker FS2 for us HIDmaker FS users. I sincerely doubt they have one, but hey, won't know until we ask.

$400USD is a bit steep for me, but if it can deliver as advertised C++ code for WinForms that works in v4.6 NET framework in 64-bit, that's exactly what I need.


EDIT: Crap, forgot to ask if it just generates .PBP and INCLUDE files. I don't use MPLAB, so I don't know what they mean by "MPLAB 8 project files".

• Generates MPLAB X project files for all PIC side code generators, which lets you use the latest Microchip tools and processors.
• Also generates MPLAB 8 project files for all PIC side code generators, so you can work faster, with fewer IDE bugs. Great for maintaining and upgrading your existing projects, without having to learn an entirely new tool suite.

[mpgmike]

I originally bought HIDmaker FS (I wanna guess around 2015) which includes PBP code generation. It is for 8-bit PIC MCUs only. Later when I migrated to MPLABX and 16-bit MCUs I upgraded to FS-32. The FS was updated when I upgraded. The FS-32 does NOT generate PBP code (which is what it looks like the image in Post Blogs shows), but the lower-cost FS does. The FS-32 generates USB code for 8-, 16-, and 32-bit MCUs, while the FS only generates code for 8-bit versions.

[Robert Hedan]

So I did a thing...

"Trace Systems Inc sent you an invoice"

I figured I might as well upgrade to HIDmaker32, just in case I start playing with the big boys.



EDIT: Got a "special report" on HIDmaker coming as soon as I can figure what's going on with my programmer (yeah, I found my U2 programmer and it's also acting wonky).

[Robert Hedan]

I originally bought HIDmaker FS (I wanna guess around 2015) which includes PBP code generation. It is for 8-bit PIC MCUs only. Later when I migrated to MPLABX and 16-bit MCUs I upgraded to FS-32. The FS was updated when I upgraded. The FS-32 does NOT generate PBP code (which is what it looks like the image in Post Blogs shows), but the lower-cost FS does. The FS-32 generates USB code for 8-, 16-, and 32-bit MCUs, while the FS only generates code for 8-bit versions.

Mike,

Can you do me a favour and try to compile 2 demos for HIDmaker FS2 using MPLAB?

Copy it to a test folder first so you have your originals untouched.

- C:\Trace\HM32_v2_5\Projects_FS_2\SoftD
- C:\Trace\HM32_v2_5\Projects_FS_2\Varty32

I'm getting errors during compile, but I'm using MCS+5, so I'm trying to eliminate that as the cause before reporting a potential bug.

Error[113]   K:\PROJECT_V2\HIDMAKERFS2\VARTY32\PIC\PBP3_NEW\VARIETY32_M.ASM 866 : Symbol not previously defined (_OutVar32)
...
Error[113]   K:\PROJECT_V2\HIDMAKERFS2\VARTY32\PIC\PBP3_NEW\VARIETY32_M.ASM 867 : Symbol not previously defined (_OutArray32)
...
Error[113]   K:\PROJECT_V2\HIDMAKERFS2\VARTY32\PIC\PBP3_NEW\VARIETY32_M.ASM 1001 : Symbol not previously defined (_InVar32)
...
Error[113]   K:\PROJECT_V2\HIDMAKERFS2\VARTY32\PIC\PBP3_NEW\VARIETY32_M.ASM 1003 : Symbol not previously defined (_InArray32)
...

I tried using MPLAB v8 to compile them, but I'm stuck on this error (renamed to .BAS but made no difference).

Executing: "C:\PBP3\PBPX.EXE" -ampasmwin -k# -oq   -p18F4550 "Variety32_M.bas"
PICBASIC PRO(TM) Compiler 3.0.8.4, (c) 1998, 2013 microEngineering Labs, Inc.
All Rights Reserved.
ERROR: Unable to execute mpasmwin.Halting build on first failure as requested.
BUILD FAILED: Sun May 14 23:03:43 2023

I tried pointing the MPASM TOOLSUITE Executables to the versions I have in C:\PBP3\temp, that didn't do a difference. I googled, but got no help there.

And yeah, I need that SoftDetach demo for my project. :LOL:

Thanks!

Robert

[mpgmike]

Robert, first I cannot find any attachment to try to run. Secondly, I'm in limbo and don't have ready access to my PC with HIDmaker (I'm on my Mac).

[Robert Hedan]

Ah, ok.

We're not allowed to share code generated by HIDmaker, that's why I pointed to the source folders on my PC (hoping you hadn't deleted your demos by now).

I just realized it would be nice to have a HIDmaker forum on here; MeLabs distributes the product.

We "should" be able to share the source configuration files (ie: SoftD.hps); but would have to confirm with Dr. Miller first.

Unless you know of a HIDmaker forum somewhere?

Robert

[mpgmike]

No, I just know every time I called Dr. Bob he bent over backwards to help me in any way he could. The web site says he doesn't do this and that, but he bent his rules to help me get started. His customer service is beyond most, and about as good as I could hope for. Send him an email explaining what you're experiencing, and include a phone number. He will call you to discuss it more than likely.

[Robert Hedan]

We've already talked nearly 45 minutes on the phone a few days back, and that was just "ordinary talk, not a bug or anything". Definitely top notch.

Thing is, I'm using MCS+5, he tested with MPLAB. I don't know if it's something I'm doing wrong, and I never figured out MPLAB.

I've already sent him a lengthy email last night; did a review of his videos, and added comments and suggestions (he asked for it, he got it ).

I'm definitely a happy customer. Would love to help him any way I can, to spread the word on HIDmakerFS2.

Robert

[Robert Hedan]

Mike,

Is there a switch we're supposed to press to generate 64-bit code on the PC side?

Mine keeps generating Win32 and I don't know why. If I try to migrate in VS2022 from Win32 to x64, I get an error on one statement (compiles ok in Win32 though).

MS Flight Sim SDK needs an MFC app in x64, so I'm now using C++MFC instead of C++WinForm.

All these Windows terms are new to me except win32 and 64-bit. I'm only learning now "exactly" what MS meant on the SDK requirements. I hadn't picked up on the term MFC when I first read the specs earlier this year. At least now I know which code to generate.

Robert


EDIT: Oh farg, I just noticed that the HIDmakerFS2 page only mentions 64-bit alongside the Borland compilers; there's no mention in the Microsoft compiler section. I totally missed that.

I saw at the top "Generate CUSTOM source code for YOUR favorite PC compilers, and use their latest features and capabilities, including new frameworks, styling of your project's PC program, 64-bit and 32-bit compile targets, and more", and my vision blurred and I just skimmed the rest cause that's exactly what I needed.

https://www.tracesystemsinc.com/blog/new-enhanced-hidmaker-fs-2-for-8-bit-usb-pic-processors.html

Frack! 64-bit is a requirement to run the MS FS SDK.