Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

How can I avoid doing a build each time I log into a data taking machine when I haven changed any of the front end software?

0
Posted

How can I avoid doing a build each time I log into a data taking machine when I haven changed any of the front end software?

0

Most of you rarely if ever modify the user*.h files that control the front end computer. Yet, whenever you sit down at a workstation to begin a run, you have to do a build to recompile the front end code. To address this, there are two new commands: a. savefront — This will first ask you for a filename without an extension. It will then add a .hex extension to that name and store the front end code under that filename in your data directory. This is the code that resulted from your last build operation. The file is usually less than 2000 blocks in size, so doesn’t take up that much space. b. loadfront — This performs the reverse operation. It asks for the filename (again without extension) that you used with savefront then copies that file to the proper download directory on the workstation. It can then be loaded into the front-end by a restart cold or by pushing the red restart button, as usual. Typically, you would run savefront once after doing a build, then use loadfront at the s

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.