![binary editor use datalogging without saving data binary editor use datalogging without saving data](https://static.listoffreeware.com/wp-content/uploads/bineditor_bin_file_editor_2019-10-16_12-05-46.png)
![binary editor use datalogging without saving data binary editor use datalogging without saving data](http://support.moates.net/wp-content/uploads/2016/02/tprt-adx-wideband1-450x345.png)
- #BINARY EDITOR USE DATALOGGING WITHOUT SAVING DATA UPDATE#
- #BINARY EDITOR USE DATALOGGING WITHOUT SAVING DATA CODE#
The file format can be “customername-date-time” or just “customername-counter”. When saving trace data, save the active cell (time stamp, value in table, X axis value, Y axis value).Ī button in the tool bar will allow the user to save as new file. When the user selects “record trace data”, store trace data in a file. Large updates should be done on a table basis. Single updates can be done a cell at a time. The push should be selected between sending individual cells and large cell rages (the whole table).
#BINARY EDITOR USE DATALOGGING WITHOUT SAVING DATA UPDATE#
User should be able to select between real time updates (sent to the ostrich2 as they are made), and user selected update intervals (pushed when user is done making changes and selects “update” function/button). Be able to push updates in tables to ostrich2. Toggling off trails does not un-highlight the inactive cells. The trails button itself is the toggle for that. “reset trails” resets the display, un-highlighting the inactive cells. It will instead partially change is color back, but allow the user to see what has been active as well as what is active. Trails will not un-highlight the last active cell when a new cell is active. When highlighting active cells is on, “trails” and “reset trails” buttons should be active. (ex: shift-up or shift-down for increment and decrement of the active cell.) In this case, the table manipulation schemes discussed above should also follow. A button should be available to also “follow” the active cell with the cursor. When tracing, the active cell is highlighted. This should be done both when viewing the table numerically as well as graphically. If a window is open and trace is on/active then the currently active cell should be highlighted. Alternatively, the entire data section can be “traced” and logged. The window of watched data in the ostrich2 will be the viewed window of the currently open table. This involves sending a string to the ostrich to tell it you want to trace, and what range of data it should report hits in. (ex: shift-up or shift-down for increment and decrement of the selected value.) The graph should be able to be rotated/oriented, as well as allow for graphical manipulation of the data. The data should be able to be displayed both numerically and graphically. The row and column data should be processed and displayed with the tables. The data is stored in a format which describes if it is 1d or 2d, and the values for the rows/columns. If a descriptor file is loaded, display list of tables as defined by the descriptor file.īe able to send and receive from ostrich. The descriptor file can start as a file with no names/tables and they can be added by the program. Stores list of addresses for tables/constants, the name of each table/constant, conversion factors for raw data to display data, and file length.
#BINARY EDITOR USE DATALOGGING WITHOUT SAVING DATA CODE#
Sample code available with most of the functionality required below, including sample code for tracing/communication. The editor will be used to edit portions of binary files, both graphically and numerically, as well as interface with an emulator (Ostrich2).