Create your own Device Drivers with Neets Device Editor.
DOWNLOAD THE LATEST RELEASE BELOW IN THE SOFTWARE BAR ↓
Easy and intuitive software for creating and managing Device Drivers used by Neets Control Systems. The Device Drivers is available in the Device Driver Library in Neets Project Designer software and can be drag and dropped to your project at hand.
We develop our own Device Drivers and continue to expand the existing library. The device drivers are bi-directional and physically tested and hold the label "Neets Certified."
Three ways of communication IR, RS-232/ RS-485 and LAN
Three input formats ASCII, HEX or Decimal when entering commands in RS-232/ RS-485 or LAN
Device settings to help identify your devices with name, type, manufacturer etc.
Connection diagram for a Device Driver can be attached
Bi-directional communication makes the user experience complete, inputs on the generic remote will be detected by our control system and everything synchronizes
Help menu available to guide you through the software
LSB and MSB naming Fix in Feedback Sequence
Fixed Device driver with version 2.20 and below gives an error
Added Telnet Protocol Option
Added option to define wrong string for telnet passwords
Added 'model numbers' to device settings. Can be used to specify products that are using identical commands but with slightly different timing
Added option to duplicate sequences
Fixed bug where a non-certified device would remain certified even after it had been edited
New device version (2.30).
Support for PJ Link.
Support for leading zeros when doing increment/decrement volume control.
Possibility to define command end character.
Support for leading '+' sign on level sequences.
Support for one’s and two's compliment checksum.
Possible to control increment/decrement volume with two count values.
Now possible to control levels that has range from -100.000 to 100.000.
upport different types of linked items in a feedback item.
Baud rate drop down fix.
Issue with feedback.
It was not possible to select min and max values for a feedback sequence of type 'Number range' when 'Binary' was selected as value type.
If the first byte of a command in a feedback sequence was '00' the field was empty instead of being interpreted as the special character NUL. It didn't have any effect on the actual command.
Added tooltips in Device settings to explain the functions.
Right click menu in the sequence list is updated.
In a special case a custom byte delay was enabled, but it had no value, resulting in an error.
If a device in version 2.20 containing a feedback sequence with a reply mapped to a sequence that was not of type power or source, the following feedback sequences was not converted when changing device version to 2.10.
When adding a feedback sequence or feedback reply, focus was not in the command field.
Renaming and deleting a feedback reply was only possible once, until you manually selected a new reply.
Copy and paste in CommandFields fixed.
Bytes in CommandFields not saved, in certain conditions.
The count byte was cleared when changing level type. Now it only clears if command is changed.
It was only possible to paste in a command when it was empty.
When adding text inside a collection of count bytes, the added text was not marked as count bytes.
When pasting text that resulted in exceeding the command fields maximum length, multiple text boxes was shown.
New device version (2.20).
Support for new feedback setup.
Mute sequence is split into two Control mute sequences (on/off).
Header/Footer is removed.
Application color scheme is always light, and cannot be changed.
Minor text changes.
Minor visual changes.
When converting a device back in version, some of the new versions functionality was not added.
When saving in a write protected location a non-descriptive error message was shown.
If having an in/decrement level sequence with count bytes selected the selection was reset when entering the sequence.
It was not possible to create a new manufacturer.
It is now possible to type in, and see, more than one path for devices in the settings dialog. The Device Editor will only use the first path entered.
When saving a plugin as a new file when it was opened from Edit Device in the Project Editor, the username and password is now reset.
When changing the checksum for an in/decrement level sequence, the current type in the checksum popup was not set. And when finishing the checksum selection the caption was not properly set.
When a command is using more than two lines in a sequence and scrolling to the bottom and moving to another sequence, the scrollbar wasn’t reset, so it was possible to scroll beyond the characters.
In wizard mode, when moving back from RS232 sequences to the first page and forward again an error would occur.
In wizard mode, when adding extra IR sequences, the sequences were not added to the device although they were learned from the remote control.
Copy/paste was not working in general text areas.
When saving a device from the commission section it was only possible to press the same button one time in a row.
When resizing the window when a command was shown, an error could occur on fast computers.
The design tab now opens by default when editing commands.
Some help files are updated.
It is no longer possible to make a new 'Type' of device.
When using wizard mode to make a 'Plasma screen', 'Receiver' or 'Scaler' device, some information in the device was missing which could lead to an error.
The maximum values for several settings in the sequences can now be higher if device is only supported by the newer control systems (device version > 1.90). And some of the minimum values can now be 0.
Sometimes the last pair in an IR command was not shown correctly even though it was correct in the device.
When copying a command and inserting instead of the selected, it looked like the selected was removed, but it was still in the device so when showing the sequence the next time the previous selected text was still there.
When testing RS232 commands, the answer could be incorrect. If having a reply containing bytes above standard ASCII values '7F' the byte was shown as '?' ('3F').
When having a small screen resolution, scrollbars didn't appear which makes it impossible to see all the content in some settings.
When RS232/LAN settings was shown and is ready to write in the header/footer and then create a new sequence it jumps to the correct settings, but when start writing, the entered text is written in the ribbon. Now it has focus in the first command.
In Windows XP, when saving a device and the name of the device contains invalid characters an error could occur. When learning IR codes that is RC5 format the data was not inserted in the field.
Tooltips is added in the menu, to make it easier to preview all the functions.
Shortcuts for inserting CR and LF are added. Press Ctrl+Enter for CR when in a text field and Shift+Enter for LF.
When testing in/decrement sequences you are now informed that the checksum is not calculated before sending.
The repeat time for an IR level down command wasn’t saved.
The repeat time for an RS232/RS485/LAN level down command wasn’t saved when continuous.
The repeat time for an RS232/RS485/LAN level command wasn’t saved when in/decrement.
If you select some text in a command field and paste some other, it looks like the selected text is removed, but if you go to another sequence and back again, the old text and the new text is there. If you delete the text first it worked.
Optimization on the warnings shown when making in/decrement level sequences.
New device version (2.00)
Support for byte delay.
Labeling and help files changed from RS232 to RS232/RS485.
If you follow these steps a device file could be overwritten. 1) Open an existing device. 2) Go to RS232. 3) Create a new device. 4) Youre asked if you want to save the changes, select no. 5) Create a new source in RS232.
6) Save the device, then the previous was overwritten. An error occurred when IR learning the 2. Command for a source sequence.
You can now see version history in the Device Editor
It is now possible to right click on a sequence and rename or delete it.
When making a new device from a template, it was not possible to learn IR due to an error in the template.
If a sequence is selected, and you collapse the parent node, and right click on it and create a new sequence an error occurred
When changing/deleting a character in an inc/decrement command that has a volume count defined, the cursor moves to the first character that is not a part of the header.
If you created an inc/decrement sequence with the settings String and Decimal, and used a negative count value, you would see a warning that the count byte was not valid.
The manufacturer list and type list was sometimes empty. It is now checked.
It was not possible to use special characters (e.g. 16:9, 4:3) in the name of a sequence.
It was not possible to click Cancel when making a new sequence.
If the value of a delay was empty in a device, it could cause an error
Support for multiple in/decrement sequences.
In a user approved device, you could be prompted if the device is still user approved several times.
You cannot set the TCP port to more than 9999
If creating a sequence with the same name as one already existing you would see an error when changing between the sequences.
If selecting a hexadecimal count format for an in/decrement sequence it would write a wrong value to the device file, and causing it not to work properly in the Project Editor when using the sequence and uploading the project.
The port number for LAN settings was not saved
If a name in a device is undefined and the type or manufacturer is not in the list, the value is set to undefined
If version revision was not present in the device (som older devices), it would cause an error when opening/editing from the Neets Project Editor
If using a different language than Danish, an error could occur
If illegal characters in COM port name an error could occur
If the PC has invalid COM ports none of them was shown
When changing to another sequence or changing the input format the menu switched to another menu item
If the type on a device was empty an error could occur in the Project Editor. The type will now never be empty
The checksum for a volume with In/Decrement type wasnt working when opening an existing device
Scrollbars in the command field was sometimes not visible
When pasting regular text in an IR command field the input was disabled
When learning a long IR code all of the code was not saved. It was caused by the command field only supporting up to 250 fields
In some cases it was not possible to load the ManufacturerList. When the file not was loaded, a error on the first page in the Wizard mode occurred.
It was not to change the ManufacturerList and TypeList path from settings
Some RS232 command was not editable when the device was loaded through the Project Editor.