Hi Milan
Yes, as stated in PDF, display is not part of default configuration.
That means its default state is Disabled and Stopped.
So to get it working, the PDF says use management server and page /display
So the state changes to Enabled and Running
The controller works using two instances of focuser settings. 1 is saved in Filesystem, other is a cached memory version for quick access.
So when you enable and run the display, the changes are in the cached memory.
After 60-90s the cached memory is written into filesystem (saved in a file).
If you reboot before time is up, it does not get saved so on the reboot its disabled and stopped.
To view the controller file in file system - see pdf - it shows you how to view the file,
So after changing settings, wait 90s then see the controller file ussing the management server get command - it will show the contents of the file, and you should see the changed state - the get commands you can see by using /cmds as a page in management server.
Once its changed, you can reboot.
Regards
Robert
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
I’m using the following display configuration:
set?display=enable
set?displaystatus=start
After that, the display turns on and functions normally.
Question:
What do I need to configure to make the display start automatically after power on?
I'm attaching my config.h, board_config, and cntlr_config.jsn files for reference.
Thank you!
Hi Milan
Yes, as stated in PDF, display is not part of default configuration.
That means its default state is Disabled and Stopped.
So to get it working, the PDF says use management server and page /display
So the state changes to Enabled and Running
The controller works using two instances of focuser settings. 1 is saved in Filesystem, other is a cached memory version for quick access.
So when you enable and run the display, the changes are in the cached memory.
After 60-90s the cached memory is written into filesystem (saved in a file).
If you reboot before time is up, it does not get saved so on the reboot its disabled and stopped.
To view the controller file in file system - see pdf - it shows you how to view the file,
So after changing settings, wait 90s then see the controller file ussing the management server get command - it will show the contents of the file, and you should see the changed state - the get commands you can see by using /cmds as a page in management server.
Once its changed, you can reboot.
Regards
Robert