315-2DP + IM360 + 343-1 Not going to run

Have a strange fault issue.
New system ran for 3 days then cpu faulted out with vague error messages.
Rack make up is.
315-2DP
IM360
343-1
341 Rs232/485
I/O modules modules

In remote rack
IM361
I/O modules.

Started with blank project with all modules at default settings, no program installed to isolate programming errors.
CPU not going to run.
Remove 343-1 Ethernet module. (rehash Harware setup and download)
CPU goes to run.
Replace 343-1.
Remove IM360. (rehash Harware setup and download)
CPU goes to run ok.

As long as only the IM360 OR the 343-1 are installed, no problem.
With both installed, will not go to run.
Fault log along the lines of:
Parameter assignment error.
No relevance for user: SDB 1001
Nothing there to point at which module.
Replaced 343-1 module, still the same.

Have checked all pins on base of cards, checked power supplies etc.

Have tried with just CPU and Ethernet, OK
Have tried with just CPU and IM360, OK,
Try with both and faults.

Export and post the complete diagnostics buffer from the CPU.
Also export and post the diagnostics buffer in the CP343-1.

Yes, I should of done that on way out from site.
Will gather data tomorrow and post.

Attached log.
This is with only in rack and HW setup without errors at default settings.
6ES7 315-2AH14-0AB0 (315-2DP)
6ES7 360-3AA01-0AA0 (IM360 to next rack)
6GK7-343-1CX10-0XE0 (Ethernet comms)

Event 1 of 106: Event ID 16# 49A0
STOP caused by parameter assignment error or unpermissible difference between preset and actual configuration: startup disabled
No relevance for user (SDB no.): 1001
No relevance for user (Z2): 0000 (Z3): 0000
Previous operating mode: STARTUP (warm restart)
Requested operating mode: STOP (internal)
External error, Incoming event
09:37:14:937 am 06/08/11

Event 2 of 106: Event ID 16# 4301
Mode transition from STOP to STARTUP
Startup information:
- Time for time stamp at the last backed up power on
- Single processor operation
Current/last startup type:
- Automatic warm restart after backed up power on
Permissibility of certain startup types:
- Manual warm restart permitted
- Automatic warm restart permitted
Last valid operation or setting of the automatic startup type at power on:
- Automatic warm restart after backed up power on
Previous operating mode: STOP (internal)
Requested operating mode: STARTUP (warm restart)
Incoming event
09:37:14:872 am 06/08/11

Event 3 of 106: Event ID 16# 6547
Parameter assignment error assigning parameters to modules (not on P bus, cancel download)
no relevance for user: SDB number: 1001
DP master affected in rack 0 and slot 4
Station number: 0, slot number: 10
Operating mode: STOP (internal)
Internal error, Incoming event
09:37:14:831 am 06/08/11

Event 3?

Note:
Ran for 3 days without fault.
CPU + 360 = No errors and runs.
CPU + 343 = No errors and runs.
CPU + 360 + 343 = Not going to run.

Event 3 of 106: Event ID 16# 6547
Parameter assignment error assigning parameters to modules (not on P bus, cancel download)
no relevance for user: SDB number: 1001
DP master affected in rack 0 and slot 4
Station number: 0, slot number: 10
Operating mode: STOP (internal)
Internal error, Incoming event
09:37:14:831 am 06/08/11

Click to expand...

There is a problem with reaching the CP342-5.
There is mentioned a DP master in slot 4.
Is the CP343-1 in slot 4 or in slot 10 ?
Do you have any connections configured in NetPro ? In any case recompile in NetPro.
Post a screenshot of your HW config.

Just three slots used.

Repeat question.

JesperMP said:

Do you have any connections configured in NetPro ? In any case recompile in NetPro.

Click to expand...

.............

No connections in net pro.
recompiled in net pro.
Still the same.
Replaced CPU, still the same.
Can only be the IM360 module now,
Possbility the IM360 is not passing the "P Bus" to the ethernet module as Ethernet module not visible from CPU.

Yes that sounds as a plausible reason.

Problem is finally resolved.
After working with Siemens support in Australia, was passed to Siemens Germany who eventually could not find the reason for the Fault.
Last comment from them was that my Step7 was too old.

A new IM360 module was sent after some pleading which solved the issue and CPU happily running again.