PowerVision Configuration Studio:
- Support for Sauer Danfoss Communications Adapter
- Data Logger has a new action, OutputNewFile that results in a different file containing data instead of all data in one file.
- PowerVision Configuration Studio is now High DPI unaware so should operate better with newer display technology
- NMEA devices support Manufacturer’s Code address type
- MPC10/MPC20 Simplified UI—The list of gauges available to be displayed may be changed in the MPCxx – Advanced.
- R2 hardware is supported, this includes the PV300r2, PV350r2, PV380r2, MPC-20r2 and CMX110r2
- The Engine Controller App is supported in all Monochrome displays
- Updates and improvements to the MPC-20, MPC-10 and PV380 standard configurations
- In PowerVision 2.8.10459 or later there are two new reserved strings: ECU_ID_PGN_64965 and SW_ID_PGN_65242. In the configuration these strings are part of the J1939 application and the default values can be set to the desired value. To set the default values go to “Programming” tab, open “J1939 Port Manager”, select these variables from the list and enter the desired default value (don’t forget to set the length if the string is longer than 36 – the number of characters + 1 for the null string terminator).
These strings are sent to the requestor via RTS/CTS when a request is message received by the unit and the request message is addressed to the unit and by BAM if the request message is addressed to the global address. If the string defaults have not been set (i.e. string length is 0) the Application will return a NAK.
- BiDirectional fonts, in particular Arabic and Hebrew
- RP1210 support for CAT and Cummins adapters
- Fixed expression editor bug with number formats that use . instead of , (US standard)
- New LCP R2 bootloaders to accommodate larger configurations. Mostly affects MPC10s in the field.
- The length of CAN Standard frame receive messages defined in PowerVision Configuration Studio must match the length of the received messages.