News:

  • April 16, 2026, 03:39:57 AM

Login with username, password and session length

Author Topic: Memory image data location  (Read 5053 times)

Controls Guy

  • Internal Dev
  • Hero Member
  • ****
  • Posts: 3607
  • Darth Ladder
Memory image data location
« on: September 09, 2020, 08:19:06 PM »
Is a memory image stored within the DMD project file?    I was looking to upload a partial image from one BRX and download it to another running a different version of the project, but it doesn't look like that's possible with the current UI, so I thought to copy the data file over to the target project location, change the name, etc., but while the project said it had an image associated, there was no file for it in the project directory.

In this case, I only needed to copy the MHR table, so it was easy to just export from Memory View, then go do an import from inside the target project, but I was surprised not to be able to find the MIM data file.
I retract my earlier statement that half of all politicians are crooks.  Half of all politicians are NOT crooks.  There.

franji1

  • Bit Weenie
  • Host Moderator
  • Hero Member
  • *****
  • Posts: 3803
    • Host Engineering
Re: Memory image data location
« Reply #1 on: September 09, 2020, 10:41:10 PM »
Is a memory image stored within the DMD project file?    I was looking to upload a partial image from one BRX and download it to another running a different version of the project, but it doesn't look like that's possible with the current UI, so I thought to copy the data file over to the target project location, change the name, etc., but while the project said it had an image associated, there was no file for it in the project directory.

In this case, I only needed to copy the MHR table, so it was easy to just export from Memory View, then go do an import from inside the target project, but I was surprised not to be able to find the MIM data file.
Yes, it is stored in the .dmd file.

  • Open the Source .dmd project
  • Open the Memory Image Manager below the Tools menu.
  • Select the specific region you want to export (e.g. MHR).
  • Click on the Modify Region Data button
  • In the Modify Memory Region dialog, click on the Export toolbar button (the far right button on the toolbar)
  • Save it to disk
  • Close the Source .dmd project

Not sure if you need it merged into the MIM of the destination, or just written to the PLC.

If you need the values as part of the Destination project, do a similar function as above, except do the IMPORT button on the Modify Memory Region dialog with the exported file.

If you just need to write it to the PLC, then just open a Memory View online to the PLC, and do the IMPORT from the Memory View, then write the contents to the PLC from the Memory View.

Controls Guy

  • Internal Dev
  • Hero Member
  • ****
  • Posts: 3607
  • Darth Ladder
Re: Memory image data location
« Reply #2 on: September 10, 2020, 01:53:59 PM »
I just needed them written.    I had online access to both source and target PLCs, so I opened a Memory View on the source and exported to CSV, then imported and wrote in a Memory View on the target.

I did notice the import & export options in the MIMs Edit Region Dialog, though, and that would have been helpful if I hadn't been able to go online with the source PLC.
« Last Edit: September 10, 2020, 03:02:01 PM by Controls Guy »
I retract my earlier statement that half of all politicians are crooks.  Half of all politicians are NOT crooks.  There.

franji1

  • Bit Weenie
  • Host Moderator
  • Hero Member
  • *****
  • Posts: 3803
    • Host Engineering
Re: Memory image data location
« Reply #3 on: September 10, 2020, 01:59:00 PM »
I just needed them written.    I had online access to both source and target PLCs, so I opened a Memory View on the source and exported to CSV, then did imported and wrote in a Memory View on the target.

I did notice the import & export options in the MIMs Edit Region Dialog, though, and that would have been helpful if I hadn't been able to go online with the source PLC.

That works!

The Memory Image Manager Modify Region dialog is based on Memory View, so the import/export mechanisms are compatible.

Note that MIM is ONLY the blocks' RETENTIVE range (e.g. could be MHR2000-MHR2047), while the Memory View defaults to the whole block (but you can tweak it to any sub-range of the block).

Glad you figured it out.