Atlas 3000 & 3033 JP1.3 extender

unclemiltie · Post by **unclemiltie** » Mon Jan 05, 2009 8:16 pm

Lots of questions

1: I don't have an answer for Cap'n on why he is having issues, I'm going to have to dig into it.

2: The X_POP and X_PUSH are not yet implemented. The idea was for these to push and pop the current (temporary) device onto a stack so that you can save/restore state in macros. I thought it would be useful one time, but now am not sure if it would be or not.

3: The DEC2HEX is part of one of the EXCEL add in packages, it converts decimal to hex numbers. EXCEL only knows how to compute stuff in decimal, so to deal with hex you have to convert it to decimal, then do the computation and then back to hex.

4: I don't see the mis-alignment of the notes for the device and protocol for LDKP and the backlight control. This is absolutely a hack though, when I build the extender I append a "notes" file to the end of the HEX that is generated and if I move things around I have to re-edit by hand the text. But I thought it was useful

5: There is no functional difference between Mike's protocol and the new built in, I stole his code! There is a difference in how it's enabled though.

Mikes will be in the protocol and device upgrade area, all of the code. Mine will show up only with the header and JP to the private area. It shouldn't make a difference if you install mike's protocol when installing the extender, it'll just take up more upgrade area.

greenough1 · Post by **greenough1** » Mon Jan 05, 2009 11:56 pm

mdavej wrote:Jeff,

I think pause takes 2-bytes. Here are some values you can try:
0A 62«1 second pause»
14 72«2 second pause»
1E C2«3 second pause»
28 53«4 second pause»
32 A3«5 second pause»
3C B3«6 second pause»
46 00«7 second pause»
50 90«8 second pause»
5A E0«9 second pause»
64 F1«10 second pause»

If you look at a pause upgrade in RM, it's the last 2 bytes in each key move when you make a function for a certain duration and assign it to a key.

I tried to enter a 2 byte value for the hex on the PAUSE special protocol tab and get an error : invalid data. the value $3CB3 is not within the valid range $00-FF, when I entered 3CB3 for the hex value.
Any other suggestions?
jeff

mdavej · Post by **mdavej** » Tue Jan 06, 2009 8:51 am

Each byte is 00-FF. Put a space between byte 3C and byte B3.

greenough1 · Post by **greenough1** » Tue Jan 06, 2009 10:36 am

Thanks again mdavej. I didn't try that last night.
Best,
jeff

greenough1 · Post by **greenough1** » Tue Jan 06, 2009 8:53 pm

Ok. Got the pause to work on a button or a shifted button with 2 bytes. However, it will only fire in a macro right after a fresh upload and activation. After that it won't fire. The key macro version or shifted key (SP) will. It just works once after a fresh upload and activation.

Here's the latest IR. Pause is on TV:Blue and TV:shift+Blue

LINK

Best,
jeff

mdavej · Post by **mdavej** » Tue Jan 06, 2009 11:06 pm

Seems ok, but you may have some unintended shift cloaking going on there. Delete the blue macro and see if that helps..

I do see an infinite loop on xshift-power that could be causing problems. You may want to rework that one. And you have some key moves and macros assigned to the same shift-power and xshift-power keys. That could have unpredictable results as well. Not sure if you're trying to shift cloak, but to have it work properly, you can't have anything assigned to the shifted versions of those keys. If the shift-power key moves are the codes for power, you can just delete them. When a macro calls shift-power and finds nothing assigned to it, the original power command will be performed. If the shift-power's are really discrete on/off's, just put those on the discrete on/off keys. Then you won't need keymoves for them at all.

greenough1 · Post by **greenough1** » Tue Jan 06, 2009 11:26 pm

Hi mdavej,
Hope you didn't spend too much time on this. I just figured it all out (and just say your post). I had a shift+power keymove for TV. Deleting that and the TV-power-on macro works. I also got rid of the shift+power and xshift+power on DVD and just put those on unused buttons. Everything works beautifully.

Here's the final version : LINK

In testing it was fun watching the lights blink on the device keys as the macros fire. Very entertaining indeed.

Thanks again UncleMiltie and mdavej. UncleMiltie, the offer for a beer still stands

Best,
jeff

unclemiltie · Post by **unclemiltie** » Wed Jan 07, 2009 12:19 am

I'm in for a beer...... send me an email direct and we'll get it set up.

greenough1 · Post by **greenough1** » Wed Jan 07, 2009 12:55 am

PM sent with my personal email.

Best,
jeff

unclemiltie · Post by **unclemiltie** » Thu Jan 08, 2009 2:20 pm

Slight update. No extender changes but some slight changes to the RDF's to fix some key binding issues.

V2.04 has replaced V2.03

greenough1 · Post by **greenough1** » Tue Jan 20, 2009 11:13 pm

I've run into an odd issue with V2.03, so I've not updated to V2.04. If you think I should upgrade, i.e. this bug is related to the rdf change, let me know.

I've got a setup for the main HT loaded into the Atlas 1056 sig 3A333 ("Saved" link below). After a couple of days (2-3), something happens (it happens to one of my kids and I've been unable to reproduce what they did.
I'll find the CBL box off (it should always be on) and the CBL device (comcast 6412) power button controls the TV power (mits HD TV).
Here's the downloaded file from when it's "broken": Bit-rotted

Deactivating and reactivating doesn't fix it. I tested a fair number of other devices, buttons and macros and they all seem to work except for this one.

If I reload the file saved to disc and reactivate, then the setup behaves normally,i.e. CBL power controls the boxes poweragain. Here's the file that seems to work fine on reload and activate:
Saved

I tried to look at the raw download page as something has to have changed, but I can't find it. Is there a tool that'll compare the two dumps and pick-out the change?

Thanks,
jeff

greenough1 · Post by **greenough1** » Tue Jan 20, 2009 11:44 pm

ok. I've done more off-line testing and it's not something the kids did. It's a wierd bug that you can diagnose by watching which device key lights when you press the power button.
- load the setup and activate (either of the linked files in the above post)
- short press CBL, then power. The CBL button lites. Good this is correct.
- short press any other device key, say VCR, then power and VCR lites. This is correct.
- NOW short press CBL again, then power and VCR lites. This is wrong.

- short press DVD then power and DVD lites. Good.
- short press CBL again then power and you get DVD to flash. This is wrong.

Power for CBL and only CBL is remapped back to the last active device.

I found a case that get's it back to working.
- press setup+CBL (this is my 6th device), then power and CBL lites.

Another device key, then short press CBL and power is for the last device. Very odd.

jeff

greenough1 · Post by **greenough1** » Thu Jan 22, 2009 10:15 am

Unclemiltie,

Could the above bug/user error/feature be due to a key binding issue/rdf change that's in V2.04?

Thanks,
jeff

mdavej · Post by **mdavej** » Thu Jan 22, 2009 1:47 pm

The key binding changes only have to do with what keys are allowed to be shifted or xshifted. IIRC, discreteon/off were shiftable/xshiftable when they shouldn't have been. So it's not related to your issue.

I've seen something similar. I couldn't figure out what was going on either, so I moved my misbehaving macros to different phantom keys and the problem went away, i.e., using phantom4 instead of phantom2. I can't explain what went wrong or why the change fixed it.

greenough1 · Post by **greenough1** » Thu Jan 22, 2009 3:16 pm

Thanks mdavej,

If you look at my setup, I followed (finally) your advise and cleaned up my LKP so that the short sides are empty and deal with keyset assignment, up front in the macros.

I'll try moving some keys around.

It seems to me that it started misbehaving around the time I added a LKP on FWD that is short:FWD and long:20sec skip. I think the 20sec skip is a keymove on phanton 6 or 7.

I'll back out that change and see what the effect is as well as moving things around.

jeff