Want to move NL220 database to Lonmaker

[joey791]

Can anyone point me in the right direction of how to do this? We have a job with a TAC Vista system running NL220, I'm hoping to get rid of the Vista front end and take over the system and replace controllers with Distech as they go bad. I've been Googling database transfer between these 2 programs but haven't found any relevant information. If someone could point me in the right direction it would be appreciated.

[crab master]

Why not leave NL220 or buy it and leave a site copy?

Have you contacted Echelon?

Also did you get the toolpack?

[joey791]

Don't know Crab, not sure what direction to head and what is the best thing to do..............................................


I did get the toolpack, thanks, Dropbox rules.

[381engineer]

Sysint says incrediously "Are you guys serious?"

But seriously, isn't NL220 just an LNS tool same as Lonmaker,NI or Lonwatcher? There has to be an LNS database somewhere in the directory and you should be able to copy it and load it any LNS tool.

[joey791]

Sysint says incrediously "Are you guys serious?"

But seriously, isn't NL220 just an LNS tool same as Lonmaker,NI or Lonwatcher? There has to be an LNS database somewhere in the directory and you should be able to copy it and load it any LNS tool.

Don't disagree, but I can't find where its at

[381engineer]

Typically it is in the NLPrj folder. Just point Lonmucker to it and you are ready to go.

NL220 is the better tool to use. Less overhead, works better.

Maybe consider lightweight client.

So I've been told.

[joey791]

Yeah I have a copy of everything in that folder, Lonmaker doesn't open any of the files or folders.

[381engineer]

Yeah I have a copy of everything in that folder, Lonmaker doesn't open any of the files or folders.

Can you email it to me?
I could try my Circon tool and save as lonmaker back up.

[joey791]

Couldn't Gmail it so I shared a dropbox folder with you

[381engineer]

Couldn't Gmail it so I shared a dropbox folder with you

Got it.

I"ll give it a try this weekend.

[joey791]

Thanks for the help

[AtticusFinch]

The NL220 tool is a very acceptable tool to use with LNS, likely the most useful. If you open up the NL220 tool it has the pathway to the database when you start. In the Lonworks\bin folder run the browser and easily find the source of your database.

There is no necessity to transfer a database for using LNS if you have access to the machine with the LNS database. Only transferring the database file to a different machine shall create more and different problems for your endeavor. Why is there a necessity to change the management system in this instance?

[joey791]

Because the customer doesn't like the company that installed it(or just wants us to deal with mechanical and controls)

[amigo]

He is talking about the Lon management system (NL220 software), he is saying why don't you just use it rather than trying to use Lonmaker.

[joey791]

He is talking about the Lon management system (NL220 software), he is saying why don't you just use it rather than trying to use Lonmaker.

Because I am more familiar with Lonmaker and am unsure about the licensing and how it works out with the existing software, also first time running into this so I want to know how to do this in case I don't have a choice.

[381engineer]

Got it.

I"ll give it a try this weekend.

Joey
No luck, do you have or can you make a new back up of the DB?

[joey791]

How do I go about doing that? With the NL220 software or Lonmaker?

[381engineer]

How do I go about doing that? With the NL220 software or Lonmaker?

I found this online
http://buildingskb.schneider-electri...220_Manual.pdf
http://dionabms.ru/file_manager/data...utorial_EN.pdf
http://www.lonix.com/training/Lecture_NL220.pdf
Hope this helps

[crab master]

http://buildingskb.schneider-electri...w.php?AID=4198

Interesting statement, I knew I heard/read it wasn't just copy paste and reload. "NOTE: Migrating from NL220 (or other LNS management tool) back to LonMaker is a little less seamless because LonMaker utilizes proprietary Visio drawings for viewing the network, and these are not native to the LNS database. Viewing the network may be difficult with the automatically generated Visio drawings."

[joey791]

http://buildingskb.schneider-electri...w.php?AID=4198

Interesting statement, I knew I heard/read it wasn't just copy paste and reload. "NOTE: Migrating from NL220 (or other LNS management tool) back to LonMaker is a little less seamless because LonMaker utilizes proprietary Visio drawings for viewing the network, and these are not native to the LNS database. Viewing the network may be difficult with the automatically generated Visio drawings."

Actually went through all of those earlier this week Crab I also skimmed and searched 381s link and I have yet to find a single clear cut procedure lol