I was planning to play a little with my 8x8 Led Matrix module. Which is discontinued from GHI.
After installing 4.3 it does not appear in the designer, not even with a sign saying “cannot be used”. Then I tried messing with some download of the old driver source-code, which unfortunately is infiltrated by new fancy namespaces, and I decided to take a halt.
Can you please give some generic guidelines for all of us that in the next 10 years still are planning to use your great modules from previous times, which are now discontinued and not supported
Thanks for that, took it for a spin with a Cerberus newly updated, and the LEDMatrix module.
It works well in the designer, the code seems ok, and compiles fine. But deployment fails.
Cannot deploy the base assembly ‘mscorlib’, or any of his satellite assemblies, to device - USB:Gadgeteer twice. Assembly ‘mscorlib’ on the device has version 18.104.22.168, while the program is trying to deploy version 22.214.171.124
Ok, do you mean porting the driver? If I have 4.3 on the hardware, and uses a legacy Gadgeteer module, that module requires (among other stuff) Gadgeteer 4.2 and mscorlib 4.2 which cannot be deployed to the hardware.
The source can be downloaded, and I can modify the driver to fit 4.3, but thats not neat.
Not sure what John mean by that sentence. Up to date? Works?
UPDATE: I got my LedMatrix working on 4.3, by doing this:
[ul]1. Create a Gadgeteer 4.3 project
2. Add the sourcecode for your legacy module from the legacy pack in this case ledmatrix_42.cs
3. Add “Gadgeteer.Modules.GHIElectronics.LEDMatrix ledmatrix = new GTM.GHIElectronics.LEDMatrix(2);” or something similar to initialize the module
4. Port the code to match 4.3 in this case only one line. (What Andre thinks “easy”)[/ul]
AND REMEMBER: DONT USE THE DESIGNER FOR LEGACY MODULES!
This is not as nice as I hoped for, can GHI assist in finding a nicer way?
@ njbuch - That will only be required for modules that we never ported to 4.3, like the LED Matrix. Many of the modules are already ported to 4.3 and work with no issue.
As for what I meant by “It is currently up to date and works with the latest 2014 R2 SDK.” the Gadgeteer modules in the discontinued SDK were compiled against the 2014 R2 NETMF SDK. That means the 4.3 mainboards are compiled against the 4.3.3 DLLs while the 4.2 boards are compiled against 4.2.11 (or 4.2.6). All modules were compiled against 2.43.900 Gadgeteer core.
We don’t plan to support these discontinued modules beyond releasing the source and occasionally building an installer against a released SDK of ours.
Porting completely to 4.3 is pretty easy. Most of the API changes are just changing I/O constructors to the factory methods. Then you just have to add a 4.3 entry in the installer project in common.wxi and GadgeteerHardware.xml.
@ Dave McLaughlin - Cobra II WiFi was moved to the Discontinued Gadgeteer Products SDK when we discontinued the board. Since that mainboard driver was written after we moved to 4.3, there was no 4.2 driver made for it. Cobra II Eco remains with 4.2 and 4.3 drivers.
Cobra II Net and Cobra II Eco Extender were also moved to the discontinued SDK. Since the eco extender board already had a 4.2 driver, it was kept.
I did just test and those boards work fine with no reference issues. I would try to uninstall all NETMF things and try again. Make sure you don’t have any prior NETMF SDKs installed except 4.3 QFE1.
@ John @ njbuch - I try to update a MF4.2 projet with G120HDR, LedMatrix and WifiRs21 to MF4.3 with last SDK 2014-R5.
I know that LedMatrix is a discontinued product and I have read instructions to proceed with discontinued modules.
I have seen this thread and the njbuch job on CodeShare https://www.ghielectronics.com/community/codeshare/entry/914 but when I try to use LedMatrix classe on MF4.3 with last SDK, I have an error because the namespace “Gadgeteer.Modules.DaisyLinkModule” do not exist…