Help with converting TASCAM codes

Hello all.

I have been at this for about 4 hours now but having trouble getting things to work. I have a TASCAM CC-222MKII. The remote for this unit was gone when I got it and a replacement is around $60 starting. I would like to get the codes for it and get a cheap learning remote or just build one with the buttons I want.

TASCAM has the remote codes directly on their site in an Excel file all in NEC protocol. It has “DATA Code” (button function) and “Custom Code” (address code I’m guessing) all in HEX. I have done some hunting around on how to get that added to an IR file type for the Flipper but everything I have tried is not working.

Example code from Excel file has CD Play as “03” (data) and “8124” (custom code). I have tried the following:

name: CD Play
type: parsed
protocol: NEC
address: 81 24 00 00
command: 03 00 00 00

That doesn’t do anything. I have tried some other codes without success. I have even tried running the two hex values through a convert I found online to generate an IR HEX like below and it doesn’t work (tried adjusting frequency to other TASCAM remotes, no joy).

name: CD PLAY
type: raw
frequency: 38029
duty_cycle: 0.330000
data: 0000 006D 0022 0002 0155 00AA 0015 0040 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0040 0015 0015 0015 0015 0015 0040 0015 0015 0015 0015 0015 0040 0015 0015 0015 0015 0015 0040 0015 0040 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0015 0040 0015 0040 0015 0040 0015 0040 0015 0040 0015 0040 0015 05ED 0155 0055 0015 0E47

Anyone care to take a look? I know I’m probably just overlooking something.

Link to TASCAM Excel file in question - TASCAM Excel LINK

Ok, after updating the remote codes from Flipper-IRDB, I found some TASCAM ir files (Converted/Pronto/T/TASCAM). The CD-RW2000.ir and CD-RW700.ir works with some of the CD side of the deck. Going to take a look at ir files and see what is the difference.

EDIT: Found the frequency (38381) and duty cycle (0.330000). Now to play with hex values again.

The values in data: are timings, so there are decimal values, not hex. If your hex values represents the timings depends on the source.

Let’s look at data: 8937 4455 573 1667 573 573 573 573 573 573 573 573 573 573 573 573 573 1667 573 573 573 573 573 1667 573 573 573 573 573 1667 573 573 573 573 573 1667 573 573 573 573 573 573 573 573 573 573 573 573 573 573 573 573 573 1667 573 1667 573 1667 573 1667 573 1667 573 1667 573 1667 573 44006 8937 2215 573 95282

I assume the 8937 4455 is the header. Followed by 573 1667 a one and
573 573 573 573 573 573 573 573 573 573 573 573 573 1667 → 000 0001
573 573 573 573 573 1667 573 573 573 573 573 1667 573 573 573 573 → 0010 0100
573 1667 573 573 573 573 573 573 573 573 573 573 573 573 573 573 → 1000 0000
573 573 573 1667 573 1667 573 1667 573 1667 573 1667 573 1667 573 1667 → 0111 1111
573 44006 8937 2215 573 95282 → footer

I assume 1000 0001 0010 0100 is the static address and 1000 0000 0111 1111 is the command.
The address seems to be 16 bit and the command 8bit + 8bit reverse.
If you’ll change the first 8bit of the command to 1000 0001 the following 8 bit needs be equivalent 0111 1110.

No hex at all, until the protocol is parsed by the Flipper.

Edit: Source https://github.com/Lucaslhm/Flipper-IRDB/blob/main/Converted/Pronto/T/TASCAM/CD-RW2000.ir

Thanks for the replay. I managed to build a mostly working ir file from a combination of 3 files for TASCAM devices. I’m just missing 1 or 2 buttons but they are not really important for my needs. However I have noticed that the Flipper doesn’t repeat the IR codes all that great for searching/seek forward and backward through a CD. Not sure what that is all about but for the most part I’m happy with the out come. Now to look at options on getting a learning remote or just build one from components. Mostly doing this for a learning experience.

The Flipper won’t repeat the command. I already started to patch the handler, but with no success at the moment. I am really not a developer :wink:

You can take the data: part and app and the same command multiple times. Just make sure the delay between the snippets is big enough. But this would be a static amount of repeats at one button. Still not continuous. But a workaround for some scenario.