Примечания к выпуску NovaLCT V5.4.4.6 и история предыдущих версий.

Novastar Загрузка программного обеспечения NovaLCT V5.4.4.6

NovaLCT V5.4.4.6 is the 8 July 2022 maintenance release in this archive. Its documented change addresses a fault-diagnosis failure when using an overseas node. This distinction matters when deciding whether to change software on an otherwise working legacy screen.

1. Locate the V5.4.4.6 package

Прежняя ссылка на ZIP-архив возвращает ошибку 404. Чтобы запросить NovaLCT V5.4.4.6, Свяжитесь с нами EagerLED with the version number, controller model and receiving-card model. Check the package version with your supplier before installing it. If the service laptop already has a working copy, record its complete version number before making changes.

2. Compare the historical releases

Selected releases leading up to V5.4.4.6
ReleaseDate in archived notesChange relevant to service work
V5.4.4.68 июля 2022Fix for failed fault diagnosis on an overseas node
V5.4.4.530 июня 2022ScreenBoss fault diagnosis and additional panel ID ordering options
V5.4.4.325 апреля 2022Restore a configuration backed up from a mobile device
V5.4.4.114 марта 2022Maintenance fixes
V5.4.414 января 2022Additional driver chips and ScreenBoss configuration restore
V5.4.315 октября 2021Multiple sending-card redundancy settings and additional driver-chip support

The dates refer to the archived release notes. In particular, the fault-diagnosis feature described in V5.4.4.5 and the overseas-node repair in V5.4.4.6 are separate changes.

3. Verify the legacy installation

The V5.4.4.6 notes list MCTRL300, MCTRL600, MCTRL660 and MCTRL4K among the synchronous controllers, and name VX1000 and several Taurus players in their respective equipment lists. Check the full model, firmware and module driver before treating a listed family as a match.

The historical operating-system note specifies Windows 7 or later. For a present-day service PC, verify the installer and driver against the actual Windows environment. Back up the screen map and parameter files before testing the connection.

4. Часто задаваемые вопросы

(1) What did V5.4.4.6 fix compared with V5.4.4.5?

The July note identifies a fault-diagnosis failure on an overseas node. It lists no new features for that maintenance release.

(2) Why might a receiving card return unexpected parameters?

The archive warns that readback may be unreliable when receiving-card firmware lacks support for the module’s driver chip. Identify the card, chip and supported firmware before using those values.

(3) Should I change a working installation to V5.4.4.6 for routine playback?

Check whether the documented fix affects the installation. For a maintenance visit, record the working configuration and test the required service task before deciding on a software change.

5. Заключение

Keep V5.4.4.6 tied to its dated repair note and the hardware on the service record. That makes it easier to distinguish a software diagnosis problem from a cabinet configuration or driver-chip mismatch.

Оставьте комментарий