Search the Community
Showing results for tags 'waveforms3'.
Found 4 results
Using the analog discovery with waveforms 3, it seems like the UART interpreter is telling me things that are incorrect. I could be completely wrong, and maybe I don't know enough about UART framing to tell, but if that's the case let me know, The data stream I am sending is arranged like so: [FF pad byte] - [data(lower 6 + 2 tag bits)] - [FF pad byte] - [data(upper 6 + 2 tag bits)] - [FF pad byte] - [checksum] To get a much better look at the bits, go to: http://s306.photobucket.com/user/Krb686/media/waveforms_uart_bug.png.html?o=0. Then hover over the image at my photobucket, and click the zoom icon that appears in the top right. As you can see, those bits appear to be there, correctly, but the interpreter doesn't seem to think so. Byte 1, the first FF, is recognized successfully. Byte 2, the first data + tag bits, is marked as "Framing Error". From what I understand, framing errors occur when the STOP bit does not occur at the correct time. Clearly however, the STOP is bit is there, as the signal is HIGH where STOP is marked. Byte 3, the second FF, is recognized successfully. Byte 4, the second set of data + tag bits, is marked as "BREAK". What this means, I have no clue. The line drops low after the last FF so why isn't this recognized as a new start bit? I also believe that set of bits is correct. Byte 5, the last FF, is correct. Byte 6, the checksum, is also marked as "BREAK", yet appears to correctly be there. Also, this interpretation is heavily dependent on my time scale. The above image is at 0.01ms/div (20 MHz) At 0.02ms/div (10 MHz), the "BREAK"s go away, and are replaced with framing errors (still, seemingly incorrectly). And you can CLEARLY see that bit #7 in the second packet is a 1, yet the interpreter tells me the value is "h0" Finally 0.05ms/div(4MHz) All the errors are gone, and the 2nd packet is supposedly an h80
Hi Everyone! I'm attempting use Waveforms with Ubuntu 15.10. I've installed Adept runtime, and Waveforms 2015 through .debs. Waveforms on start only displays a blackscreen and the terminal reports the following error: waveforms: pthread_mutex_unlock.c:87: __pthread_mutex_unlock_usercnt: Assertion `type == PTHREAD_MUTEX_ERRORCHECK_NP' failed. Aborted (core dumped) If I attempt the cli I receive the following: Set range and print the actual obtained range: dwfcmd connect analogio channel=1 range=5V range dwfcmd: pthread_mutex_unlock.c:87: __pthread_mutex_unlock_usercnt: Assertion `type == PTHREAD_MUTEX_ERRORCHECK_NP' failed. Aborted (core dumped) Anyone have any ideas? I attempted this with the 32-bit and 64-bin installers. I am using a 64-bit system. P.S. On the main diligent site the link to the form at the bottom of the page is broken.
Hello, I have the Waveforms3 beta running on my MacBook Pro almost perfectly fine. I have full functionality of the oscilloscope, wavegen, etc. However, the measurement tool in the oscilloscope on the windows version allows the user to select Channel 1- vertical/horizontal- min/max/peak2peak/avg/etc. On the Mac version, there is no option to choose between vertical and horizontal measurements. It is set default to vertical, so I am unable to measure frequency using a horizontal measurement. I am unsure if I am just unable to find the correct tool or if it is not yet a function in Waveforms3 beta. If that is the case, it would be very helpful if someone is able to write a function that I can input manually into the function to measure frequency. Thank you!