Some applications of CANopen (CANopen Lift for example) use a lot of PDOs for the whole CAN network (hundreds). For example a car drive unit (basically an inverter designed specifically for CANopen Lift) can have just two RPDOs and two TPDOs, but their indexes are 260, 261, 262 and 263. If you want to have just these PDOs in libedssharp, then you basically have to add 260 PDOs, then delete all but the last two, and do this twice (once for TPDOs, then for RPDOs). This is ALOT of clicking, very boring... A simpler solution would be to either have PDO slot numbers editable (add two, change 1 and 2 to 260 and 261) or introduce a dialog for adding new PDOs, which would allow you to select the slot number instead of using the first free one - like the dialog for adding OD entries, where you can select the index of the new object.
Or at least the ability to mass-delete more than one PDO (like you can delete multiple selected OD entries) would also be a solution, however not such a good one as the two above.
Some applications of CANopen (CANopen Lift for example) use a lot of PDOs for the whole CAN network (hundreds). For example a car drive unit (basically an inverter designed specifically for CANopen Lift) can have just two RPDOs and two TPDOs, but their indexes are 260, 261, 262 and 263. If you want to have just these PDOs in libedssharp, then you basically have to add 260 PDOs, then delete all but the last two, and do this twice (once for TPDOs, then for RPDOs). This is A LOT of clicking, very boring... A simpler solution would be to either have PDO slot numbers editable (add two, change 1 and 2 to 260 and 261) or introduce a dialog for adding new PDOs, which would allow you to select the slot number instead of using the first free one - like the dialog for adding OD entries, where you can select the index of the new object.
Or at least the ability to mass-delete more than one PDO (like you can delete multiple selected OD entries) would also be a solution, however not such a good one as the two above.