Looking for way to manually set Display ID using RISEBERRY

  • 1
  • Question
  • Updated 2 years ago
  • Answered
Archived and Closed

This conversation is no longer open for comments or replies and is no longer visible to community members.

Hello,

I'm using the RISEBERRY build of linux for the Raspberry Pi 2 and it's working really well. The only issue for me is that I cannot find a configuration file, or a rvplayer directory, where I can go and change the display ID.

I know that I can set the display ID when I turn on the unit for the first time, but I'm trying to help my client and have the cards pre-configured. It was easy to find /home/rvplayer/ and the corresponding config file on the older RPi, but this build has me stumped!

Thank you...
Photo of sshank

sshank

  • 1,186 Points 1k badge 2x thumb

Posted 3 years ago

  • 1
Photo of Blake Freeman

Blake Freeman, Official Rep

  • 36,116 Points 20k badge 2x thumb
sshank,

You'll need to change the Display ID by using the Web Page Widget.

Create a new presentation containing the Web Page Widget, in the url portion, type http://localhost:9449/config. Assign this presentation to the display that you wish to change the Display ID on. Once the presentation is on the Display, you'll be able to use this web page to change the Display ID.
Photo of sshank

sshank

  • 1,186 Points 1k badge 2x thumb
Thanks Blake

That doesn't quite solve the problem I have. I can already assign the display ID the first time I start the display -- in the absence of a stored ID the player asks for a display or claim ID. And if I want to change it, I can simply delete the display from rise vision and then it will ask me again.

However, in the old system, I could configure my SD cards in advance, and then edit /home/rvplayer/RiseDisplayNetworkII.ini in advance (link). I would like to find this file in RISEBERRY, but have not been able to locate it on my own. I'm sure there is some config file in there I could edit.

The reason I want to do this is so I can provide backup micro sd cards to my client for each of the three displays we have there, so that they can replace them in case of corruption without having to find a keyboard/mouse, connect it, and then keep track of display IDs to type in.

Thanks
Photo of Blake Freeman

Blake Freeman, Official Rep

  • 36,116 Points 20k badge 2x thumb
sshank,

The Rise Player for Raspberry Pi b+ was what we called a Native Player. It installed directly to the media player, and had several user editable pieces, including RiseDisplayNetworkII.ini.

The community provided guide for Raspberry Pi 2 utilizes the Rise Player Chrome App Extension. The CAP does not have a user editable text file that contains a display ID. Any modifications to the ID have to be done through the browser.
Photo of sshank

sshank

  • 1,186 Points 1k badge 2x thumb
OK. Thanks for the update. They will have to learn how to enter display IDs :) And it makes my life easier as well...
Hello all, did you ever troubleshoot a way to get the Riseberry installation to remember the Display ID, even when the device is power cycled?
Photo of Lee Perkins

Lee Perkins

  • 120 Points 100 badge 2x thumb
I am also having an issue getting the PI 2 setup to remember the Display ID after power cycle.