1

Topic: PASHA Control created w/1.4 does not function when deployed w/1.2.6

In our office, we currently use v1.4 (soon 1.4.3...;o). We recently modified a file using 1.4 for a client that was originally created in 1.2.6. Obviously, after modifying we emulated to confirm that we could indeed compile.  When we returned the file to the client, they deployed using 1.2.6. They report and we confirmed that when they deploy they are not able to change the serial port selection to choose the RS232 port (COM2)! This rendered the file unusable.

We have taken the file back, and rerun the properties on the NioNode Device, re-compiled and re-emulated under 1.2.6 prior to returning to the client, and it appears to operate properly.

I know that in an ideal world, all installations would use the latest versions of software, but that's not always feasible. In any case...this is an FYI so others may  not trip over it....

Thanks!

Dave

2

Re: PASHA Control created w/1.4 does not function when deployed w/1.2.6

Yes, this is correct.

As long as one ALWAYS uses the same version of software on their computer as the version of firmware on the NION this should not happen. If you are flipping between versions, be certain to "Update all out of date devices". This would have mitigated the issue you experienced in changing between 1.4.X and 1.2.6.

The reason this failure happened was because we changed the labeling on the serial ports to a more sensible naming convention. Since the labels did not match in the two different versions, the control would not function. Had you (or the client) done the "Update all out of date devices" function, it would have updated the control to the correct labeling, provided they were running the same software on their computer that was running on the NION.

Thanks for pointing this out for everyone!

Josh Millward
Burnt Orange Studios

3

Re: PASHA Control created w/1.4 does not function when deployed w/1.2.6

Thanks Josh!

The funny thing about this is that there were no messages about "Update all out of date devices" either at the client site or in our offices.

When we emulated the file that was created in 1.2.6 using 1.4 it took it upon itself to update the NioNode device, without warning. Likewise, when we took the file that was now 1.4 compatible and re-compiled using 1.2.6 it downgraded the NioNode automatically, again without notification.

The lesson is, make sure you know your target version, and don't assume that NWare will warn you.

Thanks!

Dave