Need some help setting up RS232 -> Samsung Frame using Global Cache

First, I've read the documentation here:  allonis.com/support/documentation?view=category&id=153

I'm still a bit confused on how to get this set up and working. My setup is as such: I am using the Samsung Frame TV. In the EX-Link port, I have plugged in a 3.5mm stereo cable -> DB9 adapter. The DB9 end is plugged into a GlobalCache IP2SL device, which I have connected to my network via Ethernet.

In myServer, I have added a new Generic Serial device for this. I used the AddNetworkDevice command (wasn't sure whether I should use this or AddSerialDevice). I used the IP of my IP2SL, and for port I used 4999, per Global Cache's documentation here:  globalcache.zendesk.com/hc/en-us/article...h%C3%A9-Serial-Ports

I'm a bit lost on what to do next. The Generic Serial driver seems to imply that I need to create a SamsungFrame.serial file and copy that to myServer's data folder, then import this model in the Serial Database. What does this file need to look like?

Hoping someone can add a bit more context about how to set this up, and if the steps I've taken so far are correct.

I wanted to bump this topic back up. Can you please send an example of what the .serial file needs to look like?

I'd also love some information on how to set this up!
It looks like there's a paragraph missing from the web page describing it - or more likely it was written in a hurry there's just no way I can figure out how to set this up from the info on that page

I have a 2017 Samsung TV which I've always controlled through iRule - using RS232 from an IP2SL. It was always very quick/ responsive, which I've not found when attempting to use IP commands - so am keen to get this up and running with Allonis...

Any help much appreciated!

Afraid I'm still finding this impossible to setup without more comprehensive documentation - please help!

I have a Samsung screen connected by RS2332 using an IP2SL.

I've tried adding a network device through the Dashboard generic serial driver configuration, but think I'm on totally the wrong track...
I initially tried separating the port from the IP with a tilde - but this failed. Specifying the port after the IP with a colon seems to go further, but fails on the room...
GenericSerial|AddNetworkDevice~Samsung-MU-RS232~172.16.1.6:4999~Living Room fails saying the "input string "Living Room" was not in the correct format

allonis.com/support/documentation?view=category&id=153 doesn't show the format of any data to be placed in the .serial file

This should all be relatively simple - but the documentation for something basic like this is missing - and there is no way to download any examples.

Realise you guys are very busy with all the updates this week - but any help/ acknowledgement would be much appreciated!

Still no response on this - and the info provided at allonis.com/support/documentation?view=category&id=153 is incomplete.
Any help in how to do this or example setup files would be very much appreciated.

Well - I finally managed to get myServer controlling both my Oppo UDP-203 and Samsung (MU series) TV through GC IP2SL devices at the weekend...
The TV seems far more responsive through RS232, and the input source commands work every time - I'd had latency problems with this using the SamsungTizen driver.

This took a fair amount of experimentation/ trial & error - and wasn't always the most obvious process!
I firstly identified what the devices were wanting to receive, using the GC iTest app - making sure myServer wasn't also trying to connect to the same port...
Knowing exactly what works for the device, direct from the IP2SL removed any doubts as to what was/ wasn't working, meaning I could then move on to getting it working from myServer.

Now that I have created my own devices in the myServer Serial Database, I am able to export them as text files!  I'm attaching these to this message

@zshaiken if you still need some help with this, I'm happy to spend some time writing some more detailed instructions! I'm certain the Samsung Frame would use the same generic Samsung instructions.  I have an extensive spreadsheet of Samsung Hex commands if you need it.

In 6 basic steps:

• Install GenericSerial driver from the software updates section of myServer
• In the Drivers section of myServer, hit the GenericSerial "Configure driver" button, then click the "Driver Command Testing" button and use the "AddNetworkDevice" command.  Edit the command string with your own appropriate device name/ IP address etc before executing.  Default port is 4999 for the IP2SL.
• Edit the device you created, adding "9600,N,8,1" in the "Serial Params" box
• Move to the "Serial Database" section of myServer - import database files (format as per attached) by hitting "Serial Command Testing" then running the "Import Model command.  As per the documentation, these can be dropped into the data folder within the root folder of the server prior to import.  (I've only tried exporting, not importing!)
• If you don't have a database file, create a "New Serial Model".  Set to Hex or Ascii depending on the commands you need.  Click the arrow to the left of the serial model, and add the commands you need.  Hit the refresh symbol directly below after adding each command, and delete any duplicates that appear in the list - input seems buggy - clicking this, or re-ordering the table after adding 40 or so commands added hundreds of duplicates for me!
• Move back to the "Drivers" section of myServer, configure the GenericSerial driver, hit the "Driver Command Testing" button again, and test using the "SEND" command.

@allonis dave - I could see you were working on this in the background (updating the GenericSerial driver and myServer) - THANK YOU - I was originally unable to create the new network device - but you obviously fixed that bit
Perhaps you could add the "SEND" command to the Serial command testing list in the "Serial Database" section of myServer?  It would save swapping back to the driver section whilst editing?

Note: The Samsung MU series TV would only respond to HEX strings - and the entire string had to be in the command data, without splitting the common parts into a prefix. The Oppo was easier setup in Ascii (with \r as terminator).
Neither would respond to what Global Cache refer to as "Mixed" strings (prefixing bytes with delimiters such as \x) - so I removed these, replacing the delimiters with spaces

Note - the fact the GC IP2SL devices are persistently discovered by the myServer GenericIR driver is a total red herring - just ignore those.

Attached:  Oppo+Samsung Serial.zip
Contains:  OppoBDP203.serial and SamsungMU.serial - myserver database files for import


Ben