Using an AB 1734-ADN Point I/O DeviceNET head module with non-AB DeviceNET master?

You can get it to work in a basic fashion using the Auto Start Mode of the 1734-ADN. Enabling Auto Start Mode will do a quick configuration of the PointBus and get everything communicating, and then you can configure it as a generic DeviceNET slave. Here are the parameters of the 1734-ADN module (comma separated, so you should be able to bring this into Excel):

Param,Description,Class,Instance,Attribute,DataType
1,Autobaud on DeviceNet,3,1,64,USINT
2,Set Backplane Baudrate,312,1,5,USINT
3,Set Backplane Autobaud,312,1,6,USINT
4,AutoAddress Backplane Modules,312,1,4,USINT
5,Auto Start Mode,312,1,11,USINT
6,Phys List Acquire Status,312,1,8,USINT
7,Poll/COS Connection Consume Size,312,1,B,UINT
8,Poll Connection Produce Size,312,1,D,UINT
9,COS Connection Produce Size,312,1,E,UINT
10,Strobe Connection Produce Size,312,1,C,UINT
11,Cycling Node Status,312,1,F,SHORT_STRING
12,Cycling I/O Mapping,312,1,12,SHORT_STRING

Note that the Class, Instance, and Attribute columns are in HEX. So, use your DeviceNET master software to write the value 1 to parameter 5. That should get everything communicating (give it a minute).

After that, execute some Reads from parameters 7 through 10 to get the mapped I/O sizes for each type. By default your outputs are polled and your inputs are change-of-state. All of them include 2 bytes (in or out) for the head module itself, so your inputs will start at byte index 2 (as in 0, 1, 2). Look in the 1734-ADN manual for information about how much data each input or output slice produces or consumes.

Without RSNetWorx, there's no way to configure the more advanced features of the Point I/O, but this will get you operating.