Hi All
I want to visualize internal variables using FreeMASTER Lite 1.1.
I refered this demo but I couldn't get scope graph.
Also my condition, I using evkmimxrt1060_mc_pmsm sample code for FreeMASTER test.
My result looks like this. I can't get the graph.
Has anyone succeeded?
What kind of causes could be think of?
Is more detailed documents available about FreeMASTER Lite?
已解决! 转到解答。
Hi @kenji,
The .fmcfg file is your project file. Considering evkmimxrt1060_mc_pmsm already includes a FreeMASTER project that can be used to obtain FreeMASTER Lite configuration file:
Export FreeMASTER Lite project: File → Export → FreeMASTER Service Configuration
Then start FreeMASTER Lite by double-clicking the generated .fmcfg file or by passing its path as input argument via the command line:
C:\NXP\FreeMASTER 3.1\FreeMASTER Lite>node.exe pmsm_float_enc.pmp.fmcfg
Note: if you want preview / edit project properties open .fmcfg file in a text editor. All properties are described in the Start Guide
Just wanted to add here that we have a training tutorial video about using NodeRED with FreeMASTER (by Iulian) that you might find of use:
Hi @kenji,
To trouble shoot the issue could you open browser console (F12) while your application is running as in your second screenshot and run the following script directly in the console:
pcm.ReadVariable('variable_01').then(val => console.log('Received value ' + val.data)).catch(ex => console.error('Exception occured ' + ex.code + ' : ' + ex.message));
What this snipped does is using the global pcm object that implements the JSON-RPC API to send a variable read request to the NodeJS middleware and receives a reply. It should return variable value on success or log error message on failure:
Also, what version of FreeMASTER Lite are you running ?
> node.exe -v
Unfortunately there's no other documentation on FreeMASTER Lite except the "Start Guide" from the home page.
Hi @kenji,
Sorry if I confused you, let me clarify - I'd like to know which version of FreeMASTER Lite 1.1 you are using (ex: simply "1.1" or "1.1 Update x"). You can check it using 'node.exe' from your FreeMASTER Lite installation folder. This folder is not on the system path so FreeMASTER's "node.exe" is independent and does not interfere with your local node installation.
Latest version is "1.1 Update 2" as shown in the picture above.
Although I would recommend using the latest version, I don't think it to be the issue. Let me know what is the result of the script I posted in my previous reply once you have a chance to test it (I would expect it to give some more insight).
Hi All
By the way, to use FreeMASTER, is need to modify target board side FreeMASTER driver?
I mean, returns the value of the variable want to graph?
I had selected the desired variable in the axf (elf) file, so I thought it wasn't necessary.
Is this wrong?
I am using STM32CubeMonitor. Therefore, I thought that FreeMASTER Lite could be used in the same way, but is it completely different?
No changes are required if the variable information is loaded from the elf file.
Regarding FreeMASTER Lite usage - it can be seen more as a service like application. FreeMASTER main tool is the one you'd use if a native GUI is needed. Although demo example shipped with "Lite" can be used in simple scenarios, in more complex cases it is expected that users develop their own GUI (web or native) and use FreeMASTER Lite as a back-end service (API) to interact with the board.
Could you tell which functionalities are you missing in FreeMASTER / FreeMASTER Lite tools ?
Thanks,
Iulian
Hi @kenji,
The .fmcfg file is your project file. Considering evkmimxrt1060_mc_pmsm already includes a FreeMASTER project that can be used to obtain FreeMASTER Lite configuration file:
Export FreeMASTER Lite project: File → Export → FreeMASTER Service Configuration
Then start FreeMASTER Lite by double-clicking the generated .fmcfg file or by passing its path as input argument via the command line:
C:\NXP\FreeMASTER 3.1\FreeMASTER Lite>node.exe pmsm_float_enc.pmp.fmcfg
Note: if you want preview / edit project properties open .fmcfg file in a text editor. All properties are described in the Start Guide