If you enable the preferences panel (Views->View Preferences) you will have a Window on the right that will give a Microsoft timestamp for each capture to 1 second accuracy.

The timestamp Gerry has mentioned will be in micro seconds if the scope supports the functionality.

Can you see the other end of the broken white wire on the PCB ? Looks like there may be some glue holding it there.

Please email support@picotech.com for assistance with this

Depending upon the scope you have and the actual trigger conditions for each channel you may wish to consider using an advanced logic trigger and set up this up as an OR trigger so that either one will work.

Creating a custom application to read the data from Channel B to identify the 0/360 degree pulse indication and then doing calculations on the Channel A data to identify the flat section and it's relative position is relatively straightforward once you have collected the data from the scope. To help...

You may be able to use these for generic testing, but for a more detailed discussion on suitability please email support@picotech.com and one of the team will respond.

I would suggest emailing the support team directly at support@picotech.com with all the information, it may be a hardware/powering issue but they will be able to discuss this with you.

If possible try the unit on a Windows PC if you have access to one as this may provide additional information.

By default only Channel A is turned on, range set to Auto and coupling DC, check the toolbar and set Channel B to Auto or a specific range and it will appear on the trace.

For a starting point select Views->View Properties and you will have a panel on the right that shows how the scope is set up. The 2GS at the top is the number of samples you would like to collect across the screen, not what you actually get. The panel will show this and should help explain why it wi...

When streaming the scopes memory acts as a Fifo to help with the flow of data over the USB bus, this data then goes into the driver buffer defined by max_samples, this is a circular buffer and is over written but when you stop streaming either manually or via auto stop it will then have the last max...

The streaming buffer is a circular buffer defined by the value of max_samples this can be quite large (PC dependent) and is used to buffer data in the driver. The overview buffer is the one used to read data back to the application and the documentation recommends using 15000 to start with and then ...

It is possibly the fwrite that is causing the problem particularly if you are calling it on each loop, you may need to loop a few times to collect a bigger chunk of data before writing to the file. You may also need to consider the size of the buffer you setup in the driver as this could overflow as...

Which version of PicoScope 6 software are you using ? (Help->About)
What O/S are you using ?

If you get the Player when you try to open the Recorder it means that the Recorder is still running but has minimized to the system tray in the bottom right corner, check here for the blue PL logo.

The TA133 is a simple passive high bandwidth x10 probe so all you need to do is select x10 in the probe dropdown.