how to configure analog out card WAGO 750-556 2 channel analog out

Use code blocks when inserting long pages of code.

KSS version?

Do the digital I/Os work? Your IOSYS has 32 inputs and 32 outputs configured, but the hardware appears to only have 16 each.

What error messages are you getting?

Post your DEVNET.INI file.

Do you have communications with the bus coupler at all?

Quote from SkyeFire

Do the digital I/Os work? Your IOSYS has 32 inputs and 32 outputs configured, but the hardware appears to only have 16 each.

What error messages are you getting?

Post your DEVNET.INI file.

Do you have communications with the bus coupler at all?

this was discussed many times so there are plenty of resources already on the forum. as i recall this bus coupler tend to pack analog values at the begin of PDO to avoid fragmentation...

physical order may be:

Slot/module/desc.
0 750-346 ; bus coupler
1 750-430 ; digital input
2 750-430 ; digital input
3 750-530 ; digital output
4 750-530 ; digital output
5 750-556 ; analog input
6 750-600 ; terminator

so you may expect input PDO to have data ordered like this:

INPUTS
1 750-430 ; digital input
2 750-430 ; digital input
5 750-556 ; analog input

OUTPUTS
3 750-530 ; digital output
4 750-530 ; digital output

but reality is likely to be

INPUTS
5 750-556 ; analog input
1 750-430 ; digital input
2 750-430 ; digital input

if your bus coupler is really configured to be node 5, then digital IO (with analog module removed) should work with

[DEVNET]
INB0=5,0,x2
OUTB0=5,0,x2

the analog module is the output type

so input mapping should not change but the output mapping will likely shift 4 bytes.

[DEVNET]
INB0=5,0,x2 ; stays the same
OUTB0=5,4,x2 ; shifted by 4 bytes, skip bytes 0,1,2,3
ANOUT1=5,0,16,3,CAL32767 ; byte 0,1
ANOUT2=5,2,16,3,CAL32767 ; byte 2,3

your DEVNET.INI shows node configuration is using address 5. is that correct? are you able to get the unit work correctly without analog module? can you make anything work...?

if not...

you may be skipping important steps... you need to start by ensuring correct hardware setup:

check wiring, termination, node configuration, bus speed etc. it is not even certain if you are using correct ports or DN master. software configuration suggests you are trying to use MFC but - are you? are you sure you are not using LPDN? when hardware is not set correctly, situation is hopeless and no amount of trying software changes will get you anything.

once the hardware setup is ok, then it is time to move onto software configuration. this includes setting correct values in DEVNET.INI and IOSYS.INI.

to see how PDI structure is setup, you need to read the manual for your bus coupler. i would expect it to be much like 750-306 so previous comments should apply.

so hardware setup is ok. that is good.

only need to adjust IO mapping.

btw, i see in your IO list two input modules (8+8 = 16 inputs). that is only 2 bytes.

same goes for digital outputs. but your file shows you are mapping 2 words, rather than 2 bytes.

[DEVNET]
inw0=5,0 x2 ; why 32 points?
outw0=5,0 x2 ; why 32 points?

at any rate, the node address is 5 or this would not work. so did you try something like in post #8?

You still haven't answered the question about error messages. Usually, adding I/O slices to a Wago block will change the I/O byte size of the block, which will cause the KRC to throw Devnet faults.

Also: when adding the analog slices, do the digital I/Os stop working?

I would recommend trying the Telnet diagnostics, with and without the analog slices, and see what changes:

The KRC1 and KRC2 series controllers are kind of split-brained -- they run Windows (95 or XP) for the user interface, but at the same time run VxWorks in parallel to handle the actual robot operations.  These two operating systems *think* they are running on separate machines, communicating via a TCP/IP link.  What this means for us is that you can Telnet from the Windows side into the VxWorks side.  It turns out there are some low-level diagnostic tools available for networked I/O, like Devicenet and Profibus.
In W95 and WXP, the commands to start Telnet are somewhat different.  
95:  START,RUN, "Telnet 192.0.1.1"
XP:  START,RUN, "Telnet95 192.0.1.1"
Once you've Telnetted in, the command prompt looks like this:  ->
Remember that, in VxWorks, capitalization matters.  So you must capitalize the commands as shown.
For DeviceNet on MFC1 cards, type:  dnLookIO or dnShow will show all the nodes currently slaved to the robot, and their I/O size and state.  dnWho will scan the DeviceNet network, and any slave device that is correctly wired to the network and has the correct baud rate set will be discovered and displayed.
For later MFC cards, that use the dn2drv driver (check your IOSYS.INI), the same commands work, but have to be typed in differently:  exec "dnShow" or exec "dnLookIO" or exec "dnWho".  Typing in the quotes is important.
For LPDN cards (2 channels per card), a different driver and a different set of commands is used.
dnsc?Show displays the state of the DN channel.  Replace the ? with the number (1-6) of the channel you're trying to check.
dnsc?ShowDevice ?? bout a specific device on the network.  Replace ?? with the MAC ID you are looking for.
dnsc?GetNodeInfo ?? retrieves the network specs of the slave at the ?? MAC ID.
dnsc?SetConfig ? ?=1 turns Config Mode on, ?=0 turns Config Mode off.  Never used this one myself.
dnsc?SetMacId ?? ?? is supposed to remotely set the MAC ID of devices that don't have hardware settings for it.  Changes the device at the first MAC ID to the second MAC ID.  I've never used it.
dnsc?SetbaudRate ?? xxx  Sets the device at MAC ID ?? to baud rate xxx (125, 250, or 500 kbaud).
dnsc?NetWho will search out and display all slave modules attached to the network (if their baud rate is correct).
Aside from DeviceNet, using iosysShow or exec "iosysShow" will display all the active I/O drivers and their current states.

You should also check the Wago manuals. There were some cases where there were specific rules about the physical order of the slices on the backplane. Not every I/O slice supports pass-through power, and the relationship between the physical order and the logical order is not always 1-to-1.

why not conclude the topic with actual settings that worked for you?