E-Z Learn Device Files

I have created a device file using E-Z Learn, and the commands work great when using E-Z Learn to test them, but when the device file is loaded into a custom app, a no match is reported from the slink-e server. Any suggestions?

My long-term plan is to get away from the E-Z Learn device file and use the standard format. Where can I find more documentation on deciphering the information given from the oscilloscope? How does one determine the bit pattern (I am assuming one is high and zero is low, but what about the spacing between the one's and zero's)? What else besides the bit pattern can be determined from examining the oscilloscope?