I did a factory reset and reloaded the module and now things seem to be better. Virtual device ( 41001 ) has come online and diagnostics are more clear.
Tomorrow I will test on site and keep you informed...
This looks like where it goes off the rails:
Line 81 2020-12-10 (18:41:52):: Creating HTTP socket
Line 82 2020-12-10 (18:41:52):: HTTP server started on port 443
Line 83 2020-12-10 (18:41:52):: Configuration error
Line 84 2020-12-10 (18:41:52):: port.https : invalid value=65537
Compare with ICraigie:
(0000022244) Creating HTTP socket
(0000022278) HTTP server started on port 80
(0000022280) Creating HTTPS socket
(0000022428) AmxSslServerSocket(int,int): got called
(0000022644) HTTPS server started on port 257
Well, I have some more news... Although the connection is established, the LG cannot be controlled by the module!
Really don't know what is going wrong again.
Below you can see the basic of the latest diagnostics.
I don't know what else should I do...
Line 7 2020-12-15 (13:44:49):: Creating HTTP socket
Line 8 2020-12-15 (13:44:49):: HTTP server started on port 80
Line 10 2020-12-15 (13:44:49):: Creating HTTPS socket
Line 11 2020-12-15 (13:44:49):: AmxSslServerSocket(int,int): got called
Line 12 2020-12-15 (13:44:49):: HTTPS server started on port 443
Line 132 2020-12-15 (13:45:20):: CIpInterpreter::Run - Execute Startup Code
Line 148 2020-12-15 (13:45:23):: Loading 1 Duet Modules.
@George Krietsepis said:
Please have a look below my diagnostics.. In my case, it also loads some file://LIB/jars while starting up..
What are these exactly ?
Those are all java libraries in the core class. My only guess is you are seeing those because of the firmware you are running v4.1.430. I would suggest installing the published firmware along with the system reset. Probably not a bad idea to do a clean disk -f as well
so I had a contact with AMX. They had a deep search on this and they realized that the module guys has used the serial protocol instead of the IP one !!!
Everything else is correct now. The master can load the module..
There is no way to work as it is. They have to change the protocol inside the module !!!
0
[Deleted User]Harman Integrated Technologies Group (ITG)Posts: 0
George, can you confirm the exact model of display you are working with?
I feel your pain... I seem to have run into a similar issue with a Sony projector (AMX seem to have used the serial protocol for ip communication). Multiple months have past, reminders are send, no answer. Very disappointing.
But at some point you have to continue... if writing your own module is not feasible, maybe you could use an EXB-COM2 tucked away behind the TV. You wouldn't have to change anything, only point the module to the COM2 device and use the serial protocol. It will cost money, sure, but so will writing your own module and at least it will work (I hope, don't have any experience with the AMX module OR the TV...).
yes, an EXB-COM2 could be a solution but as you very well said, it costs money.
Also, the most of the latest LG TV models, do not have a serial port. Instead, they may have a USB port which - some times - can be used as a serial port when connecting a serial to a USB adapter.
But this TV USB port is alive only while TV is on. If it is off, no command can be received over USB. In this case, we also need an IR to power on the TV!!!
If we - at the end of the day - manage to control the LG over the above method combination ( EXB-COM + Serial to USB adapter + IR ), we don't need the module at all since the LG serial protocol is very straight forward
0
[Deleted User]Harman Integrated Technologies Group (ITG)Posts: 0
George, the module you are attempting is not for the specific European model of the display in your project. Within your support ticket, I do not see a copy of the protocol document for your specific device. Do you have that document?
So it's been a while since there was any activity on this discussion. We purchased an LG 55UM7300PUA for digital signage because of the "IP Control" ability. In the past, I used LG consumer-grade TV's with some form of USB to control them. Just like people above, we've flipped the proper toggles and can turn on the TV via WoL, but connecting to port 9761 via telnet just closes telnet as soon as another key is pressed. Clearly the TV is allowing an initial connection because it isn't timing out on the telnet (as would happen if you tried telneting to a system that didn't support it). I'm not sure what else to try at this point. We may try to run a wireshark against the LG ThinQ app (once I get that working. It seems very odd that you cannot connect to an ethernet-connected LG from a wireless device, but that appears to be the case). This shouldn't be this difficult! This link implies it should work like any other telnet-enabled tv (ie through a terminal server):
[Deleted User]Harman Integrated Technologies Group (ITG)Posts: 0
We are building a new IP module for LG IP control to leverage their PIN code authorization. The module is in test and we are tweaking on the WOL reliability prior to releasing.
@HARMAN_Chris ,
any update for the new LG IP module ?
0
[Deleted User]Harman Integrated Technologies Group (ITG)Posts: 0
George - my apologies for the delayed release. I did not like the performance of Wake-on-Lan and we are finishing up our revisions. The current state needs to be modified to conform to RPM requirements pertaining to initialized and online. If you don't have an RPM project, we can send the current version to you for help in your project.
Comments
well, I have some good news...!!!
I did a factory reset and reloaded the module and now things seem to be better. Virtual device ( 41001 ) has come online and diagnostics are more clear.
Tomorrow I will test on site and keep you informed...
George
This looks like where it goes off the rails:
Line 81 2020-12-10 (18:41:52):: Creating HTTP socket
Line 82 2020-12-10 (18:41:52):: HTTP server started on port 443
Line 83 2020-12-10 (18:41:52):: Configuration error
Line 84 2020-12-10 (18:41:52):: port.https : invalid value=65537
Compare with ICraigie:
(0000022244) Creating HTTP socket
(0000022278) HTTP server started on port 80
(0000022280) Creating HTTPS socket
(0000022428) AmxSslServerSocket(int,int): got called
(0000022644) HTTPS server started on port 257
Well, I have some more news... Although the connection is established, the LG cannot be controlled by the module!
Really don't know what is going wrong again.
Below you can see the basic of the latest diagnostics.
I don't know what else should I do...
Line 7 2020-12-15 (13:44:49):: Creating HTTP socket
Line 8 2020-12-15 (13:44:49):: HTTP server started on port 80
Line 10 2020-12-15 (13:44:49):: Creating HTTPS socket
Line 11 2020-12-15 (13:44:49):: AmxSslServerSocket(int,int): got called
Line 12 2020-12-15 (13:44:49):: HTTPS server started on port 443
Line 132 2020-12-15 (13:45:20):: CIpInterpreter::Run - Execute Startup Code
Line 148 2020-12-15 (13:45:23):: Loading 1 Duet Modules.
Line 182 2020-12-15 (13:45:49):: CIpEvent::OnLine 41001:1:15
Line 183 2020-12-15 (13:45:49):: Memory Available = 12605336 <11392>
Line 184 2020-12-15 (13:45:50):: DDD.handleDynamicDevice(): new DPD - 192.168.6.160
Line 185 2020-12-15 (13:45:50):: ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
Line 186 2020-12-15 (13:45:50):: $09LG_75UM6970PUB_Comm_dr1_0_0 Device: 41001:1:0 is using ITGCommon v1.0.34 compiled: February 07, 2020 00:34 GMT
Line 187 2020-12-15 (13:45:50):: ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~
Line 233 2020-12-15 (13:45:52):: $09$09$09
Line 234 2020-12-15 (13:45:52):: -+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--
Line 235 2020-12-15 (13:45:52):: -+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--
Line 236 2020-12-15 (13:45:52):: $09$09$09
Line 237 2020-12-15 (13:45:52):: $09LG_75UM6970PUB_Comm_dr1_0_0 Version: 1.0.0 Compiled: March 24, 2020 09:02
Line 238 2020-12-15 (13:45:52):: $09$09$09
Line 239 2020-12-15 (13:45:52):: -+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--
Line 240 2020-12-15 (13:45:52):: -+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--
Line 241 2020-12-15 (13:45:52):: $09$09$09
Line 331 2020-12-15 (13:45:54):: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Line 332 2020-12-15 (13:45:54):: $09 initPropManager
Line 333 2020-12-15 (13:45:54):: $09 ---- Properties for 41001 ----
Line 334 2020-12-15 (13:45:54)::
Line 335 2020-12-15 (13:45:54):: Baud_Rate 9600
Line 336 2020-12-15 (13:45:54):: Device-Channels 255
Line 337 2020-12-15 (13:45:54):: Device-Interface com.amx.duet.impl.LG_75UM6970PUB.dr1_0_0.ILGTV
Line 338 2020-12-15 (13:45:54):: Device-Levels 15
Line 339 2020-12-15 (13:45:54):: Device_ID 01
Line 340 2020-12-15 (13:45:54):: Duet-Device 41001:1:0
Line 341 2020-12-15 (13:45:54):: Has-Aspect-Ratio true
Line 342 2020-12-15 (13:45:54):: Has-Aspect-Ratio-Cycle true
Line 343 2020-12-15 (13:45:54):: Has-Brightness false
Line 344 2020-12-15 (13:45:54):: Has-Color false
Line 345 2020-12-15 (13:45:54):: Has-Contrast false
Line 346 2020-12-15 (13:45:54):: Has-Freeze false
Line 347 2020-12-15 (13:45:54):: Has-Freeze-Cycle false
Line 348 2020-12-15 (13:45:54):: Has-Input-Select true
Line 349 2020-12-15 (13:45:54):: Has-Input-Select-Cycle true
Line 350 2020-12-15 (13:45:54):: Has-Lamp false
Line 351 2020-12-15 (13:45:54):: Has-Menu true
Line 352 2020-12-15 (13:45:54):: Has-Menu-10Key true
Line 353 2020-12-15 (13:45:54):: Has-Menu-Navigate true
Line 354 2020-12-15 (13:45:54):: Has-Notes false
Line 355 2020-12-15 (13:45:54):: Has-Picture-Mute true
Line 356 2020-12-15 (13:45:54):: Has-Picture-Mute-Cycle true
Line 357 2020-12-15 (13:45:54):: Has-PIP false
Line 358 2020-12-15 (13:45:54):: Has-PIP-Cycle false
Line 359 2020-12-15 (13:45:54):: Has-PIP-Position-Cycle false
Line 360 2020-12-15 (13:45:54):: Has-PIP-Tuner false
Line 361 2020-12-15 (13:45:54):: Has-Power true
Line 362 2020-12-15 (13:45:54):: Has-Power-Cycle true
Line 363 2020-12-15 (13:45:54):: Has-Sharpness false
Line 364 2020-12-15 (13:45:54):: Has-Station true
Line 365 2020-12-15 (13:45:54):: Has-Tint false
Line 366 2020-12-15 (13:45:54):: Has-Volume true
Line 367 2020-12-15 (13:45:54):: Has-Volume-Mute-Cycle true
Line 368 2020-12-15 (13:45:54):: Has-Volume-Ramp true
Line 369 2020-12-15 (13:45:54):: IGNORE-UNKNOWN-NETLINX-COMMAND true
Line 370 2020-12-15 (13:45:54):: IP_Address 192.168.6.162
Line 371 2020-12-15 (13:45:54):: Password 6HWDIRNZ
Line 372 2020-12-15 (13:45:54):: Poll_Time 10000
Line 373 2020-12-15 (13:45:54):: Port 9761
Line 374 2020-12-15 (13:45:54):: Queue_Interval_MS 200
Line 375 2020-12-15 (13:45:54):: Reconnect_Time 15000
Line 376 2020-12-15 (13:45:54):: Support-Discrete-Power false
Line 377 2020-12-15 (13:45:54):: Support-Multiple-Screens false
Line 378 2020-12-15 (13:45:54):: Support-PIP false
Line 379 2020-12-15 (13:45:54):: Supported-Bands TV
Line 380 2020-12-15 (13:45:54):: Timeout_Count 3
Line 381 2020-12-15 (13:45:54)::
Line 382 2020-12-15 (13:45:54):: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Line 1003 2020-12-15 (13:47:26):: LGTV reconnection successful
Those are all java libraries in the core class. My only guess is you are seeing those because of the firmware you are running v4.1.430. I would suggest installing the published firmware along with the system reset. Probably not a bad idea to do a clean disk -f as well
so I had a contact with AMX. They had a deep search on this and they realized that the module guys has used the serial protocol instead of the IP one !!!
Everything else is correct now. The master can load the module..
There is no way to work as it is. They have to change the protocol inside the module !!!
George, can you confirm the exact model of display you are working with?
Chris, the model is - as appears on TV display:
[LG] webOS TV UM7050PLC
Also ( if its useful ):
TV SW Version
4.9.0-53903 (goldilocks2-gyeryongsan)
Hello Chris,
did you have any look on this ?
It sounds tragic that eventually AMX is not able to control an LG TV over IP !!!
Thanks,
George
I feel your pain... I seem to have run into a similar issue with a Sony projector (AMX seem to have used the serial protocol for ip communication). Multiple months have past, reminders are send, no answer. Very disappointing.
But at some point you have to continue... if writing your own module is not feasible, maybe you could use an EXB-COM2 tucked away behind the TV. You wouldn't have to change anything, only point the module to the COM2 device and use the serial protocol. It will cost money, sure, but so will writing your own module and at least it will work (I hope, don't have any experience with the AMX module OR the TV...).
yes, an EXB-COM2 could be a solution but as you very well said, it costs money.
Also, the most of the latest LG TV models, do not have a serial port. Instead, they may have a USB port which - some times - can be used as a serial port when connecting a serial to a USB adapter.
But this TV USB port is alive only while TV is on. If it is off, no command can be received over USB. In this case, we also need an IR to power on the TV!!!
If we - at the end of the day - manage to control the LG over the above method combination ( EXB-COM + Serial to USB adapter + IR ), we don't need the module at all since the LG serial protocol is very straight forward
George, the module you are attempting is not for the specific European model of the display in your project. Within your support ticket, I do not see a copy of the protocol document for your specific device. Do you have that document?
LG TV's can be controlled from AMX via IP - we just released a tested and verified Wake On LAN update for another series of LG TV's.
Chris, I don't have the document on my hands but I have a photo taken from that TV IP Control menu.
How can I upload this photo here ?
Also, the module is not for my TV model but it is for a UM series one. My TV is also a UM model.
Do you think that any LG TV model has a different IP protocol ?
As mentioned on my previous post, AMX tech support told me that the module uses the RS232 protocol by mistake instead of the IP one.
I would expect an IP protocol for LG to be extremely stable, as the RS232 protocol hasn't changed in 10 years.
So it's been a while since there was any activity on this discussion. We purchased an LG 55UM7300PUA for digital signage because of the "IP Control" ability. In the past, I used LG consumer-grade TV's with some form of USB to control them. Just like people above, we've flipped the proper toggles and can turn on the TV via WoL, but connecting to port 9761 via telnet just closes telnet as soon as another key is pressed. Clearly the TV is allowing an initial connection because it isn't timing out on the telnet (as would happen if you tried telneting to a system that didn't support it). I'm not sure what else to try at this point. We may try to run a wireshark against the LG ThinQ app (once I get that working. It seems very odd that you cannot connect to an ethernet-connected LG from a wireless device, but that appears to be the case). This shouldn't be this difficult! This link implies it should work like any other telnet-enabled tv (ie through a terminal server):
https://www.manualsdir.com/manuals/825204/lg-oled65g6p.html?page=33
We are building a new IP module for LG IP control to leverage their PIN code authorization. The module is in test and we are tweaking on the WOL reliability prior to releasing.
@HARMAN_Chris ,
any update for the new LG IP module ?
George - my apologies for the delayed release. I did not like the performance of Wake-on-Lan and we are finishing up our revisions. The current state needs to be modified to conform to RPM requirements pertaining to initialized and online. If you don't have an RPM project, we can send the current version to you for help in your project.
Chris,
No I don't have an RPM project so I'd very appreciate if you could send me the current version.
Thanks,
George
Message sent with link
The updated IP control module supporting the keycode requirement has been posted to the InConcert database.
Hello Ian and Chris,
it is long time passed without posting any further information here. To be honest, I have never used the webOS module from the InConcert database yet.
Now I have been asked to implement something very simple for 9 LG TV's.
POWER ON -> CH40 (play lifeguard instructions) -> BACK (to any channel when instructions have finished).
The LG models will be from Pro:Centric series ( Hotel TV ) which are supposed running the webOS.
https://www.lg.com/us/business/hospitality-tvs/hotel-tvs/pro-centric-smart
Is there anybody here who has already used the module?
Thanks,
George
A revised WebOS module v1.0.1 was released early this year
https://developer.amx.com/#!/searchresult?Manufacturer=LG Electronics&Model=WebOS
As I remember the revision was a request or report from outside ITG so someone is using it w/o complaint or comment after the updated release.
I believe the module was tested internally during development on 2 different models but am unable to confirm which exact models.
good to hear there's no complaint or comment after the updated release.
No matter which models it was tested with, I believe any model running webOS is compatible with that module