Thank you Jeff.
Details you sent were great help.
I found a difference between your output and mine which I think may be causing the issue.
The RS-232: Control supported, non-DMTech displays command sent to my DMP before any commands to turn the TV on/off were sent: init.startService_dmttv=no&init.startService_rs232=yes&rs232.device=/dev/ttyS1&mib.save=1&mng.reboot=1
My output showed:
init.startService_rs232 T_STRING yes
.
.
rs232.device T_STRING /dev/ttyS0
rs232.speed T_STRING 9600
rs232.parity T_STRING none
rs232.data_size T_STRING 8
rs232.stop_bits T_STRING 1
rs232.flow_ctrl T_STRING none
rs232.tx_hex T_STRING 8C000002008E
rs232.tx_str T_STRING
rs232.rx_buf T_STRING
rs232.rx_overflow_flag T_STRING false
rs232.tx_cnt T_STRING 6
rs232.rx_cnt T_STRING 0
Your output showed:
init.startService_rs232 T_STRING yes
.
.
rs232.device T_STRING /dev/ttyS1
rs232.speed T_STRING 9600
rs232.parity T_STRING none
rs232.data_size T_STRING 8
rs232.stop_bits T_STRING 1
rs232.flow_ctrl T_STRING none
rs232.tx_hex T_STRING 8c000002018f
rs232.tx_str T_STRING
rs232.rx_buf T_STRING e9
rs232.rx_overflow_flag T_STRING false
rs232.tx_cnt T_STRING 60
rs232.rx_cnt T_STRING 15
The line: rs232.device T_STRING /dev/ttyS0 is different from yours: rs232.device T_STRING /dev/ttyS1
I don understand why the "RS-232: Control supported, non-DMTech displays" clearly states: &rs232.device=/dev/ttyS1 but the output post sending the command shows: &rs232.device=/dev/ttyS0
My understanding is that /dev/ttyS0 is a different comm port than /dev/ttyS1 and that could be causing the issue.
Do you know how to check the permissions on the DMP for /dev/ttyS0 and /dev/ttyS1? Im thinking if the permissions are not set correctly then the commands will not flow to the correct port....in this instance /dev/ttyS1.
Thanks
Linda