0

iTach: ERR_1:1,008 (invalid pulse code)?

Eric Finlayson

March 04, 2011 20:00

None

Follow

I'm trying to control a pair of portable air conditioners (Sunpentown WA-1300E's, for reference).  After about three hours of trying to program three buttons via iLearn and not getting a consistent result from any of them, I contacted the manufacturer for a list of IR codes.  They responded with the following text:

on_off   df 20 7f 00

inc   5f a0 7f 00

dec   9f 60 7f 00

I then converted these into decimal, and pulled the consistent header from the learned text, to come up with these commands:

POWER sendir,1:1,4998,37993,1,1,223,32,127,0
INC sendir,1:1,4998,37993,1,1,95,160,127,0
DEC sendir,1:1,4998,37993,1,1,159,96,127,0

However, sending these to the iTach via telnet comes back with the ERR_1:1,008 "invalid pulse code" message.  Where am I going wrong?

• Facebook
• Twitter
• LinkedIn

4 comments

• 0
  
  Eric Finlayson March 04, 2011 20:06

  In case it's of any use, this is the text from some of the attempts in iLearn:

  [POWER]    sendir,1:1,1,37993,1,1,21,86,21,3799

  [POWER2]    sendir,1:1,1,37993,1,1,341,86,21,3654

  [SPT-POWER]    sendir,1:1,1,37764,1,1,12,2,3,17,1,384,3,3776

  [UP]    sendir,1:1,1,37764,1,1,325,86,21,3632,341,86,21,3776

  [DOWN]    sendir,1:1,1,37993,1,1,341,85,22,3654,341,85,22,3799

  [SPT-UP]    sendir,1:1,1,30413,1,1,13,18,21,17,21,17,21,17,21,51,21,51,21,52,21,51,21,51,21,52,21,51,21,51,21,17,21,51,21,17,21,17,21,17,21,17,21,17,21,17,21,52,21,17,21,52,21,51,21,51,21,52,21,51,21,1249,341,68,21,3041
  
  [SPT-DOWN]    sendir,1:1,1,37993,1,1,342,170,22,21,21,21,22,21,22,21,21,21,22,21,22,21,21,21,22,21,22,63,22,64,21,64,22,63,22,64,21,64,22,63,22,21,22,63,22,64,21,21,22,21,22,21,21,21,22,21,22,63,22,21,22,21,21,64,22,63,22,64,21,64,22,63,22,1559,342,85,21,3799

• 0
  
  Eric Finlayson March 04, 2011 20:15

  Okay... I've figured part of it out, anyhow --- the 0 is causing the 008 error.  Replacing it with a 960 let the job complete, but it still didn't shut the AC off. 

  Am I perhaps misinterpreting the hexcodes?  Should I treat each of them as an "on" pulse count, and follow them with some "off" pulse count?

• 0
  
  Josh Sherman March 07, 2011 20:03

  To know what to do here, you will need to request the format of the codes obtain from the manufacturer. These do not look like any standard hex code I have seen before. iTach units will not accept a pulse value of less than 1 period of the carrier frequency, so any value lower than 5 will throw an error in your code.

• 0
  
  Eric Finlayson March 09, 2011 20:44

  With a bit more patience (and a lot more caffeine!), I re-acquired the codes using iLearn.  Putting them into a CSV and viewing them in a spreadsheet helped me identify the parts that were common to all the keycodes and which were unique. 

  I wrapped this up in a simple perl script that I'll be calling to swap the A/Cs between primary and secondary roles.