Forum user Nick Ireland had an issue that threw the same error code.
In that particular instance, it turned out to be the data rate setting.
Ref: