RDFS JP1.2

Post by **vickyg2003** » Fri Jul 19, 2024 2:25 am

I have been out of the loop for a while. I just bought some new equipment and went to upgrade my remotes and found that I couldn't get anything to work with my old Comcast JP1.2 nor my Atlas JP1.2 remotes.

It turns out that the official RDFs for both of these remotes have been changed to make them into SST remotes instead of HCS08.

So anything that needs a protocol upgrade doesn't work.

Post by **The Robman** » Fri Jul 19, 2024 6:47 am

Hey Vicky, welcome back. What are the signatures of the remotes that you believe are incorrectly categorized?

Post by **vickyg2003** » Fri Jul 19, 2024 8:34 pm

CS301009 Comcast 1067

The processor has been changed from HS308 to SST

Remote Chart and the RDF

It took me forever to figure out why nothing worked.

I've been having all sorts of problems, and because I'm pretty rusty, I am not sure if its a PICNIC problem or not. But the RDF is not my problem.

Post by **The Robman** » Sat Jul 20, 2024 8:16 am

I just looked it up on the old remote chart and it appears the CS301009 was the odd-man-out being HCS08 when all the others were SST, so this RDF might have got swept up in some mass update.

Could you change it back to HCS08 and test that it works now, then load a copy of it here, for Graham to find and incorporate into RMIR:
https://www.hifi-remote.com/forums/dload ... &cat_id=44

3FG · Post by **3FG** » Sun Jul 21, 2024 12:41 am

I looked in SourceForge, and the change occurred between 2.12.8 and 2.13.0. The only difference even for 3.0.15 is the processor type, so Graham could just restore the 2.12.8 version. I think the extender version of this RDF also needs to be restored.

Post by **The Robman** » Sun Jul 21, 2024 8:34 am

3FG wrote:I think the extender version of this RDF also needs to be restored.

The CS301X09 extender rdf still says HCS08

Post by **vickyg2003** » Mon Jul 22, 2024 6:19 am

As directed I uploaded the RDF, although it looks like I am a bit late.

Post by **The Robman** » Mon Jul 22, 2024 6:51 am

vickyg2003 wrote:As directed I uploaded the RDF, although it looks like I am a bit late.

Not late at all, did that change mean that everything works again, did you test it? I've let Graham know that this change is coming, but he's busy with some non-JP1 projects at the moment, so there's no rush.

Post by **vickyg2003** » Wed Jul 24, 2024 9:39 am

Yes, once the processor is correct, the right protocol can be loaded and the remote works.

I am using an old Serial JP1.1/1.2 cable with a dynex adaptor. It works fine on Jp1.2 and JP1.3 remotes when I have the older driver loaded.

I am having issues with the Atlas 1056b03 remotes with the Max something-or-other processor. I keep getting the no-remote-found message.

Does that remote require the newer cable? I know I built some, but for the life of me I can't find them.

Post by **The Robman** » Wed Jul 24, 2024 11:10 am

vickyg2003 wrote:I am having issues with the Atlas 1056b03 remotes with the Max something-or-other processor. I keep getting the no-remote-found message.

Does that remote require the newer cable? I know I built some, but for the life of me I can't find them.

I'm not sure, but I wouldn't be surprised. Making a JP1 cable now is so easy, all you have to do is buy an FTDI FT232RL or Prolific PL2303HXD cable, make sure you get one with 6 connectors though. Then you need to replace the plug with a 2*3 plug.

https://www.hifi-remote.com/forums/viewtopic.php?t=16360

Post by **mathdon** » Tue Aug 06, 2024 3:45 am

The Robman wrote:I've let Graham know that this change is coming, but he's busy with some non-JP1 projects at the moment

I'm still busy but have now made this change, which will be in the next release. I don't know how the change to SST got made but my apologies, Vicky, for it.

Post by **mathdon** » Fri Aug 09, 2024 4:36 am

The correction from SST to HCS08 is now included in development build v3.0.17 in the RMIR Development folder on SourceForge. If this build passes other tests then I will convert it into an official release.

Post by **vickyg2003** » Thu Sep 05, 2024 3:26 pm

Sorry to be so late with the reply.
I was going absolutely bonkers with my new Samsung "smart" TV. The new tv came with a voice remote that had very few buttons similar to a roku remote and I was trying to get a working remote where I could enter channel numbers and do things that needed to be done. Hubby couldn't watch TV because it kept doing things on its own. Turns out the TV has a built in microphone and is constantly listening for Hi Bixby, even when it was off, and everytime my husband said Vicky, the TV thought he said Bixby and was TV was doing all sorts of nasty things. And because I was out of the room, I didn't see the little listening symbol on the screen....

Anyway during the trial and error trying to find codes that worked I found two ways to break RMIR on my last trip, and meant to convey that to Graham.

My last time here I was doing a discrete hunt on my NEVO I kept crashing RMIR and wasn't sure what I was doing wrong, until crash #17. If you delete a function without making absolutely sure it is removed everywhere it might be used. RMIR silently crashes, but everything seems to be working flawlessly until you try to save your work, or upload it to your remote. Once you try to save it, of course it can no longer be opened.

Of course deleting a device if a function is used on another device or remains in a macro, also crashes. Again silently very happy, until you go to save it.

Post by **The Robman** » Thu Sep 05, 2024 6:03 pm

Apparently, you can turn off Bixby, if it's becoming a problem.

To disable Bixby on your new Samsung TV, go to Settings > General > Bixby Voice Settings. You'll want to go to Voice wake-up and turn it to Off. This ensures that the TV isn't always listening for the wake words 'Hi Bixby' and should never activate. Now, just make sure to never tap the Microphone button on your remote, and Bixby should never appear.

Source: https://www.techradar.com/how-to/how-to ... samsung-tv

Post by **vickyg2003** » Fri Sep 06, 2024 11:41 am

Yes I had to disable Bixby, unless I wanted to change my name!

At first I thought it was just the super sensitive CEC. That has never been a problem on my older TV's but with this new one you can't remove a DVD, or turn on the the stereo without the TV turning on or changing sources.

After turning off CEC, we still had the TV randomly turning on, ads popping up and covering what we were watching all the time. Problem was my husband didn't notice what was happening, he was just extremely frustrated by the whole "smart" TV thing. And since I never say my own name, so it took forever for me to diagnose the problem. Vicky=Bixby. I pretty much thought he was losing it! LOL! Bixby is pretty useless if you want to change sources, change channels, change apps, can't turn on Closed captioning. The TV listening all the time, really creepy!

The new remote is similar to a roku or firestick remote, no numbers, no TV guide, 100's of button pushes to do the simplest things. Can't turn on Closed captions by voice and no discrete it takes 14 button pushes, and if DH doesn't close all apps he keeps getting stuck in multi-view.

The new remote is not IR, but the TV does respond to IR commands. Many of the functions in the Samsung Master file do different things than they did in the past. I think if I had to use the original remote I would have returned the darned thing. The picture is absolutely beautiful, but the OS is really awful. Can you imagine having 9 numbers pop up on the screen when you want to change the channel, and then going right-right-ok-left-ok -right-right-right-right-right to punch in a number. Yuck.

The getting beyond 6 apps is very difficult, you have to wade through pages and pages of ads to find the rest of the apps. We can't figure out what if anything ever has focus and can't read the tiles to see what apps we are starting.

So after 2 months of struggling turned off all the features and using a Roku!