Samsung ME series and WOL
ajish.raju
chief evangelist of favante
I am controlling a Samsung ME55C via TCP and since Samsung unit shuts down the LAN port when its powered off, there is no option to turn it on. I know wake up on lan works for other series of Samsung but i am not able to do the same with this series. I have tried the following ports 40000, 7001(magicinfolite server port) and 6000( after scanning the ports).
Has anyone got this unit to turn on ?
Has anyone got this unit to turn on ?
Comments
-
Have you turned off all the "Green" features on the TV? They are generally spread across multiple menus. I have not controlled the ME55C with WOL. I have controlled the DE40C with WOL, but it required updating firmware on the TV.
-
Turned off all the green options, auto power off, pc module options are set to always on. But all to no avail.
-
When you list the ports that you have tried, are those the ports you are sending the WOL packet to? On the DE40C's I use port 9 for WOL and port 1515 for control.
-
I have now tried port 9 also but to no avail. Here is the WOL command i am sending \xFF\xFF\xFF\xFF\xFF\xFF\xFE\xF0!\x05\x0C\xBD\xFE\xF0!\x05\x0C\xBD\xFE\xF0!\x05\x0C\xBD\xFE\xF0!\x05\x0C\xBD\xFE\xF0!\x05\x0C\xBD\xFE\xF0!\x05\x0C\xBD\xFE\xF0!\x05\x0C\xBD\xFE\xF0!\x05\x0C\xBD\xFE\xF0!\x05\x0C\xBD\xFE\xF0!\x05\x0C\xBD\xFE\xF0!\x05\x0C\xBD\xFE\xF0!\x05\x0C\xBD\xFE\xF0!\x05\x0C\xBD\xFE\xF0!\x05\x0C\xBD\xFE\xF0!\x05\x0C\xBD\xFE\xF0!\x05\x0C\xBD
-
Your WOL packet looks correct. This is the Function I use to generate my WOL "Magic" packet.
DEFINE_FUNCTION INTEGER Generate_Magic_Packet(CHAR sMAC[], CHAR sMagicPacket[]) { STACK_VAR INTEGER Count IF (LENGTH_STRING(sMAC) == 6 AND MAX_LENGTH_STRING(sMagicPacket) >= 102) { sMagicPacket = "$FF,$FF,$FF,$FF,$FF,$FF" FOR (Count = 1; Count <= 16; Count++) { sMagicPacket = "sMagicPacket, sMAC" } RETURN TRUE } RETURN FALSE }Also make sure you are using IP_UDP in your IP_CLIENT_OPEN for WOL, and IP_TCP for your IP_CLIENT_OPEN for the control connection. -
What server address are you populating in your ip_client_open code when opening up UDP dialog?
Perhaps post this code snippet for us to look at... -
Thanks for all the responses. I am connecting to the subnet mask 255.255.255.255.
-
No probs, so is it working now?ajish.raju wrote: »Thanks for all the responses. I am connecting to the subnet mask 255.255.255.255. -
Not yet. I am trying to contact Samsung Tech support to resolve it.
-
We have quite a few ME40c, 55c and 75c's controlled under IP. Try using port 1515 - didn't see that in the list above.
-
I am using that port for the control functions and it works perfectly. Whenever i switch the unit off via remote or third party control, i am not able to ping the unit nor control it. If i turn on the unit, the lan port is alive for control again.
-
Running out if ideas for you...but,
Apart from screen firmware, you may also want to ensure the client network policies/routers allow WoL.
WoL can sometimes be a funny old fish.
That's pretty normal - it's part of a very low network layer.Whenever i switch the unit off via remote or third party control, i am not able to ping the unit nor control it.
Anyhow, hope it helps. -
Samsung Tech guy said he will send some info soon. Crossing my fingers here.
-
I would not use 255.255.255.255 as the broadcast IP, as it is not technically valid. I would try using the broadcast IP for your subnet instead. For example if your IP address is 192.168.1.5 and your subnet mask is 255.255.255.0, the broadcast IP for your subnet would be 192.168.1.255.
-
No luck after changing the broadcast IP
-
If you post your code we can take a look at it.
-
If your subnet mask is 255.255.255.192 ,tv ip address is 10.215.157.11 and gateway is 10.215.157.1, what will be the broadcast ip. I tried a software called fusion wol , google it and i was able to wol the unit. I am trying to figure what port and broadcast ip this software might be using
If all else fails, i will post the code. -
Try 10.215.157.63 as the broadcast ip
-
You may have to go the old route of IR to power it on and IP for the rest. There are still some Sony receivers out there that do not respond to power on via IP or even rs232. Once they are powered up they work fine. I've had a few automobiles like that before.
-
Here is what I'm using, tested as working, as you can see port is 7676;
cSamsung_MAC1 = "$F4,$7B,$5E,$61,$0F,$18"
IP_CLIENT_OPEN (dvSamsung1_UDP.PORT,'255.255.255.255',7676,2)
Wait 5
{
SEND_STRING dvSamsung1_UDP,"$FF,$FF,$FF,$FF,$FF,$FF,cSamsung_MAC1,
cSamsung_MAC1,
cSamsung_MAC1,
cSamsung_MAC1,
cSamsung_MAC1,
cSamsung_MAC1,
cSamsung_MAC1,
cSamsung_MAC1,
cSamsung_MAC1,
cSamsung_MAC1,
cSamsung_MAC1,
cSamsung_MAC1,
cSamsung_MAC1,
cSamsung_MAC1,
cSamsung_MAC1,
cSamsung_MAC1"
nDisplay_Standby[5] = 1
WAIT 200
{
IP_CLIENT_CLOSE(dvSamsung1_UDP.PORT)
Wait 200
{
IP_CLIENT_OPEN(dvDisplay5.PORT,'10.242.142.123',1515,1)
nDisplay_Connect[5] = 1
}
}
} -
Please find the working code, used port 2304,7406,9,7 and broadcast ip of 255.255.255.255.
Categories
- All Categories
- 2.5K AMX General Discussion
- 922 AMX Technical Discussion
- 514 AMX Hardware
- 502 AMX Control Products
- 3 AMX Video Distribution Products
- 9 AMX Networked AV (SVSI) Products
- AMX Workspace & Collaboration Products
- 3.4K AMX Software
- 151 AMX Resource Management Suite Software
- 386 AMX Design Tools
- 2.4K NetLinx Studio
- 135 Duet/Cafe Duet
- 248 NetLinx Modules & Duet Modules
- 57 AMX RPM Forum
- 228 MODPEDIA - The Public Repository of Modules for Everyone
- 943 AMX Specialty Forums
- 2.6K AMXForums Archive
- 2.6K AMXForums Archive Threads
- 1.5K AMX Hardware
- 432 AMX Applications and Solutions
- 249 Residential Forum
- 182 Tips and Tricks
- 146 AMX Website/Forums