ELK M1 and ISY994 communication issue

Hi all,
 
I recently purchased an ISY994, a ELK M1 Gold system, and the relevant peripherals to supposedly make them communicate (M1XEP, ELK Integration Module). 
 
But they won't. I won't bore you with a wall of text, so I've made some screen-grabs and a screen cast video. More info can be conveyed that way. 
 https://www.youtube.com/watch?v=SZEntoHpefE&feature=youtu.be
 
Bottom Line: The ISY 'sees' the ELK M1XEP, gets some of the data (partial zone information), but doesn't get the area name, etc.
 
Things tried (with the help from Steve at Universal-Devices):

• FULL ISY994 Reset
• Connecting to unsecure port using ElkRP (works fine)
• Lots of different port configurations
• New ISY994

From ISY Log file:
Wed 09/03/2014 10:14:57 AM : [ELK-TX-R   8] 06as0066
 r=1 - Send Failed
Wed 09/03/2014 10:14:57 AM : [ELK         ] Connect Successful
Wed 09/03/2014 10:15:00 AM : [        Time] 10:15:01 1(0)
Wed 09/03/2014 10:15:29 AM : Elk Query All Failed, requesting retry
Wed 09/03/2014 10:16:04 AM : Elk Query All
Wed 09/03/2014 10:16:19 AM : [ELK         ] Disconnect
Wed 09/03/2014 10:16:19 AM : [ELK         ] Connect
Wed 09/03/2014 10:16:19 AM : [ELK         ] Connect Successful
Wed 09/03/2014 10:16:29 AM : Elk Query All Failed, requesting retry
Wed 09/03/2014 10:17:04 AM : Elk Query All
Wed 09/03/2014 10:17:29 AM : Elk Query All Failed, requesting retry
Wed 09/03/2014 10:17:34 AM : [ELK         ] Disconnect
Wed 09/03/2014 10:17:34 AM : [ELK         ] Connect
Wed 09/03/2014 10:17:34 AM : [ELK         ] Connect Successful
Wed 09/03/2014 10:18:04 AM : Elk Query All
 
 
Help!

ISSUE SOLVED:
 
For posterity, the issue was a leading space in the area name in the ELK configuration.