Andreas

Thanks for the clarification. The dimensions as parameters (in inch!) are vital. Without a correct width and height, the command does nothing. I noticed LED-indicators do not print and Combo-boxes disapear and become a black box in the top left corner. Otherwise it seems to work. This functionality will probably be sufficent for me. page.printPDF seems to be around for some time and as it is the only solution, that works for report creation, I think it deserves to be documented.

Thanks for the response. Unfortunately page.capture() only works with Pro and Developer licence. I also could not find any documentation about page.printpdf(). It is also not part of the command suggestions (see picture). When I try to use it anyway, nothing happens. Not even an error occurs. I also tried putting some parameters with no effect.

I have the same or at least closely related problem (Version 19.1, Windows 10). I cannot say if previous versions had this issue as I have not used printing feature previously. More Detail: I tried printing a big, complex page of an exisiting Project. In the preview there is already a blank page. Zooming in and out does not change that. when I print from the preview page, I receive a blank result. Interesting note: when exiting the preview, in the Live DAQFactory view the page content becomes blank as well. I have to switch pages back and forth for it to become visible again. When I print directly, without preview, I receive an almost blank page: there is a very small, empty dropdown (Combo Box) component in the top left corner. I created a new document with just two components: a print-button and a plain text. In the preview, there is at first only the button visible. When I zoom in once, the text also becomes visible. When I zoom in again (maximum zoom), the text vanishes again. Either way, the actual print remains blank - also when I print directly. I added a Combo Box. Then I have the identical behaviour as with the big project: When I print directly, there is a small combo box in the top left corner. I also tried adding a 2D-Graph: in the preview, the Axis labeling becomes all messed up around the place. There appears to be something seriously broken.

Hello, I finally had some time testing that logging-code. It does work, basically. I added some features (like start/stop from page, choosing file destination, adjust scands per s, ... from the page). However, there are still some points/issues: - IMO, this st += scansPerRead / scanRate" line should be after the logging part. otherwise the time stamps of logged data and channel data will always be "scansPerRead/scanRate" apart. However, when only logged data and its timedeltas are relevant, this does not matter. - the whole thing is still quite unhandy. Everything must be (hard-)coded. e.g. there is again no conversion before logging. One must code it or open the data and add a conversion afterwards. A native streaming and respective logging support would be much appreciated. - I have not managed to use "file.writedelim()"-command to write the time column with all six decimals (double precision, µs). The time format of variables up to this point (systime(), st-Variable and data[][0]-Array) is double precision, having six decimals. In the resulting logfile, however, there are always only 3 decimals (ms). With only 3 decimals, there are 10 identical times for ten data points, when logging with full speed (10000 scans/s). Porbably, this is just a formatting-issue but I could not find anything in the UsersGuide.

Hello, I found the problem with "logging" myself. It was not the alignment threshold or the logging-functionality per se (I tried different values before). The problem actually lies with the way, the stream data is read and put into the channel: In a "while"-loop, every 1/10th second, an array of data (for 10000 values per second, the array is 1000values big) is read from the LJ-Stream and put to the channel, using "Channelname.AddValue(Array)"-Method. It appers, that the Logging-functionality only writes/logs a single value, when data is written to the channel-history. So in this case only every 1/10th second, a single value is written to the log. to prove this, I tried a loop every 1/100th second and received a maximum of 100 values per second in the log. I based this stream-reading method on the application example from the users guide (chapter 17.9). It appers to me, that the logging-functionality is incompatible with this streaming-method and putting arrays in the channel. At least I have not managed to write more than one value per "logging-event". I managed to write a sequence, with a loop, which uses an Export-Set to write data (10000 points) every second. It works basically. However, with this I get "alignment"-issues (time-gaps) as the loop for the Export-Set is not exactly 1second long. So the sequence with the export-set loop is a step forward, but I am still looking for a way to continously (without gaps) log about 10000 values per second from my Labjack T7-stream to a ASCII-file.

Hello, I'm using a Labjack T7 in stream mode to collect data from analogue inputs. Streaming works fine using sequences and I receive 10000 data points per second in my "Test-"Channels with no problems. I can see this data in the channel tables, channel graph and page graph. There are really 10000 points per second. However, I am unable to log more than exacly (!) 10 data points per second using a logging set in ASCII-Method. The UsersGuide in chapter 9.2 says, 10000 points per second should be acheivable with this method. It doesn't matter how many channels I try to log or what other settings I use (Mode, Time Format, Interval, Threshold,...). 10 points per second is the maximum. As the logged data points are equally spaced at 0.1 seconds, I suspect an artificial limit somewhere.