4.0 .MER file

Best VPN

This topic contains 5 replies, has 2 voices, and was last updated by Fred Graham Fred (a.k.a. PLCGuru) 9 months ago.

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #991
    Kevin Cotton
    Kevin Cotton
    Participant
    Karma Points: 10
    Rank: Padawan

    I am running FTVME 8.20 on my laptop and v6.1 on a VM. I also have RSView on another VM. I have a panelview plus running a 4.0 runtime. I have a copy of the .mer in 8.20. I do not have the original 4.0 .apa file. Is there any way to create a 4.0 .mer with what I have?

    #992
    Kevin Cotton
    Kevin Cotton
    Participant
    Karma Points: 10
    Rank: Padawan

    And version 8.2 will only let me create runtime files down to version 5.

    #993

    Hi Kevin and welcome to the forum!

    My advice would be to flash the panelview to a newer firmware. If it’s an older panelview which it sounds like it is I would recommend flashing it to version 5.1 which is the latest you can go on those. You will also need to use the Legacy Conversion Tool in a 32 bit environment to export all the tags and import them into your new version. FTV 6.1 and on use SQL Server as their backend database. There is a technote here if you have a techconnect contract.

    There is a little work here to do but in the end it’s the best route.

    If you need some assistance upload the .mer and I can see what I can do.

    #998

    Hi Kevin, any progress on your problem! Let us know how we can help further!

    #1046
    Kevin Cotton
    Kevin Cotton
    Participant
    Karma Points: 10
    Rank: Padawan

    I loaded my project on a Panelview we had in stock, and swapped it with the PvP in question (without shutting the machine down). Took that one to my office and flashed it up as high as the hardware would let me (5.09), it is a ~12 year old old pvp1000. Worked like a charm. I really hoped there was a way to make it work without having to flash it up. We have several panelviews running frn < 5 and some of them I cannot pull with the equipment running due to our electrical safety policy.

    #1047

    Hi Kevin,

    Glad you got it sorted. I get it, managing software revisions and firmware revisions on a plant-wide scale is a task unto itself. I do think you should think about a plan to migrate those older firmware/pvp’s during scheduled downtime, there are advantages to version 5 and above such as mer upload’s right from the terminal (in case you lose or don’t have the.apa file), activex compatibility just to name a few.

    Come back and visit us!

Viewing 6 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic.