Closed dschick closed 4 years ago
okay, found the answer to my own question.
It was obviously not a pytango but a tango issue.
The documenation was a bit thin at that point.
By adding -ORBendPoint giop:tcp::10000
to the command for starting the DS it is working.
Hi @dschick
Glad you got it sorted out. Another convenient method to do this is the using the DeviceTestContext
, which we normally use to launch device servers during automated tests. It can be used from the command line, something like this:
python -m tango.test_context plasma-debris-protector.PlasmaDebrisProtector --host 127.0.0.1
A full example here.
And the command line arguments for v9.2.5 can be seen here.
great, that is even more convinient. Maybe it it worth putting this a bit more prominant into the docs?
many thanks!
I agree this should be made visible in the documentation. I have also created an issue #354 to improve the command line options and help
great! I guess this will help many users.
Many thanks for the prompt replies
Hi,
I am currently developing a DS on a raspi and would like to test it without the need for a connection to a Tango-DB on a remote host. I found the
-nodb
option in the TANGO documentation. But when I start my DS with the following command:./plasma-debris-protector.py raspi -nodb -dlist id12/motor/1
I do get the following error:Otherwise the DS works fine in connection with the Tango DB. I am using PyTango 9.2.5 from the raspi repos.
Best
Daniel