Jesus,
I believe that your problem stems from the fact that the StateSpaceModel assumes the functions exist before time 0 and the NDSolve solution explicitly sets the functions to zero. You can see this by plotting the function f2 (which is a delayed version of ff1):

You need to add a time delay to the StateSpaceModel with SystemsModelDelay or by including the delay in the equations:
[{ff1'[tA]== i{g n1a.l2[, t.]}, C{ o8,s .[5}2, {.\9,[ i ] 1.0 }f {1.],f25'}[,t ]{=.=6f,f 1.'9[}t}-;t auu ]=} ,{{{f\f[1M[ut]]1,, \[M]u}], {}s}i;gnal
]},{2 Ff =( f{f{1.[5t}-,t a{u.]7)}},, t{]1.0},
1.}, y{12=.O0u}t}p;u
Resp\o[nCsaep[imt1a,luO1m[t],]{ t=, 0{,{3\ [tSaiug}m]a;],
1}, P{l1o,t [\y[1S,i{gtm,a0],}3} ;ta
1}, P{l1o,t [\y[1S,i{gtm,a0],}3} ;tau}]
Which gives the delayed plot for f2 (which matches the image above).
I am not quite sure why having the tau explicitly in the output of StateSpaceModel automatically adds the SystemsModelDelay while the way you entered it does not. If you look into the documentation maybe you can figure it out and post the reason.
Regards