Announcement

Collapse
No announcement yet.

Change tuner frequency being rejected (SX-1222)

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Change tuner frequency being rejected (SX-1222)

    Using 1.1.4561.15275 against an SC-1222 over Ethernet.

    Any attempt to change the tuner frequency just doesn't seem to work. Here's the debug log attempting to change to 100.60

    12/9/2012 1:43:00 PM - UltraPioneerAVR De - Processing Tuner Function command TunerDirectAccessSet.
    12/9/2012 1:43:00 PM - UltraPioneerAVR De - Sending command 'TAC1TP0TP0TP6TP0TP' to Pioneer AVR device '192.168.200.12:23', waiting for response ''.
    12/9/2012 1:43:00 PM - UltraPioneerAVR De - Sending command 'TAC1TP0TP0TP6TP0TP' to Pioneer AVR device '192.168.200.12:23', attempt #1.
    12/9/2012 1:43:00 PM - UltraPioneerAVR De - Entered SendToPAVR() function.
    12/9/2012 1:43:00 PM - UltraPioneerAVR De - Sending 'TAC1TP0TP0TP6TP0TP' to Pioneer AVR device '192.168.200.12:23' via Ethernet.
    12/9/2012 1:43:00 PM - UltraPioneerAVR De - Command TAC1TP0TP0TP6TP0TP does not produce a result.
    12/9/2012 1:43:00 PM - UltraPioneerAVR De - Data 'E02' sent by Pioneer AVR device '192.168.200.12:23'.
    12/9/2012 1:43:00 PM - UltraPioneerAVR De - Entered ProcessCommand() function.
    12/9/2012 1:43:00 PM - UltraPioneerAVR De - Expected command response ' []' received from Pioneer AVR device '192.168.200.12:23'.
    12/9/2012 1:43:00 PM - UltraPioneerAVR Wa - Pioneer AVR device [192.168.200.12:23] rejected the command due to 'unknown reason'.
    12/9/2012 1:43:01 PM - UltraPioneerAVR De - Data 'FL025A323A423120464D2038372E3530' sent by Pioneer AVR device '192.168.200.12:23'.
    12/9/2012 1:43:01 PM - UltraPioneerAVR De - Entered ProcessCommand() function.
    12/9/2012 1:43:01 PM - UltraPioneerAVR De - Expected command response ' []' received from Pioneer AVR device '192.168.200.12:23'.
    12/9/2012 1:43:01 PM - UltraPioneerAVR De - Pioneer AVR device '192.168.200.12:23' Panel Display=Z2:B1 FM 87.50
    12/9/2012 1:43:01 PM - UltraPioneerAVR De - Data 'E02' sent by Pioneer AVR device '192.168.200.12:23'.
    12/9/2012 1:43:01 PM - UltraPioneerAVR De - Entered ProcessCommand() function.
    12/9/2012 1:43:01 PM - UltraPioneerAVR De - Expected command response ' []' received from Pioneer AVR device '192.168.200.12:23'.
    12/9/2012 1:43:01 PM - UltraPioneerAVR Wa - Pioneer AVR device [192.168.200.12:23] rejected the command due to 'unknown reason'.
    12/9/2012 1:43:01 PM - UltraPioneerAVR De - Data 'E02' sent by Pioneer AVR device '192.168.200.12:23'.
    12/9/2012 1:43:01 PM - UltraPioneerAVR De - Entered ProcessCommand() function.
    12/9/2012 1:43:01 PM - UltraPioneerAVR De - Expected command response ' []' received from Pioneer AVR device '192.168.200.12:23'.
    12/9/2012 1:43:01 PM - UltraPioneerAVR Wa - Pioneer AVR device [192.168.200.12:23] rejected the command due to 'unknown reason'.
    12/9/2012 1:43:01 PM - UltraPioneerAVR De - Data 'FL025A323A423620464D2038372E3530' sent by Pioneer AVR device '192.168.200.12:23'.
    12/9/2012 1:43:01 PM - UltraPioneerAVR De - Entered ProcessCommand() function.
    12/9/2012 1:43:01 PM - UltraPioneerAVR De - Expected command response ' []' received from Pioneer AVR device '192.168.200.12:23'.
    12/9/2012 1:43:01 PM - UltraPioneerAVR De - Pioneer AVR device '192.168.200.12:23' Panel Display=Z2:B6 FM 87.50
    12/9/2012 1:43:01 PM - UltraPioneerAVR De - Data 'PRB06' sent by Pioneer AVR device '192.168.200.12:23'.
    12/9/2012 1:43:01 PM - UltraPioneerAVR De - Entered ProcessCommand() function.

    PHP Code:
    The documentation I have from Pioneer for the TAC command indicates there should be a <CRbetween each of the numbers, for example quoting from their PDF "Command: TAC<CR>8TP<CR>7TP<CR>5T P<CR>0TP<CR> (87.50MHz direct set" 
    Is this a known issue with the UltraPioneerAVR plugin, or am I missing something?

    Many thanks,
    John.
    Last edited by Rupp; December 9th, 2012, 04:58 PM.

  • #2
    Correction

    The message board got rid of the CR in my message. I meant that the documentaion indicates there should be CR's in between each digit when setting the frequency.

    Comment


    • #3
      Hello. The code does insert a CR between each digit. I am not sure why the Pioneer 1222 is rejecting the command. I have the VSX-1121-K and my Pioneer is not rejecting the commands.

      Can you watch the display and tell me what is being displayed when you tune to channel 100.60?

      Regards,
      Ultrajones
      Plug-ins: UltraMon, UltraM1G, UltraCID, Ultra1Wire, UltraLog, UltraWeatherBug, UltraPioneerAVR, UltraGCIR

      Comment


      • #4
        Interesting observation I just made, and should have mentioned it before - I was using Zone 2 for the tuner. It seems (not entirely reliable, I'm still trying to work it out entirely as the results don't appear consistent) that it only doesn't seem to work if only zone 2 is on tuner and the main zone is turned off. It ends up trying to set it to a tuner preset (as in Z2:C5 FM 87.50 displayed on the panel). I don't actually have any presets stored in the pioneer unit yet. In addition, I can't get the tuner preset option in the status panel of HS to go to the "blank" option at the top of the dropdown.

        If the main zone is turned on, it seems I can set the frequency correctly. Possibly a bug in the Pioneer firmware?

        Thanks,
        John.

        Comment


        • #5
          Quite possibly a bug... The *only* bug I have found with the Pioneer API is with the DIRECT ACCESS function. I tried reporting it before when I had my Pioneer VSX-1022-K and they never responded. A possible work-around would be to use the station presets.

          Regards,
          Ultrajones
          Last edited by Ultrajones; December 12th, 2012, 07:18 AM.
          Plug-ins: UltraMon, UltraM1G, UltraCID, Ultra1Wire, UltraLog, UltraWeatherBug, UltraPioneerAVR, UltraGCIR

          Comment

          Working...
          X