My team and I have recently programmed an RTI Panel for our client. Just today we added very long system macros for her XP-6. However, when we opened our program in ID and try to open one of our long macros, ID locks up and seems to not recover. We can open shorter macros just fine.

My question is: has anyone run into this issue before, or know a fix for it?

Thanks!

What is in the macro?

How big is the macro ?

This is the largest macro I have done, and from what I can tell is the maximum a macro can handle, if i tried to input anything else it would crash ID.

I tried my best stitching it together, and there are 4 more pages but I could not be bothered to carry on stitching. This macro leads to 3 other macro's that are exactly the same size.

System runs fine, opens fine.

If the size of the macro is the problem, which I doubt, there are many ways to shorten the macro. Chances are you could probably use less lines of commands using a different approach. I would love to see this macro!

Sorry picture didn't load, too big, shrunk it down, hopefully you can see it is silly big. But proves a point that a macro has to be utterly huge to crash.

The picture is there now. Like I said there is 4 more pages to be stitched on to that, which leads to 4 more macros.

I'd love to post what I put in the macro, but I can't open it in ID without crashing the program. What it controlled was a Driveway Annunciation system by Car Tell. When the car tell triggered the contact closure, the sense into RTI's ports would trigger the macro - which would shoot an IR command to an iPod, play a sound over their receiver, switch any TV that is currently on to their DVR camera feed, switch to the RTIPanel camera page with their camera view, then after ten seconds return to whatever source (using if-thens) the TV was previously on by setting and clearing flags. What made it so long was if the first source in the If-Then wasn't the source, it would refer to another macro and check that for its flag, etc.

I'm hoping there is a way to be able to open these macros. Seems like it is a limitation on ID itself and not the processor - seeing as it worked like a champ in our tests. We've tried different computers with varying amounts of RAM with no luck. I'm thinking ID might not be able to handle super-long macros.

Does it look any where near as big as the picture I have posted ? remembering there is 4 more sections to that.

It wasn't nearly as long as yours was.

Well I have 4 macro's bigger than the size shown in the picture. And they work fine.

Maybe you some how you have written in something in the macro that could not be.

Many versions of ID previously, I some how created a macro with a toggle IR code with a system variable test, ID should have thrown up an error message, but allowed the macro to close and save, thus crashing my entire file over and over again.

It wasn't until I found the offending macro which I had accidental created, deleted it, was all back and normal.

What I would say is try re-create your macro, but slowly, seeing if a step you have created causes an issue.

Thank you for the help. I called into RTI Tech Support and they gave me a reason and a solution for what was happening. RTI theorized that possibly one or more drivers became corrupt in the file during a save and caused the macros using those drivers to lock up the program.

The solution is to create a new system file and import all of the devices from the previous file. Seemed to do the trick.

PatG1, glad there was a solution that worked! RTI tech support staff are great people!

One a completely random side note, I'm much more interested in the ridiculously long macro Diskreet is referencing...

Any further details on why you would be creating a godzilla-macro?

The reason I had to do these huge macros was for a power control unit.

It had 8 controllable power outlets but the only way I could control the unit with RTI was with the http driver. The problem I had was you could not send a single command to turn on/off a particular outlet, you had to send a full configuration of 1 on 2 off 3 on etc.

So basically I saw a challenge and thought I could do it but you have to address every single possibility of configuration of a 8 way unit.

So with a iPad you have 8 buttons, which toggled 8 flags, then when you had set all your flags you sent the config which would in turn check all the flags of all the possibilities and send the correct config.

It took me a while to get my head round all the possibilities and how to test all the flags within the rti system.

It was complicated, but it works which is the main thing !