Install and enable

• A working Bicrypto install you can rebuild — see Server requirements
• An admin account that can open Admin → System → Extension Manager (permission access.extension)
• Shell access to the app directory, for the command that finishes the install
• The Chart Engine purchase code, from your MashDiv dashboard
• Enough free RAM to rebuild the frontend (8 GB is comfortable; 4 GB needs swap)

frontend/components/(ext)/chart-engine/
├── index.tsx          the component source
├── dist/index.js      the built bundle — this is what the app actually loads
├── package.json       declares main: ./dist/index.js
└── …                  indicators, drawings, renderers, panels

The package's package.json points main at ./dist/index.js, so editing anything under the addon's source directory changes nothing in the running site until the bundle is rebuilt. A release always ships dist/ pre-built. You only need to rebuild it yourself if you have customised the source:

pnpm build:chart-engine

That runs npm install and tsup inside the addon directory, and must finish before the frontend build, not after.

1. The Chart Engine card — click it to open the product page
2. Its switch stays disabled, reading Activate license first, until the licence is activated

1. Open the Extension Manager. Admin → System → Extension Manager (/admin/system/extension; the screen needs the access.extension permission). Its heading reads Add-ons & Integrations. On the Extensions tab, or by searching for Chart, find the Chart Engine card and click it. Until its licence is activated the card's chip reads Activate and its switch is disabled, with the tooltip Activate license first.

2. Activate the licence. The product page opens with a License Required chip; press Activate License. On the licence screen paste the purchase code from your MashDiv dashboard, optionally an email address for update notifications, and press Activate License. The screen confirms License Activated! and, for this product, lands you on Binary Settings a couple of seconds later — that is the per-screen switch from further down this page, and it is not the next step. Go back to the Chart Engine product page for the install. If the server has no outbound access, the License File tab on the same screen takes the licence certificate downloaded from your MashDiv dashboard instead, placed as license.txt in the lic folder at the project root.

   1. Paste the purchase code here
   2. Activate License — then wait for the redirect
   3. License File — the offline route, for a server with no outbound HTTPS
   4. The Product ID — 61364182 for Chart Engine

The hourly licence heartbeat handles a revoked or expired result for product 61364182 by rewriting settings, not by showing a banner. It sets binarySettings.display.chartType back to TRADINGVIEW, sets spotChartEngine back to TRADINGVIEW, and every process picks the change up immediately.

Traders see TradingView again with no explanation, and an operator who does not know this looks for a chart bug rather than a billing problem. If your charts change provider on their own, check the licence first.

1. Install the release. Back on the Chart Engine product page — now the licensed view, with an Enabled switch in its heading and Overview, Releases and Capabilities tabs — the Overview tab has a release panel. If it offers Install v…, press it; if it says Up to date on a product you have only just licensed, press Check for Updates once, then install whatever it offers. The Releases tab holds the notes for the version you are being offered — read them first.

   Install downloads the release, verifies it and extracts it over the project root, which is how the bundle lands under frontend/components/(ext)/chart-engine. It builds nothing and restarts nothing, so finish it from a shell on the app root:

   pnpm updator

   That single command takes the platform down, checks dependencies, applies the schema and seed data, rebuilds the frontend and starts everything again. It is the whole install for an existing platform. If the panel still says Up to date after the check there is nothing to download; run the command anyway if this frontend has never been built with the bundle present, and move on.

   1. Check for Updates, then Install v… when it is offered
   2. Releases — the notes for the version you are about to install
   3. The Enabled switch — step 4, not yet

2. Confirm the files landed. The build's detection is a file-existence check, so this is the thing that decides everything downstream:

   ls frontend/components/\(ext\)/chart-engine/dist/index.js

3. Rebuild the frontend if you unpacked the files by hand. pnpm updator already does this; a manual extraction does not.

   pnpm build:frontend
   pnpm restart

4. Switch it on. Back on the product page — or on its card in the Extension Manager, usable now that the licence is verified — turn the Enabled switch on. Chart Engine has no admin console or user route of its own, so nothing new appears in the menus; what changes is that the platform now counts it among the active add-ons, and the admin dashboard's product card lists it as Running. It takes effect without a restart. No trading page has switched over yet — that is the per-screen settings below.

Every screen imports the chart from the stub path, which always exists. On an install without Chart Engine the stub answers with a null component, the build succeeds, and each screen falls through to TradingView. That is the designed degradation — you will not see a module-not-found error either way.

1. Confirm the provider still reads Chart Engine - a lapsed licence resets it silently

1. Open a trading page you switched over and confirm the chart's own toolbar is present — timeframe buttons, a chart-type picker, and buttons for indicators, alerts, replay, heatmap and fullscreen. TradingView has none of those in that arrangement.

2. Open the browser console. If you see [ChartSwitcher] Chart Engine addon not installed. Falling back to TradingView., the build did not see the files. Rebuild the frontend.

3. Add an indicator from the toolbar, reload the page, and confirm it comes back. Indicators persist in the browser, so this proves the whole chart is live and not a stub.

4. Watch the last candle move. A price that never changes means the historical fetch worked and the WebSocket did not — see Troubleshooting.