I have a project that I need to move to a different development station.

I have copied the $prwra_db content to the new computer and also the folders under /usr/local/pwrp.

Is that all I have to do? (doesn't work, when I open the volume,I get build signature doesn't match and he starts to configure new root volume)

Complication: the new computer is a 64 but machine and old is a 32 bit.

Can i run the development station on 64bit and the process station and operator stations on 32 bit.

Is there any documentation about this?

Thanks
Martin

Hi Martin,

The BerkeleyDb database are not compatible in 64 bit Linux, so you have to dump the database to text file on 32-bit and reload the database on 64-bit. Dump the database by executing the first pass (dumpdb) in reload.sh. This will create the file 'volumename'.wb_dmp on $pwrp_db. Copy this file to the new machine (to $pwrp_db) and run reload.sh again, but now skip the dump pass by entering 'renamedb' as start pass.

The problem with 64 bit development station and 32 bit operator station is the plc program. It will be built for 64-bit linux and is not runnable on 32-bit. In theory it should be possible to build 32-bit programs on 64-bit by installing the 32-bit archives, but when I tried it the compiler insisted on choosing the 64-bit version for some archives anyway. If you don't have any plc progarm though, is should work.

/Claes

Thanks a lot, Claes for your always excellent support.

I tried this but I get some errors...

Enter start pass [dumpdb] > renamedb

---

Pass rename old database

---

Do you want to continue ? [y/n/go] y
-- Saving file /usr/local/pwrp/hotairsoldering/src/db/volhotairsoldering.db -> /usr/local/pwrp/hotairsoldering/src/db/volhotairsoldering.db.1

---

Pass load database

---

Do you want to continue ? [y/n/go] y
-- Loading volume volhotairsoldering
-- Processing line: 56
-- Building volume directory
I Volume directory loaded
I Database opened /usr/local/pwrp/hotairsoldering/src/db/directory.wb_load
-- Processing line: 8066
-- Building volume VolHotairsoldering
I Volume VolHotairsoldering loaded
Berkeley DB 5.1.25: (January 28, 2011)
info put: 0
Berkeley DB 5.1.25: (January 28, 2011)
info get: 0
int rc = m_txn->abort(): 0

---

Pass compile plcprograms

---

Do you want to continue ? [y/n/go] y
Berkeley DB 5.1.25: (January 28, 2011)
info get: 0
I Database opened /usr/local/pwrp/hotairsoldering/src/db/volhotairsoldering.db
-- Plc window generated H1-control-W
-- Not built for x86_linux
-- Plc window generated H1-control-W-Temperature1-W
-- Not built for x86_linux
-- Plc window generated H1-control-W-Temperature2-W
-- Not built for x86_linux
-- Plc window generated H1-control-W-Temperature3-W
-- Not built for x86_linux
-- Plc window generated H1-control-W-Airflow1-W
-- Not built for x86_linux
-- Plc window generated H1-control-W-Airflow2-W
-- Not built for x86_linux
-- Plc window generated H1-control-W-Airflow3-W
-- Not built for x86_linux
-- Not built for x86_linux

---

Pass create loadfiles

---

Do you want to continue ? [y/n/go] y
-- Creating loadfiles for database volhotairsoldering
Berkeley DB 5.1.25: (January 28, 2011)
info get: 0
I Database opened /usr/local/pwrp/hotairsoldering/src/db/volhotairsoldering.db
-- Not built for x86_linux
-- Working with load file volume 'VolHotairsoldering'...
-- Open file...
-- Successfully created load file for volume 'VolHotairsoldering'
-- 1400 objects with a total body size of 134232 bytes were written to new file.

---

Pass create bootfiles

---

Do you want to continue ? [y/n/go] y
-- Creating bootfiles for all nodes
-- Creating bootfile for node air-desktop
-- Plc thread generated priority 22, scantime 0.10000 s, 1 plcpgm's
-- Not built for x86_linux
-- Not built for x86_linux
-- Creating bootfile for node hotairsoldering
-- Plc thread generated priority 22, scantime 0.10000 s, 1 plcpgm's
-- Not built for x86_linux
-- Not built for x86_linux

-- The reload is now accomplished.
Please remove the dumpfiles: $pwrp_db/*.wb_dmp*
when you are satisfied with the reload.

The reload of the database seems to have been successful, but you are no longer able to build for 32-bit. If you want to build for 64-bit instead you have state this for both the node and the volume. Change the OperatingSystem in the NodeConfig object in the directory volume, and also in 'File/Volume attributes' in the menu when you have opened the configurator for the root volume.

/Claes

Thanks again, it works well.