Hi Mehmet,
Sure, using the scaffold file sounds reasonable to me. Depending on whether your downstream analysis tools can tolerate 'N's, you might want to split the scaffolds into scaftigs (by breaking them where sequences of N's occur). You can do that with:
$ abyss-fatoagp -f scaftigs.fa scaffolds.fa > /dev/null
FYI, there is a list of assembly parameters in the README.md:
https://github.com/bcgsc/abyss#assembly-parameters. 'k' is probably the most important parameter. It might be worth setting the minimum coverage threshold ('c') and minimum erosion coverage ('e') to zero and seeing if that helps, i.e.
$ abyss-pe c=0 e=0 <... your other params ...>
If you have overlapping paired-end reads, you can merge them with abyss-mergepairs. (Assembling with merged reads generally allows you to use a larger k and improves contiguity.)
Hope that helps,
- Ben