Database to network errors

Just finished a job where we set everything up on the laptop before going to site. This raised a couple of problems/errors that i'm not sure are mine or inherent within Toolkit.

We had a couple of items with correct serial numbers but wrong product types - my fault. Problem is i could not see a way of correct the product type within the database after entry ? - This caused the database and physical items not to match with meant they had to be re-entered on site - is this normal, or did i miss something ??

When i first did network discovery and unravel, it took about 3 attempts and to restart toolkit before it got it right - even though it tied the items to the database it wouldnt upload to them (all Saturn switches). Biggest problem was that none of the tags were copied from database to network - and what ever i did i couldnt make this work.

Any suggestions appreciated.



Dean.

 

Hi Dean,

This is kind of both your fault and Toolkits fault. Toolkit lacks the ability to change Unit Types and retain core programming information. A good example of where this would be useful would be where Neo's were set up in the database and fully programmed then a decision was made to go with Saturn.. big similarities in programming but no way in Toolkit to achieve it, you'd need to delete all the Neo's and reprogram with Saturn. I guess you've got another example.

At the moment that functionality is low on the priority list.

Which version of Toolkit was this with?

Did you get error messages?

Tags aren't saved to the Network, only the "Partname" is saved to the unit. The Tag is a 32 character string that is stored in the database.. the Partname is an 8 character string that IS saved to the Unit.







Dean.