Jump to content
AIDA64 Discussion Forum
Fiery

New LCD device support: Samsung SPF Digital Photo Frames

Recommended Posts

I have a Samsung SPF87H frame that also only works for approximately 5 seconds. 

 

I'm running a clean install of Windows 8.1, with a registered copy of Aida 64 and the Samsung SPF drivers downloaded from this site.

 

Can you help get me running for more than 5 seconds? :-)

Share this post


Link to post
Share on other sites

AIDA64 uses an unofficial, non-documented interface to communicate with Samsung SPF devices. If it doesn't work on your device, then I'm afraid we cannot help you out :( Only one thing you can try: in case you have a complicated LCD layout, you can try lowering the JPEG quality, but about the 5-seconds issue I don't think that would help :(

Share this post


Link to post
Share on other sites

Hi thanks for your reply.  I have tried changing the quality to 50 %, I still only get a display for 5 seconds. 

 

Your reply does contradict the first post in this topic stating support for Samsung SPF frames in particular the model I managed to track down. Maybe this should be edited as I'm the second person to indicate problems with the SPF87H.

 

 

 

It now looks like I have to find an alternate display, can anyone recommend a USB display device that works ?  At the moment this is a disappointing outcome.

Share this post


Link to post
Share on other sites

Your reply does contradict the first post in this topic stating support for Samsung SPF frames in particular the model I managed to track down. Maybe this should be edited as I'm the second person to indicate problems with the SPF87H.

We've edited the first post, thank you.

It now looks like I have to find an alternate display, can anyone recommend a USB display device that works ?  At the moment this is a disappointing outcome.

How about using your cell phone or tablet display as a wireless LCD for AIDA64?

http://forums.aida64.com/topic/2636-remotesensor-lcd-for-smartphones-and-tablets/

Share this post


Link to post
Share on other sites

Thanks for replying Fiery.

 

I did briefly try using an old Ipod touch but couldn't connect to the IP address.

 

Ideally I would like a display big enough to show a number of sensors at the same time, that's why the photo frame option seems an ideal solution.

 

I would love to purchase a Samsung 800P but they seem impossible to track down in the UK.

 

 I'll keep looking. 

 

Final question, I was considering a Yocto Display, as an alternative.  Have you tested these displays and is it possible to have multiple pages as I'm not sure how much data could be displayed on the small screens?

Share this post


Link to post
Share on other sites

We've tested the AIDA64 LCD module with Yocto-MiniDisplay and Yocto-MaxiDisplay, and they both worked flawlessly. But those are quite little screens, compared to a photo frame. And they do not feature buttons to change pages.

Share this post


Link to post
Share on other sites

I try to use SPF-107H (LP10|PLERT/EN,  PID=$2036, VID=$04E8, firmware 1008) in Win7x64. It works only 2-3 seconds.

Do you use the Samsung Mini-Monitor driver, or our LibUsb driver?

Share this post


Link to post
Share on other sites

Without installed "Frame manager" frame don't work at all. AIDA don't recognize it.

I can't install LibUsb driver - without "Frame manager" frame may be manually turned in "mini-monitor" mode for 2-3 seconds, after that it unconnect from USB.

For work I close "Frame manager" and start AIDA. It successfully turn frame from "storage" to "mini-monitor" and show picture, but only 2-3 sec. After that USB connection close. 

Share this post


Link to post
Share on other sites

Without installed "Frame manager" frame don't work at all. AIDA don't recognize it.

I can't install LibUsb driver - without "Frame manager" frame may be manually turned in "mini-monitor" mode for 2-3 seconds, after that it unconnect from USB.

For work I close "Frame manager" and start AIDA. It successfully turn frame from "storage" to "mini-monitor" and show picture, but only 2-3 sec. After that USB connection close.

Sad to hear that it doesn't work with either driver :( I've moved your device to the "not working" category in the opening post. I'm confused though, since it seems to work in some cases, while on a similar (or almost similar) device it fails to work. Maybe the issue is related to a certain hardware revision or firmware revision? Hard to tell, we have very limited knowledge about SPF variants :(

Share this post


Link to post
Share on other sites

Maybe it will be helpful:

Controller of frame is MP630DTCG-B - http://www.modiotek.com.tw/index.php?option=com_content&view=article&id=62&Itemid=82〈=en
I try to use it in Windows similar to this projects:
http://web.media.mit.edu/~gracewoo/stuff/picframe/
http://www.puschmann.net/page/?page_id=62
But unsuccessfully.

 

Maybe this models (SPF-87H & SPF-107H) has "exit timer" and it close connection if frame frequency is very low.

I try to decrease LCD update time to 50ms (20Hz), but min in 5.20 version is 500ms. Can you expand this range to check it? 

 

Share this post


Link to post
Share on other sites

Maybe it will be helpful:

Controller of frame is MP630DTCG-B - http://www.modiotek.com.tw/index.php?option=com_content&view=article&id=62&Itemid=82&lang=en

I try to use it in Windows similar to this projects:

http://web.media.mit.edu/~gracewoo/stuff/picframe/

http://www.puschmann.net/page/?page_id=62

But unsuccessfully.

 

Maybe this models (SPF-87H & SPF-107H) has "exit timer" and it close connection if frame frequency is very low.

I try to decrease LCD update time to 50ms (20Hz), but min in 5.20 version is 500ms. Can you expand this range to check it?

We've extended the update frequency down to 100 msec in the latest beta update to AIDA64 Extreme:

http://www.aida64.com/downloads/latesta64xebeta

But, I don't think it would help. Please let me know how it works.

Share this post


Link to post
Share on other sites

I try both: LibUsb driver from post #38 and Original Samsung.

The same result.

Does the every 500ms there are "Device Vendor_Device" command - two zero bytes anomaly happen with both drivers?

Share this post


Link to post
Share on other sites

My mistake - correct name of command is "Function Vendor_Device".

This command sending by "Frame manager" to 0 point. I try to do it from custom application and get good result - USB connection is stable. Also I try to increase frame update time to 500ms. Now "Function Vendor_Device" (two zero bytes to 0 point) and frames (packets to point â„–2) sending from one timer - 500ms. USB connection is stable and pictures shows correct. 

Share this post


Link to post
Share on other sites

My mistake - correct name of command is "Function Vendor_Device".

This command sending by "Frame manager" to 0 point. I try to do it from custom application and get good result - USB connection is stable. Also I try to increase frame update time to 500ms. Now "Function Vendor_Device" (two zero bytes to 0 point) and frames (packets to point â„–2) sending from one timer - 500ms. USB connection is stable and pictures shows correct.

I don't think I can follow that :( If by Frame manager you mean Samsung Frame Manager software, then you have to uninstall all SPF-related Samsung software and driver before installing our LibUsb driver. Otherwise Samsung's software and driver may collide with our driver.

But, in case you've figured it out and now things are stable, then it's great :)

Share this post


Link to post
Share on other sites

We've extended the update frequency down to 100 msec in the latest beta update to AIDA64 Extreme:

http://www.aida64.com/downloads/latesta64xebeta

But, I don't think it would help. Please let me know how it works.

 

Concerning the switch back from monitor mode after a couple of seconds for some Samsung SPF I have found on "http://pyframe.blogspot.de/2011_12_01_archive.html" this information (it's from a python script). 

  # This control function is required to keep the frame permanently in Mini Monitor mode. 

  # When the frame is switched to Mini Monitor mode, it remains there for a few seconds, but 

  # then switches back, unregistering from the USB bus.

  # This function is needed only once after connection of the frame, but it does not seem

  # to do any harm when transfered with every picture transfer

  dev.ctrl_transfer(0xc0, 4 )    

 

Perhaps you can add this byte sequence to the contol code sent to the frame, to solve the problem of the not permanent "mini monitor" mode. 

Share this post


Link to post
Share on other sites

Concerning the switch back from monitor mode after a couple of seconds for some Samsung SPF I have found on "http://pyframe.blogspot.de/2011_12_01_archive.html" this information (it's from a python script). 

  # This control function is required to keep the frame permanently in Mini Monitor mode. [/size]

  # When the frame is switched to Mini Monitor mode, it remains there for a few seconds, but [/size]

  # then switches back, unregistering from the USB bus.[/size]

  # This function is needed only once after connection of the frame, but it does not seem[/size]

  # to do any harm when transfered with every picture transfer[/size]

  dev.ctrl_transfer(0xc0, 4 )    [/size]

 

Perhaps you can add this byte sequence to the contol code sent to the frame, to solve the problem of the not permanent "mini monitor" mode.

That seems like a very useful information, thanks a lot! We've already implemented it in the latest AIDA64 Extreme beta update available at:

http://www.aida64.com/downloads/latesta64xebeta

Let us know if it helps to fix the disconnection issue.

Share this post


Link to post
Share on other sites

That seems like a very useful information, thanks a lot! We've already implemented it in the latest AIDA64 Extreme beta update available at:

http://www.aida64.com/downloads/latesta64xebeta

Let us know if it helps to fix the disconnection issue.

 

If works for me (SPF 107H USB-ID 04e8:2035 / 2036).

Great (and unbelievable short time to make it happen)!

Share this post


Link to post
Share on other sites

If works for me (SPF 107H USB-ID 04e8:2035 / 2036).

Great (and unbelievable short time to make it happen)!

Your post came at just the right time to squeeze a new single line into the code before we rolled out the new beta update :) Thanks again ;)

Share this post


Link to post
Share on other sites

Hi, since last two updates, my Samsung frame stops responding after few minutes.

It was working fine for months before.

Share this post


Link to post
Share on other sites

105P is working and it is a huge display.

I had the issue where Frame Manager was disabling Aero.

Uninstalled it and now everything is fine.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • By Roy
      Hi,
      it would be nice if there was the possibility to send sensor values unformatted as a number or percentage, via a serial port.
      Similar to the LCD displays, only without formatting, or pure numbers with separators.
      Together with a small GUI.
      Background is the simple evaluation of the data with a microcontroller and display in different ways.
      I imagine not only LCD or OLED, but rather seven segment display, nixi tubes or an analog pointer display. That would create a lot of possibilities.
    • By Wampo
      Hey Aida Team,
      i have some issues with this Adafruit LCD wich is recomended. On the two Pictures you can see what aida should do and what can i see on the Display. The First line is completely erased and the screen is flickering. The Adafruit Backpack is set to 20x4 LCD. When the Display is updating you can see the right setting for a millisecond.
      But if i change the LCD Setting in AIDA to 16x2, and leave the Backpack in 20x4 mode,  the Screen isn flickering and the first line is there. I think you got a little problem with the 20x4 Driver. I have Searched for the code but i cant find it, to edit it if i found the failure. 
       
      Please give me response for this BUG. I have extra ordert this overpriced 50€ LCD for it. 
      Greetings Daniel from Germany


      VID_20181129_160917.mp4
    • By Fiery
      We've added support for RoboPeak RPUSBDisp color graphical USB-connected LCD display.

      You can enable the LCD device from AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD / RoboPeak. Currently there is no Windows driver made specifically for RoboPeak displays.  But there's a workaround: you can use the AlphaCool LCD driver (Version 2.1).  The driver installation has to be forced due to the USB device ID mismatch (between AlphaCool and RoboPeak displays).
      The driver installation works as:
      Open Device Manager --> Other devices --> double-click on rp-usbdisp --> Update Driver button --> Browse my computer for driver software --> Let me pick from a list of available drivers on my computer --> Show All Devices --> Next button --> Have Disk button --> Browse button --> select acusbdisplay.inf file from the AlphaCool LCD driver folder --> Next button --> press Yes button on the Update Driver Warning message box.

      You can order a RoboPeak display from DFRobot at:
      https://www.dfrobot.com/product-1062.html#.UqfXHfSnoqX
      You can find the new AIDA64 beta update at:
      https://www.aida64.com/downloads/latesta64xebeta
      Please let us know if you find any difficulties enabling or using this new feature. Also let us know if you've got another kind of LCD device that is currently unsupported by AIDA64.
      Regards,
      Fiery
    • By Fiery
      We've added support for several Matrix Orbital USB character based and monochrome graphical LCD displays, including LK, MX, PK, VK, GLK, GLT, GX Typhoon, and their drive-bay and external variants as well.
      You can enable the LCD device from AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD. The only thing needed to enable this feature is having the appropriate Matrix Orbital USB LCD drivers installed, and the LCD to be connected to a USB port. You can verify if your device is supported by AIDA64 by finding the device on the Devices / USB Devices page in AIDA64, and checking its Device ID. It should be one of the following IDs:
      0403-FA01
      0403-FA02
      0403-FA03
      0403-FA04
      0403-FA05
      1B3D-011F
      1B3D-0120
      1B3D-0121
      1B3D-0123
      1B3D-0125
      1B3D-0127
      1B3D-012C
      1B3D-0134
      1B3D-013E
      1B3D-013F
      1B3D-0140
      1B3D-0141
      1B3D-0155
      1B3D-0156
      1B3D-0157
      1B3D-0158
      1B3D-015E
      1B3D-0161
      1B3D-016A
      1B3D-016B
      1B3D-016C
      1B3D-0176
      1B3D-017B
      1B3D-01F0
      1B3D-01F1

      Due to their interface bottleneck BGK, EGLK, GLK and GLT displays perform display updates quite slowly, so visual discrepancies may be experienced when using the GLK (graphics) protocol on these displays. It is possible to use the LK (character based) protocol on GLK displays as well, which will work much faster. In order to switch between the GLK and LK protocols, you need to first disable the GLK protocol (in AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD), and then enable the LK protocol on the same page. Ignore the error, and restart AIDA64 to apply the switch.
      You can find the new AIDA64 beta update at:
      http://www.aida64.com/downloads/latesta64xebeta
      Please let us know if you find any difficulties enabling or using this new feature. Also let us know if you've got another kind of LCD device that is currently unsupported by AIDA64. BTW, Abacom, AlphaCool, Digital Devices, LCD2USB, Mad Catz Venom, and SDC Megtron LCDs are also supported now by the latest AIDA64 beta.
      Regards,
      Fiery
    • By Fiery
      We've added support for the built-in 160x32 pixel monochrome LCD screen of EVGA Z10 gaming keyboard.  You can enable the LCD device from AIDA64 / main menu / File / Preferences / Hardware Monitoring / LCD / EVGA.
      [/
      Currently AIDA64 communicates with the LCD directly, using USB HID interface.  It collides with EVGA's own software (EVGA Unleash), so it's recommended to close that software before enabling EVGA Z10 support in AIDA64.  EVGA will soon develop a proper SDK/API for their keyboard, much like the LCD API of Logitech gaming keyboards, so that multiple software can put information on the LCD the same time, without collisions.
      You can find the new AIDA64 beta update at:
      https://www.aida64.com/downloads/latesta64xebeta
      Please let us know if you find any difficulties enabling or using this new feature. Also let us know if you've got another kind of LCD device that is currently unsupported by AIDA64.
      Regards,
      Fiery
×