Update broke firmware

Support forum for users of the M1 Build

Update broke firmware

Postby aNinjaneer on Tue Aug 08, 2017 10:57 am

I just did an update on M1 Build (1.4.0.131) that included an update for the "MoTeC Control" module (to 1.12 build 0033). This update seems to have broken every control object in the package. When I click on the objects, it just says [CObjUnknownType]. Has anyone else dealt with this? I assume there is no easy fix to revert back to before updating it. I've had to be cautious with version control, but things like this make me thing it's necessary. I assume the only way to revert back is to downgrade the module version and make all of the changes I did previously to match what it was before. This is really frustrating. I hope I can get it all back to how it was so I don't screw up any functionality in the firmware. Attached are some screenshots of what I'm seeing. Sorry if they look humongous for you, as they do for me. Not sure how to resize them on here once they're uploaded.

Screen Shot 2017-08-07 at 6.41.35 PM.png
Screen Shot 2017-08-07 at 6.41.35 PM.png (1.5 MiB) Viewed 14784 times


Screen Shot 2017-08-07 at 6.44.32 PM.png
Screen Shot 2017-08-07 at 6.44.32 PM.png (1.21 MiB) Viewed 14784 times
Last edited by Stephen Dean on Tue Aug 08, 2017 2:04 pm, edited 1 time in total.
Reason: Resized images
aNinjaneer
 
Posts: 27
Joined: Tue Apr 05, 2016 4:57 am

Re: Update broke firmware

Postby Stephen Dean on Tue Aug 08, 2017 2:08 pm

Can you post a screen capture of the errors that come up when you Validate the Project.
Stephen Dean
MoTeC Research Centre Melbourne, Australia
User avatar
Stephen Dean
Site Admin
 
Posts: 1731
Joined: Tue Dec 02, 2014 10:29 am
Location: Melbourne

Re: Update broke firmware

Postby John Reed on Fri Aug 11, 2017 4:32 pm

I had the same thing happen. That latest version of the "control" module 1.12.33 does not load correctly when you update to it. Simply reverting back to the previous version will fix your project with no issues. But yes the v33 update does seem to have something needing attention. I was on system v51 also, with all other modules up to date (as of today).
John Reed
Motec Sales/Install/Tuning/Support
johnreedracing@gmail.com
John Reed
 
Posts: 31
Joined: Thu Jul 10, 2008 5:58 pm
Location: Portland, Oregon

Re: Update broke firmware

Postby Stephen Dean on Fri Aug 11, 2017 5:49 pm

Hi,

This is being investigated at the moment, with a resolution early next week. At this point in time, please revert back to 1.12.0032, the change made in 0033 is a project specific change that will not be used in the GP Packages.
Stephen Dean
MoTeC Research Centre Melbourne, Australia
User avatar
Stephen Dean
Site Admin
 
Posts: 1731
Joined: Tue Dec 02, 2014 10:29 am
Location: Melbourne

Re: Update broke firmware

Postby aNinjaneer on Tue Aug 15, 2017 11:47 am

So I reverted back to the previous version and most things were OK. I had to re-set a couple parameters for things like boost control, but it wasn't too bad. I've learned to create more frequent versions, now, especially when trying to update anything.
aNinjaneer
 
Posts: 27
Joined: Tue Apr 05, 2016 4:57 am


Return to M1 Build

Who is online

Users browsing this forum: No registered users and 9 guests