Bright Sign XD1033
-
Hi guys,
Previously I was using a Raspberry Pi 3 to display my dashboard pages. I thought it was sufficient, but the RAM usage of Chromium often resulted in the page crashing. I also used IceWeasel on the Pi but as the RAM went down from 70% usage to 30%, the transitions between the dashboard pages has become slower (about 15 seconds) and the gauges take a long time to load.
I have been suggested to use BrightSign boxes, the particular box I am using is a XD1033: https://www.brightsign.biz/digital-signage-products/HD-product-line/HD223
They are used a lot at our organisations for many HD digital displays.However, when I plug it in I get the follow error: Error bootstrapping mango app:[ng:area] http://errors.angularjs.org/1.6.6/ng/area?p0..... (See picture for full error).
Based on the XD1033 can you suggest why this is happening?
-
Strange they don't list how much ram it has or if it supports JavaScript. I'm not sure about the error but if you need something more powerful than the Raspberry Pi you could look at: http://www.hardkernel.com/main/products/prdt_info.php?g_code=G143452239825 which has 2GB of ram.
-
From what I can tell they use Chromium (open source version of Chrome) as their browser so it should be supported. Its hard to tell what the issue is, is there any way you can click the "Show stack trace" button and get me the output?
-
Sorry for the picture, I'm don't have immediate access to the BrightSign display. Can you tell anything else from this?
-
I transposed the URL:
http://errors.angularjs.org/1.6.6/ng/areq?p0=fn@p1=not%20a%20function%2C%20got%20undefined
-
@phildunlap said in Bright Sign XD1033:
http://errors.angularjs.org/1.6.6/ng/areq?p0=fn@p1=not a function%2C got undefined
Sorry @phildunlap, do you have any suggestions with might be wrong? It does work perfectly on Chrome or Firefox.
-
@henryblu I still can't tell whats going on exactly. All I can tell is that something, somewhere inside Angular is trying to call a function which is undefined.
Can you get console output from the sign somehow? You can access Mango fine from a standard Chrome browser I assume?
I would hazard a guess that the sign is running an older version of Chromium that doesn't support a Javascript API we are using or something? You could try updating the signs firmware maybe.
-
Thanks Jared,
It does work fine on Chrome and Firefox. I think the signs firmware might be the issue. Yesterday they released a new firmware update https://brightsign.zendesk.com/hc/en-us/articles/218067927-Firmware-Release-Notes - which mentions there is a new JavaScript API. I'll try that and let you know how I go.
Cheers.