Here are a number of links on interfacing to Xanbus:
Any interest in XanBus protocol
Xantrex C35/C40/C60 Display
Help with Xanbus protocol
monitoring the system
TCP/IP Modbus using Conext Combox
Had to switch to conext gateway for xw pro, missing combox modbus monitoring
My take on the above is that Xanbus is a proprietary CAN-bus implementation, and Schneider has implemented encryption keyed off their device serial numbers to prevent third part configuration and control. Furthermore, if you do crack their protections and modify parameters via third party means, it will nullify your warranty. I understand why, and am not going to fight that battle, yet. There are some glimmers of hope to be able to extract data from Xanbus for read only purposes, but I need to do a lot more research.
Something that I came upon revisiting this is that SE provides Modbus via RS-485 and TCP/IP through their ComBox and Conext Gateway. Although this is not an Open Source solution, it does provide a start point that will allow me to begin utilizing emonCMS and learning more about the OEM stack. I already have a ComBox, so I am setting up an Ubuntu server, install emonCMS and attempt to feed Modbus data via TCP/IP. The following link is the Modbus mappings for all the SE devices, most of which I posses.
I will post my progress here. Please advise if I should start a new topic, split or whatever.