Hi I have been experiencing some trouble with using DLS with a Simulink generated application. My model is composed by 3 complex subsystems. I have not been able to narrow down the source of the issue in the subsystems but I have managed to see that commenting out one of the subsystems the model works with DLS, so it is a problem of the model and not DLS (or at least that is what I think).
The model works fine in both cases (I can visualize data and change parameters with TestManager). The only problem is using DLS. I have extracted the dlsd log for both tests (see below) I have the impression that there is an issue with a wrongly named block but I have checked and they look fine to me. Do you have any idea what can be the issue? ########################################################################################## ## DLSD log with model and commented subsystem### ########################################################################################## Oct 09 16:55:10 linux-nvm6 dlsd_mother[13406]: INFO: ----- DLS Mother process started ----- Oct 09 16:55:10 linux-nvm6 dlsd_mother[13406]: INFO: dlsd 1.4.0-rc2 revision 51dc3443178a Oct 09 16:55:10 linux-nvm6 dlsd_mother[13406]: INFO: Using dir "/home/cmg_demo/dls_data/" Oct 09 16:55:10 linux-nvm6 dlsd_mother[13406]: INFO: Bound to :::53584. Oct 09 16:55:10 linux-nvm6 dlsd_mother[13406]: INFO: Starting process for job (118) CMGS_Torque_test_LC. Oct 09 16:55:10 linux-nvm6 dlsd_mother[13406]: INFO: Locking connection threads... Oct 09 16:55:10 linux-nvm6 dlsd_mother[13406]: INFO: Threads locked. Oct 09 16:55:10 linux-nvm6 dlsd_mother[13406]: INFO: Unlocking connection threads... Oct 09 16:55:10 linux-nvm6 dlsd_mother[13406]: INFO: Started process with PID 13407 Oct 09 16:55:10 linux-nvm6 dlsd_mother[13407]: INFO: Unlocking connection threads... Oct 09 16:55:10 linux-nvm6 dlsd_logger[13407]: INFO: Process started for job 118! Oct 09 16:55:10 linux-nvm6 dlsd_logger[13407]: INFO: Message file ./plainmessages.xml not found. Oct 09 16:55:10 linux-nvm6 dlsd_logger[13407]: INFO: Connected to "127.0.0.1:2345". Oct 09 16:55:10 linux-nvm6 dlsd_logger[13407]: INFO: PdCom: MSR Protocol handler recognises the protocol. Oct 09 16:55:10 linux-nvm6 dlsd_logger[13407]: INFO: PdCom: Waiting for <connected> tag. Oct 09 16:55:10 linux-nvm6 dlsd_logger[13407]: INFO: PdCom: Autodetected MSR Protocol. Oct 09 16:55:10 linux-nvm6 dlsd_logger[13407]: INFO: PdCom: <connected> tag arrived. Oct 09 16:55:10 linux-nvm6 dlsd_logger[13407]: INFO: PdCom: Logging in as "root@linux-nvm6" Oct 09 16:55:10 linux-nvm6 dlsd_logger[13407]: INFO: PdCom: Requesting parameter list. Oct 09 16:55:10 linux-nvm6 dlsd_logger[13407]: INFO: PdCom: Found 142 parameters. Oct 09 16:55:10 linux-nvm6 dlsd_logger[13407]: INFO: PdCom: Requesting channel list. Oct 09 16:55:10 linux-nvm6 dlsd_logger[13407]: INFO: PdCom: Found 339 channels. Oct 09 16:55:10 linux-nvm6 dlsd_logger[13407]: INFO: PdCom: Protocol initialisation finished. Oct 09 16:55:10 linux-nvm6 dlsd_logger[13407]: INFO: Start logging. Oct 09 16:55:10 linux-nvm6 dlsd_logger[13407]: INFO: ADDED 12 channels Oct 09 16:55:10 linux-nvm6 dlsd_logger[13407]: INFO: Receiving data. ########################################################################################## ########################################################################################## ## Log with complete model### ########################################################################################## Oct 09 17:30:25 linux-nvm6 dlsd_mother[14052]: INFO: ----- DLS Mother process started ----- Oct 09 17:30:25 linux-nvm6 dlsd_mother[14052]: INFO: dlsd 1.4.0-rc2 revision 51dc3443178a Oct 09 17:30:25 linux-nvm6 dlsd_mother[14052]: INFO: Using dir "/home/cmg_demo/dls_data/" Oct 09 17:30:25 linux-nvm6 dlsd_mother[14052]: INFO: Bound to :::53584. Oct 09 17:30:25 linux-nvm6 dlsd_mother[14052]: INFO: Starting process for job (117) CMGS_Torque_test_DLS. Oct 09 17:30:25 linux-nvm6 dlsd_mother[14052]: INFO: Locking connection threads... Oct 09 17:30:25 linux-nvm6 dlsd_mother[14052]: INFO: Threads locked. Oct 09 17:30:25 linux-nvm6 dlsd_mother[14052]: INFO: Unlocking connection threads... Oct 09 17:30:25 linux-nvm6 dlsd_mother[14052]: INFO: Started process with PID 14053 Oct 09 17:30:25 linux-nvm6 dlsd_mother[14053]: INFO: Unlocking connection threads... Oct 09 17:30:25 linux-nvm6 dlsd_logger[14053]: INFO: Process started for job 117! Oct 09 17:30:25 linux-nvm6 dlsd_logger[14053]: INFO: Message file ./plainmessages.xml not found. Oct 09 17:30:25 linux-nvm6 dlsd_logger[14053]: INFO: Connected to "127.0.0.1:2345". Oct 09 17:30:25 linux-nvm6 dlsd_logger[14053]: INFO: PdCom: MSR Protocol handler recognises the protocol. Oct 09 17:30:25 linux-nvm6 dlsd_logger[14053]: INFO: PdCom: Waiting for <connected> tag. Oct 09 17:30:25 linux-nvm6 dlsd_logger[14053]: INFO: PdCom: Autodetected MSR Protocol. Oct 09 17:30:25 linux-nvm6 dlsd_logger[14053]: INFO: PdCom: <connected> tag arrived. Oct 09 17:30:25 linux-nvm6 dlsd_logger[14053]: INFO: PdCom: Logging in as "root@linux-nvm6" Oct 09 17:30:25 linux-nvm6 dlsd_logger[14053]: INFO: PdCom: Requesting parameter list. Oct 09 17:30:25 linux-nvm6 dlsd_logger[14053]: INFO: PdCom: Found 217 parameters. Oct 09 17:30:25 linux-nvm6 dlsd_logger[14053]: INFO: PdCom: Requesting channel list. Oct 09 17:30:25 linux-nvm6 dlsd_logger[14053]: [4.1K blob data] Oct 09 17:30:25 linux-nvm6 dlsd_logger[14053]: INFO: Finishing job... Oct 09 17:30:25 linux-nvm6 dlsd_logger[14053]: INFO: Job finished without errors. Oct 09 17:30:25 linux-nvm6 dlsd_logger[14053]: INFO: ----- Logging process finished. Exiting with ERROR! (Code -2) ----- Oct 09 17:30:25 linux-nvm6 dlsd_mother[14052]: INFO: Process for job (117) CMGS_Torque_test_DLS with PID 14053 exited with code -2. Restarting in 30 s. ####################################################################################### Thank you Daniel -- Etherlab-users mailing list Etherlab-users@etherlab.org http://lists.etherlab.org/cgi-bin/mailman/listinfo/etherlab-users
