POGO - TANGO Controls

# 9 years ago
saro	Hi AlL I have some questions related to pogo. 1) What is "write hardware at init" button from edit attribue window? And what is the difference between "memorized" and "write hardware at init". 2)What is "Allocate-Read data member" button from the same window. What is its use. What is the effect of selecting or deselecting that button. 3)I have developed a code which adds the new attributes at runtime. But can I change the type and dimensions of the attribute at runtime using add_dynamic_attribute(); What are the application of dynamic attribtes. 4) What are class properties and device properties. Why the device property and class property defined through pogo does not reflect on jive. Could anybody help me to understand the basics of pogo and use of every field on pogo window. Thanks and Regards Sarojini B. Sutar

# 9 years ago

Hi AlL

I have some questions related to pogo.
1) What is "write hardware at init" button from edit attribue window? And what is the difference between "memorized" and "write hardware at init".

2)What is "Allocate-Read data member" button from the same window. What is its use. What is the effect of selecting or deselecting that button.

3)I have developed a code which adds the new attributes at runtime.
But can I change the type and dimensions of the attribute at runtime using add_dynamic_attribute();
What are the application of dynamic attribtes.

4) What are class properties and device properties. Why the device property and class property defined through pogo does not reflect on jive.

Could anybody help me to understand the basics of pogo and use of every field on pogo window.

Thanks and Regards
Sarojini B. Sutar

# 9 years ago
Pascal	Hi Saro 1) Memorized means write value will be stored in database and set to your attribute at next start up. Write hardware at init meas the methods *write_attr_hardware()* and *write_TheAttribute()* will be called at start up. 2) *Allocate-Read data member* means that Pogo will generate code to allocate (and delete) a variable to manage attribute content. If you want to manage by yourself or use a hardware memory you can unselect. 3)You cannot change maximum size or type at run time. Only the real size. Dynamic attributes are attributes able to be created/deleted at runtime. 4)Device/Class properties are used to configure devices/classes. They cannot be reflected in jive, Pogo run without database (and of course not with all existing databases). You have to create them if needed. Some properties use default values and does not need to be created. Regards Pascal

# 9 years ago

Pascal

Hi Saro

1) Memorized means write value will be stored in database and set to your attribute at next start up.
Write hardware at init meas the methods write_attr_hardware() and write_TheAttribute() will be called at start up.

2) Allocate-Read data member means that Pogo will generate code to allocate (and delete) a variable to manage attribute content. If you want to manage by yourself or use a hardware memory you can unselect.

3)You cannot change maximum size or type at run time. Only the real size.
Dynamic attributes are attributes able to be created/deleted at runtime.

4)Device/Class properties are used to configure devices/classes.
They cannot be reflected in jive, Pogo run without database (and of course not with all existing databases).
You have to create them if needed.
Some properties use default values and does not need to be created.

Regards
Pascal

# 9 years ago
TCS_GMRT	Hi All, I have one doubt related to following syntax: DbDevImportInfo Database::import_device(string &); I have tried the code given in tango_manual_81. The code is as follows: `string s = string("gmrt/c0/tcs"); DbDevImportInfo my_device_import; my_device_import = db->import_device(s); cout << "Device " << my_device_import.name << endl; cout << "Exported " << my_device_import.exported << endl; cout << "IOR " << my_device_import.ior << endl; cout << "Version " << my_device_import.version << endl; cout << endl;` But the above code is throwing this exception: `Tango exception Severity = ERROR Error reason = API_CorbaException Desc : BAD_INV_ORDER CORBA system exception: BAD_INV_ORDER_ORBHasShutdown Origin : Connection::command_inout() Tango exception Severity = ERROR Error reason = API_CommunicationFailed Desc : Failed to execute command_inout on device sys/database/2, command DbImportDevice Origin : Connection::command_inout() Received a CORBA_Exception Exiting` So please help me to resolve this doubt. Thanks and Regards, Tcs-Gmrt Regards, TCS_GMRT

# 9 years ago

TCS_GMRT

Hi All,

I have one doubt related to following syntax:
DbDevImportInfo Database::import_device(string &);
I have tried the code given in tango_manual_81. The code is as follows:


        string s = string("gmrt/c0/tcs");

	DbDevImportInfo my_device_import;
	my_device_import = db->import_device(s);
	
	cout << "Device " << my_device_import.name << endl;
	cout << "Exported " << my_device_import.exported << endl;
	cout << "IOR " << my_device_import.ior << endl;
	cout << "Version " << my_device_import.version << endl;
	cout << endl;

But the above code is throwing this exception:


Tango exception
Severity = ERROR 
Error reason = API_CorbaException
Desc : BAD_INV_ORDER CORBA system exception: BAD_INV_ORDER_ORBHasShutdown
Origin : Connection::command_inout()

Tango exception
Severity = ERROR 
Error reason = API_CommunicationFailed
Desc : Failed to execute command_inout on device sys/database/2, command DbImportDevice
Origin : Connection::command_inout()

Received a CORBA_Exception
Exiting

So please help me to resolve this doubt.

Thanks and Regards,
Tcs-Gmrt

Regards,
TCS_GMRT

# 9 years ago
Andy	Can you send a complete program so I can try to reproduce it? Can you test the DbDevImportinfo command with the test device tool in jive? BTW your question is not related to Pogo. It would be easier for others to answer if you opened a new thread with a different subject. Andy Edited 9 years ago