PLUS+1 User Forum

PLUS+1™ Hardware => Controllers => Topic started by: dlewis on November 13, 2013, 09:41:26 PM

Title: MC050-110 lg vs. nl
Post by: dlewis on November 13, 2013, 09:41:26 PM
What's the difference between the lg hdw version and the nl hdw version?  Both versions, according to the data sheets, call out the same part number for the controller itself.
Title: Re: MC050-110 lg vs. nl
Post by: Daniel on November 26, 2013, 12:52:26 PM
Hi dlewis

lg = One that supports old symbols to enable older applications to be recompiled without changes.
nl = One that is used to unleash the full potential of the new hardware that supports new symbols, naming conventions etc. and will be the base for future development.


Best regards
Daniel
PLUS+1® HelpDesk
Title: Re: MC050-110 lg vs. nl
Post by: BRIan on December 15, 2013, 10:33:16 PM
So what does lg and nl stand for? It's not as obvious as old and new, so how do we remember it?
Title: Re: MC050-110 lg vs. nl
Post by: oiltronic on February 03, 2014, 06:06:25 PM
lg = LeGacy
nl = New...Language, Land, Love?
Title: Re: MC050-110 lg vs. nl
Post by: bgtwuk on February 03, 2014, 06:26:11 PM


Love..?...  Really? :)
Title: Re: MC050-110 lg vs. nl
Post by: Daniel on February 05, 2014, 02:10:52 PM
Hi there.

Good suggestions!

But actually it stands for:
lg = legacy
nl = non-legacy


Best regards
Daniel
PLUS+1® HelpDesk
Title: Re: MC050-110 lg vs. nl
Post by: niteRider on May 06, 2014, 11:28:20 PM
I converted an MC024-10 application over to an MC024-110 yesterday, and using the -lg version was able to compile without a problem.  I did the recompile on my Desktop, and downloaded the .lhx to the new controller also from my desktop.

I took the controller out to a machine, opened my service tool on my laptop, and connected to the system.  When I scanned the system, I saw the new controller on-line, but when I went to my parameter and log functions, none of my Checkpoints or Parameters would show up.

Anyone else had this problem?  I ended up repeating the recompile process of the original Project File on the laptop to turn it into a -110, and after re-downloading, was able to see Checkpoints and Parameters normally.

I sent the controller to a customer, and had him hook up his laptop to check the unit after installation, with the same service tool... he's having the same problem I did yesterday... none of the Checkpoints or Parameters are visible, but the Controller is showing up under the ECU list and appears to be functioning correctly... he just can't make any adjustments or view any log functions in the service tool.

I'm running GUIDE version 7.0.7.1 on both machines.

Title: Re: MC050-110 lg vs. nl
Post by: niteRider on June 27, 2014, 05:44:37 PM
Was able to reproduce this again... appears that I can only connect to the controller and see all the checkpoints and parameters if I compile the converted project on the same machine.  If I try to connect to the controller with another computer, I get the Invalid Format Error.

Sent an email to the Helpdesk and will post result.
Title: Re: MC050-110 lg vs. nl
Post by: 240glt on August 13, 2014, 12:22:12 PM
Hi there.

Good suggestions!

But actually it stands for:
lg = legacy
nl = non-legacy

I was just about to start a new project with a MC50-120. There is three different OS: lg, nl, os. What does os stand for? And which one should I use for a new project?

Regards
Kent
Title: Re: MC050-110 lg vs. nl
Post by: niteRider on August 20, 2014, 10:58:10 PM
Go here:
http://powersolutions.danfoss.com/products/mobileelectronics/plus1guide/plus1guidedownloads/index.htm
and click on the 'Readme' next to the package download. 

nl = One that is used to unleash the full potential of the new hardware that supports new symbols, naming conventions etc. and will be the base for future development.

lg = One that supports applications with old-style naming conventions to be able to re-compile MC0XX-0XX applications without changes.

os = One that supports old CAN and EEPROM symbols.

That said I'm not sure when you would want to use the OS version... if converting, I'd start with the -lg and if you have issues then try to -os.  If starting from scratch, use -nl.


hope that helps... I remember hunting for this a while back and hopefully can save the next guy some time : )

Title: Re: MC050-110 lg vs. nl
Post by: 240glt on August 26, 2014, 10:21:46 AM
Thanks NiteRider!  :)
I thought that I had looked everywhere... But that readme document is not included into guide when the hwd files are installed.
Title: Re: MC050-110 lg vs. nl
Post by: Loader on December 12, 2014, 03:05:39 PM
Hi NiteRider, have you solved it? I have same problem!
Title: Re: MC050-110 lg vs. nl
Post by: niteRider on December 17, 2014, 02:36:09 PM
Not really a fix per-se, but a least a workaround:

--On the machine you compiled the -lg Project on, create a new Service Tool and create a Parameter Group 'All Params' (or whatever you want to call it) and add all parameters for the Controller you converted.  I'm pretty sure you have to do it on the original machine that Compiled the new -lg Project or it will not work.

--Copy the newly created Service Tool over to a machine that is getting the 'Invalid Format' error via flash drive, email, etc.

--Power up the controller and connect the 'Invalid Format' machine to it via CG150, then launch the Service Tool you created.

--You should get the 'Invalid Format in File' error on the first system scan.  If you do not, close out the Service Tool and try again.  It took me a couple tries sometimes...

--When you get the 'Invalid Format in File' error on the first scan, immediately re-scan the system (File-->Scan System or press F4).  You should be able to see Parameters and Checkpoints after rescanning.  Strangely enough, once you do this, all Service Tools created for this controller (even ones created under the previous versions) will scan and see Parameters and Checkpoints normally.

It sometimes took several tries and I found that if you do anything besides re-scanning after the initial 'Invalid Format' scan, it doesn't work.  The main drawback is that you have to do this on any machine that exhibits this error... in my case, I had several Field Service guys and customers that had to do it, so I suspect it has something to do with the machine that I compiled the -lg conversion on... the fact that a Service Tool created on that same machine seems to be the key to fixing it seems to support that hypothesis.  Unfortunately, Randy was unable to reproduce so it remains a bit of a mystery why this happens.  Perhaps as more people run into this they will be able to gather enough data to pin it down.

Hope that helps... if you cannot get this to work or doing this on all your Service Tool machines in the field is not an option, you'll want to start from scratch with a new Project built around -nl hardware... that's what I ended up doing before I was able to figure out this workaround via trial and error.  I got pretty good at exporting and importing pages, and it ended up being a good opportunity to clean up my code.  Having two machines with a full version of GUIDE side-by-side makes it a fairly painless process, just a little time consuming to make sure you hook everything back up correctly and you have to pay close attention to signal naming to avoid mismatches between pages.

Good luck!
Title: Re: MC050-110 lg vs. nl
Post by: Loader on December 17, 2014, 03:11:30 PM
Thank you very much!
I have the problem with MC024-110 instead the MC050-110 is ok.
We sometime have solved making a recover ECU with a Service Tool empty and than download again the application, but not always it works... :( overall because we often don't see the ROP...
When this procedure works, the ECU is visible and all is ok, but for strange causes another day the problem return again....
we have compiled the project with different PC but it is the same...I have tried also with S.Tool 7.1 but I think is better 7.0 for this problem...
I try with your workaround.
Thanks again, bye
Title: Re: MC050-110 lg vs. nl
Post by: niteRider on December 17, 2014, 03:17:46 PM
Good idea... it didn't occur to me to try Recovering the ECU.  Make sure you share any insight with the Helpdesk/Randy so they can keep an eye on it.

Have a good one!
Title: Re: MC050-110 lg vs. nl
Post by: Loader on December 17, 2014, 03:24:31 PM
oh, yes. Our Danfoss contact person had already shared this problem with Helpdesk.
Good luck  ;)
Title: Re: MC050-110 lg vs. nl
Post by: Daniel on December 19, 2014, 03:06:56 PM
Hi

We can inform that we have found a bug in the HWD for the MC024-110. When the controller is scanned, only a part of the PLG-file is uploaded (the part with controller default signals, inputs, outputs etc). No NV-memories or ROP information is uploaded to the PC.

It works as long as you use the same computer as when you downloaded the LHX, but not when you connect another computer to the controller.
This is because at download, the PLG will be copied directly from the LHX file to the PLG folder in GUIDE and hence that part of the information is already stored.

The issue is reported to the developers and will be resolved in the next release of HWD.

Meanwhile, if you have a customer far away and do not want to send a LHX file to them, you may instead just send them the PLG file created on your PC and ask them to go to File -> Install Diagnostic Data..., hit Install and then chose the PLG file sent to them.
On a Windows 7 system, the PLG files are normally found under C:\Users\[Your user name]\AppData\Roaming\Danfoss\PLUS1\CommonData\GUIDE Service Tool\PLG

Please report to plus+1helpdesk@danfoss.com if you have additional information that you think will be of our interest.


Thanks!
Daniel
PLUS+1® HelpDesk