I wasn't even aware that it attempted to read the parameter names until I looked at the code. I can't see why it fails, but it certainly does. So, for instance, in callnacamodule.scad you should see that param1 is called 'naca', not 'param1'.
callmodule2d is exactly the same.
Tested in GraphSCAD 1.0.7
Incidentally, I think I now realise why you can chain parameters together. It allows you to know the order of the parameters when you call a module using callmodule. Is this correct?
Just as I created node_variables to declare multiple variables, I find a multiple parameter node useful. I have tried to edit node_param to create node_params but it doesn't work. I can see no reason, but, while the new node appears in GraphSCAD's graphical view, its settings are not recognised by GraphSCAD, even if the only change I make is the filename and matching Node_params classname. I am baffled. It seems the param node must be called node_param, nothing else. Or else there is allowed to be only one node class creating params.
So I have created a new node_param in the zip file below. Just like my node_variables, it allows up to 10 parameters to be declared. As you enter a new parameter's name the input plug for its value appears.
EDIT: I found a backwards-compatibility issue so posted an updated version today. See below.