Your Universal Remote Control Center
RemoteCentral.com
Crestron Control Systems Forum - View Post
Previous section Next section Up level
Up level
The following page was printed from RemoteCentral.com:

Login:
Pass:
 
 

Topic:
RSD and IP conflict with D3 and SIMPL/Crestron App for IOS
This thread has 8 replies. Displaying all posts.
Post 1 made on Monday June 19, 2017 at 23:25
AvidScramber
Junior Member
Joined:
Posts:
June 2017
4
I am a relatively new Crestron programmer and I am making a silly mistake that I am hoping you can spot.

This is on a DINAP3, programmed with D3Pro.  Program 01 has a virtual keypad, tied to IP-ID 6.  It is exported via RSD from the D3Pro lighting program.  It is up and running.  This is the only IP-ID on the Program 1 IP table.

Program 02 is a SIMPL program with only two devices configured.   One device is the same virtual keypad, which was added to the SIMPL program via importing the RSD.  The second device is the Crestron App, on IP-ID 7.  There is a basic interface on the ipad, made with VTPro-e, that seems to be working fine.

When program 02 is loaded, the Toolbox error log says that IP-ID 6 is already in use.  What I can't figure out is why this is an error, or more important, how to fix it. it.  How can you ever export a device without ending up with an IP ID conflict if it shows up in the original program and in the exported program.

467. Info: LogicEngine.exe [App 2] # 2017-06-18 21:23:54  # Loading program from \SIMPL\app02
468. Info: LogicEngine.exe [App 2] # 2017-06-18 21:23:54  # Loading Program \SIMPL\app02\app_process_1_1.bin.
469. Error: LogicEngine.exe [App 2] # 2017-06-18 21:23:54  # Exclusive device Slot-02.IP-ID-06 is in use by Program 01
470. Notice: LogicEngine.exe # 2017-06-18 21:23:56  # **Program 2 Started**
471. Info: LogicEngine.exe [App 2] # 2017-06-18 21:23:56  #  Going to steady state now 


Thank you.

Last edited by AvidScramber on June 20, 2017 00:03.
Creston, Lutron RRA, SONOS, Z-Wave, AV/HDBaseT, various engineering and programs, and other home automation
Post 2 made on Tuesday June 20, 2017 at 08:28
Tony Golden
Founding Member
Joined:
Posts:
August 2001
639
Make sure you're using 127.0.0.2 as the RSD's IP address, in both programs.
Post 3 made on Tuesday June 20, 2017 at 15:08
kgossen
Super Member
Joined:
Posts:
March 2008
2,852
It shouldn't be in both programs. The Keypad at ID 6 is ONLY in program 1 and NOTHING in program 2 can be using that same ID. The reason for the RSD is so that you only have to have the Keypad in 1 program but can access it from any of the others.
"Quality isn't expensive, it's Priceless!"
OP | Post 4 made on Tuesday June 20, 2017 at 23:13
AvidScramber
Junior Member
Joined:
Posts:
June 2017
4
For Program 02 -- I thought SIMPL brought in IP-ID 6 automatically when I imported it.  How do you remove the IP-ID after importing the RSD?

Thanks again for your help.
Creston, Lutron RRA, SONOS, Z-Wave, AV/HDBaseT, various engineering and programs, and other home automation
OP | Post 5 made on Wednesday June 21, 2017 at 00:10
AvidScramber
Junior Member
Joined:
Posts:
June 2017
4
kgossen: Went into SIMPL to try to remove the IP ID on the virtual keypad in Program 02.   I can't figure out how to have the RSD for the virtual keypad in program 02 without it having the IP-ID it was imported with.  If I delete the device in the configuration, I lose the signals.

Tony Golden: I tried setting it to 127.0.0.1 on both devices to no avail.
Creston, Lutron RRA, SONOS, Z-Wave, AV/HDBaseT, various engineering and programs, and other home automation
Post 6 made on Wednesday June 21, 2017 at 08:33
SWOInstaller
Senior Member
Joined:
Posts:
October 2010
1,259
On June 21, 2017 at 00:10, AvidScramber said...
kgossen: Went into SIMPL to try to remove the IP ID on the virtual keypad in Program 02.   I can't figure out how to have the RSD for the virtual keypad in program 02 without it having the IP-ID it was imported with.  If I delete the device in the configuration, I lose the signals.

Tony Golden: I tried setting it to 127.0.0.1 on both devices to no avail.

You need to change the RSD to 127.0.0.2. This is the address used for all internal RSD's of a processor.
You can't fix stupid
Post 7 made on Wednesday June 21, 2017 at 10:10
kgossen
Super Member
Joined:
Posts:
March 2008
2,852
On June 21, 2017 at 00:10, AvidScramber said...
kgossen: Went into SIMPL to try to remove the IP ID on the virtual keypad in Program 02.   I can't figure out how to have the RSD for the virtual keypad in program 02 without it having the IP-ID it was imported with.  If I delete the device in the configuration, I lose the signals.

Tony Golden: I tried setting it to 127.0.0.1 on both devices to no avail.

I might have misinterpreted what you were doing. It sounded like you were adding the KP at ID 6 in both program 1 and 2. It just needs to be in your D3 RSD file.

Like SWO said, address in both programs for the RSD needs to be 127.0.0.2
"Quality isn't expensive, it's Priceless!"
OP | Post 8 made on Monday June 26, 2017 at 22:42
AvidScramber
Junior Member
Joined:
Posts:
June 2017
4
Thanks very much.  Switching both to 127.0.0.2 resolved the conflict in the error log.

Somehow my virtual button press 1 isn't triggering the global preset (from program 01) that it is tied to.  But it's not because of the IP ID error any more.  I can see the signal showing up in the SIMPL debugger for program 02.

Thanks again.
Creston, Lutron RRA, SONOS, Z-Wave, AV/HDBaseT, various engineering and programs, and other home automation
Post 9 made on Friday September 15, 2017 at 10:54
tgrugett
Select Member
Joined:
Posts:
August 2004
1,755
Use debugger viewing program 1 (D3) to see if the signal triggered in program 2 is making it to program 1.

Also make sure that the button press in program 1 is doing what you want.

The RSD is just a form of Ethernet Intersystems Communication. If it were two processors you would use the IPs or host names of the processors in eachothers IP tables. On a 3 series processor you would use the 127.000.000.002 loopback address. Once this is done correctly then what ever signal input you trigger on the RSD on one program should appear on the corresponding output of the other.

The problem is that you will not see the actual RSD in D3 without opening the associated Simpl file that is generated. Make sure you have done the following...
  1. Check the box for the device you want to include during the creation of the RSD in D3. I assume you did this.
  2. Make sure you set the 127.000.000.002 address for the RSD when creating it in D3.
  3. Double check the RSD properties in Simpl once it is imported and make absolutely sure the 127.000.000.002 is set for it.
  4. Make sure that you look at all available signals created for that device in the RSD that is imported into simple.
  5. Make sure that you hold high the enable signal for that device if it has an enable signal.


Jump to


Protected Feature Before you can reply to a message...
You must first register for a Remote Central user account - it's fast and free! Or, if you already have an account, please login now.

Please read the following: Unsolicited commercial advertisements are absolutely not permitted on this forum. Other private buy & sell messages should be posted to our Marketplace. For information on how to advertise your service or product click here. Remote Central reserves the right to remove or modify any post that is deemed inappropriate.

Hosting Services by ipHouse