diff --git a/SIMPL-Bridging.md b/SIMPL-Bridging.md
index fe57a58..6cc42e4 100644
--- a/SIMPL-Bridging.md
+++ b/SIMPL-Bridging.md
@@ -290,6 +290,8 @@ Example device config: <https://github.com/PepperDash/Essentials/blob/master/Pep
 
 6. Related to item 5, you can use the same paradigm with respect to physical device communication. If you were to have a DSP device in some rooms communicating over RS232 and some via SSH, it would be trival to swap the device from a Com port to an SSH client in the Essentials Devicee Config and update the Bridge Config to brigde to the desired communication method. Again this would require no change on the SIMPL Windows side as long as you maintain the same join Start in the Bridge Device Configuration.
 
+7. It is important to note that ```eiscapiadv``` and ```eisapi``` instantiate versions of bridges and joinmaps that are incompatible with one another.  If your device utilizes ```IBridgeAdvanced``` it can only bridge to an ```eiscapiadv``` device.  Similarly, if your device utilizes ```IBridge``` if can only bridge to an ```eiscapi``` device.  Remember this when writing new plugins or device classes, adn when building bridges to link bridges of disparate types to your SIMPL programs.
+
 ## Common Use Cases
 
 1. There are 10 conference rooms that all operate the same, but have hardware differences that are impossible to account for in SIMPL Windows. For example, each room might have a DM-MD8X8 chassis, but the input and output cards aren't all in the same order, or they might be different models but function the same. You can use Essentials with a unique configuration file for each hardware configuration.