Thanks, much appreciated for that, it helped to track everything down and I've just released v0.4.3 which should (hopefully) stop this error happening again.
In short, the error occurs when trying to set a trains schedule to one thats effectively empty -- this can happen for example when placing a train down from the players inventory, immediately boarding it and then pressing ALT+P, for various reasons that actually triggers tnfp to save and restore the trains schedule, which happens to be blank.
Now in versions 0.17.58 and earlier, it was valid to set a trains schedule to an empty object/hash (i.e. train.schedule = {}), but in 0.17.59 and above that now triggers this error and the schedule needs to be explicitly set to "nil" instead (or at least, not set to an empty hash ;-) ). It's unclear exactly why this changed, but I guess its just part of the fun of experimental releases...
Cheers, Lee H.