Recent Posts

Pages: [1] 2 3 ... 10
1
MagicInfo / Re: Hardware - Very Dim Screen - OH55F
« Last post by Pepijn on November 25, 2022, 09:59:48 AM »
Dear Ppierre61,

Get in contact with the people off Screencom.eu. You can request a firmware update or request assistance with a factory reset on the screen.

Kind regards, Pepijn
2
MagicInfo / Hardware - Very Dim Screen - OH55F
« Last post by Ppierre61 on November 24, 2022, 05:31:13 PM »
Howdy folks,

Total newbie here. I own a small ice cream shop in upstate New York and I have 2 Samsung OH55F screen that run Magic Info to display my menu. I use the screencon.eu service to upload my menu as it changes.

Recently, one of my screens went very dark. Not off, just very very dim. If I crouch and look at the screen at a very acute angle, I can see the content and change settings.

The other screen is working as it should. I haven’t changed any settings on the hardware. On the dim screen, eco mode is off. I’ve restarted the unit. 

We spent so much money on this units, I’m really nervous the screen is broken, but perhaps there is a setting or configuration that will bring it back to life.

I’ve moved the brightness and contrast to 100 but that’s doesn’t appear to be issue.

I have not reset to factory settings for fear of losing my configuration to screencom.eu

Any assistance or tips would be very much appreciated.
3
MagicInfo-I Premium / Re: API Authentication
« Last post by jknowles on November 24, 2022, 10:45:46 AM »
I know this is a rather old topic, but still seems to get views on it.
To access the api, first you need to send the api request to  ..../MagicInfo/restapi/v2.0/auth   with content-type:application/json in the header, and  {"username":"password"} in the body of the the request, using the POST method.
You'll then receive a json response with token, refreshToken, dateFormat ,timeFormat, and scheduleFirstDay.   Parse the response stream and use the value from token in all your subsequent api calls by adding it into the header for your next request under the key named "api_key" with the value being from the previous response "token".  It's kind of confusing that you are renaming what the variable is called between the auth response and subsequent requests .
I just ran the example through fiddler:

REQUEST

POST https://myserver/MagicInfo/restapi/v2.0/auth HTTP/1.1
User-Agent:Fiddler Everywhere
Content-Type:application/json
Host:ss.10net.net:7002
Content-Length:52

{"username":"jknowles","password":"signageisfun"}

Response:

HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Access-Control-Allow-Origin: *
X-FRAME-OPTIONS: SAMEORIGIN
X-Content-Type-Options: nosniff
Content-Security-Policy: default-src 'self' 'unsafe-inline' 'unsafe-eval'  blob:; img-src 'self' data:;worker-src blob:;
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
Access-Control-Allow-Methods: POST, GET, PUT, OPTIONS, DELETE
Access-Control-Max-Age: 3600
Access-Control-Allow-Headers: Origin, X-Requested-With, Content-Type, Accept, api_key
X-Frame-Options: SAMEORIGIN
Content-Type: application/json;charset=UTF-8
Transfer-Encoding: chunked
Date: Thu, 24 Nov 2022 09:55:52 GMT

70e
{"token":"xxxxxxxxxxxxxxxxxxxxxxxxxxxxx","refreshToken":"yyyyyyyyyyyyyyyyy","dateFormat":"yyyy-MM-dd","timeFormat":"24hour","scheduleFirstDay":"0"}
0

I then use the token in my request for list of devices

Request:
GET https://myserver/MagicInfo/restapi/v2.0/rms/devices?pageSize=15&startIndex=1 HTTP/1.1
Content-Type: application/json
api_key: xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Host: myserver

Response:

HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Access-Control-Allow-Origin: *
X-FRAME-OPTIONS: SAMEORIGIN
X-Content-Type-Options: nosniff
Content-Security-Policy: default-src 'self' 'unsafe-inline' 'unsafe-eval'  blob:; img-src 'self' data:;worker-src blob:;
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
Access-Control-Allow-Methods: POST, GET, PUT, OPTIONS, DELETE
Access-Control-Max-Age: 3600
Access-Control-Allow-Headers: Origin, X-Requested-With, Content-Type, Accept, api_key
X-Frame-Options: SAMEORIGIN
Content-Type: application/json;charset=UTF-8
Transfer-Encoding: chunked
Date: Thu, 24 Nov 2022 10:35:43 GMT

2000
{"apiVersion":"2.0","status":"Success","items":[{"deviceName":"WP-320-Middle","deviceId":"f0-70-4f-0f-2e-2c","deviceType":"SPLAYER","deviceTypeVersion":7.0,"power":true,"groupNam

  etc. etc


Hope this helps!!1
4
MagicInfo / Re: Display website in local network
« Last post by jknowles on November 23, 2022, 05:45:48 PM »
Tizen's current version of chromium is 56.xx which is very old compared to current chromium release  If you want to debug your website with tizen's chromium version, you can download it at:
https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html

The specific error I've received trying to run a shopify website on a samsung display was related to javascript and window.webPixelsManager.init()

PS You can find the exact version of your TV chromium browser in the settings.  With the version number, you can enter it at https://omahaproxy.appspot.com/ then download the equivalent windows/mac/linux version from the above link.

Hope this helps!

5
MagicInfo / Re: MagicInfo
« Last post by SaDiKoFF on November 15, 2022, 04:33:28 PM »
Wukat, Samsung TVs does not work with Magic Info.

Magic Info works with professional signage Monitors with player Only and there is nothing you can do.

It is very common mistake that customer purchase any TV in local stores and then want to make use them as signage.

Tizen is a Linux based proprietary OS.

Regards,
6
MagicInfo / Re: MagicInfo
« Last post by Pepijn on November 09, 2022, 11:12:23 AM »
Dear Wukat,

For my understanding, only Samsung Signage players are compatible with MagicINFO.
Tizen OS runs on many Samsung products.

Please have look at all the Samsung signage products.
https://displaysolutions.samsung.com/main/index

Kind regards, Pepijn.
7
MagicInfo / Re: MagicInfo
« Last post by wukat on November 08, 2022, 04:35:37 PM »
I forgot to mention that the TV is also Tizen compatible. 

On the Samsung website Tizen compatible devices are regarded as supported signage players

Is this an option to us?
8
MagicInfo / MagicInfo
« Last post by wukat on November 08, 2022, 03:28:02 PM »
A company currently hosts MagicInfo V8 for us and we have some Samsung screens which are recommended for MagicInfo.

We recently purchased a Samsung TV which is connected to the network/internet and has the Tezma store, so, can we install the MagicInfo app to the TV and then link that to the MagicInfo server which is being hosted for us?    As our hosting company says no.

If not,  can we :-

Stream via the TV web browser
Stream via a Firestick with an android app

Or what is the best way to stream onto a different device?


If we can't make the solution work with different devices then I think we must rip it out and change solution. The Samsung solution seems great, but not every device we add can be Samsung MagicInfo kit. 

We get zero help and support from out MagicInfo hosting company, to be honest they seem a bit shady.  I am hoping to find out if we can work out a solution and then find a new host ASAP.

Thanks
9
MagicInfo / Re: MagicInfo Pro
« Last post by SaDiKoFF on November 03, 2022, 12:39:53 PM »
MagiInfo Pro is like 8 years old, so it is very hard that some body still installers. This software was design to work on Windows XP/7 only.
I don't recommend to install new windows version(7 or 10) due to drivers compatibility and CPU performance. I have done it and install more RAM, but PC will slow down.
What you can do is install MagicInfo I player version 3.0 and it will run on that SBB and connect it to magicinfo server V8. This will give you 1 year more of time so you can update your whole system.
My personal recommendation update systems at least every 5 years. Most of manufacturers ditch support after 3-4 years, since they want to sale not to support.
10
MagicInfo-I / Re: Downgrade firmware on DB48E display
« Last post by Pepijn on October 28, 2022, 03:29:08 PM »
Dave,

Indeed it is not recommended to roll back on firmware.

To use a USB drive it needs to be formatted at FAT32
You need to place the two files (I believe the .bem and the info text file) in the root of your drive.

Kind regards,
Pepijn.
Pages: [1] 2 3 ... 10