attila

Hi @Anthocyanina Hope in this latest version the auto scaling works better. The Tracer is now by default stacked with Scope, Logic... The automatic options cannot be perfect and neither can the default positions, there are many tools, views... and combinations/use case with these. You can save workspaces with preferred settings and positions, use 'without acquisition' option for faster save/load.

Hi @Josh52 It is fixed in the latest version: Thank you for the observation.

Hi @Piyapong If you are getting overcurrent try disconnecting the load on V+/-, use 5V DC supply for the device to increase the supply limits.

Hi @Anthocyanina Could you send me or attach a workspace or project with a Tracer trace that does not auto-scale properly ?

Hi @Josh52 It is a documentation bug. The FDwfDigitalUartParitySet options order should be as it is in the WaveForms application: 0 no parity, 1 even, 2 odd, 3 mark (high), 4 space (low) Thank you for the observation.

Hi @Rachel The ADP3450 and EclypseZ7 (can) have 4 Scope channels and 128/256M sample buffer. See the device comparison at the following link or the WaveForms application Help tab. https://digilent.com/reference/test-and-measurement/start https://digilent.com/reference/programmable-logic/eclypse-z7/start The newer WaveForms versions support Dual device control. I recommend using the WF app and the latest beta version for such purpose, and for automation use the Script tool of the application. The pydwf is a 3rd party support from @reddish I'm not too familiar with it but it should support all T&M devices. About the API/SDK see the manual and examples in the installation:

An ADuM4160 based one.

Hi @JerryM 1. With local network, select "Obtain IP address automatically" ! or use your networks subnet and an unused IP, outside of the DHCP server reservation. 2. You can try Linux mode but with this you loose the deep buffering and a bit on transfer performance.

Hi @Holger Senn The limitation is from the low level library, niVB_Status_ErrorCannotRenameDeviceBecauseNameInUse It does not allow devices to have the same name. This can be tricked by renaming one from another computer. If you connect multiple ADP5XXX or VirtualBench devices with the same name, only one will be listed/available ! To rename with one computer: close WaveForms (and LabView, VirtualBench app...), delete the following file, connect one device and rename. C:\Users\[USER]\AppData\Local\National Instruments\NI-VirtualBench\ ni-virtualbench-devices.db

Hi @aida I wanted to say that you could use demo mode, but to be realistic, it adds a bit of noise to the simulated signal; triggering is not supported... In demo mode the Scope channel # returns a preview of the configured signal for FGen # adding up to 0.1% of the amplitude as random noise.

Hi @SausageDog Not DAQmx, but WaveForms application, WF API, Digilent WaveForms VIs,...

Hi @chiznut

Hi @jom@JonD

Hi @mmessuri The USB isolator I have is FS and the signals on it look like this:

Hi @LegoTechniker Make sure you are looking at correct IOs, wires. Which device are you using ? On Analog Discovery 1,2,3 the DIO0 is in the middle of the connector, at the keyhole, pink wire. Before this you have the Trigger1 (gray) and after the DIO1 (green)

Hi @JerryM Make sure the other network interfaces are not in conflict with this, are on different subnet, it is not 192.168.2.X Have you tried connecting the device to your local network with auto IP, DHCP ?

Hi @mmessuri It should work. The FS differential frequency is only 12MHz and the signal voltages are higher (3.3V) so single ended inputs should be able to capture it.

Hi @JerryM The IP should be different, like .10 for one and .11 for the other one.

Hi @mmessuri This product is not suitable for monitoring USB HS 480MHz differential signals.

Hi @chiznut The next software version will support multi chip-select in Protocol/ SPI/ Spy

Hi @Maxime Are you using the newer Matlab support ?

Hi @Aye The on 64bit Intel (x86_64/amd64) you can have 32bit and 64bit OS installed. Regardless of this, since you got ""FTDI library loading failed"", indicates that on your system the drive is not properly installed. 1. You could try to copy the following: C:\Program Files (x86)\Digilent\Runtime\UsbDriver\amd64\ftd2xx64.dll as ftd2xx.dll to the 64bit SYS32, C:\Windows\System32\ (see from 64bit apps, file explorer) and for 32bit apps support C:\Program Files (x86)\Digilent\Runtime\UsbDriver\i386\ftd2xx.dll to the 32bit SYS32, C:\Windows\SysWOW64\ (see from 64bit apps, file explorer) 2. Remove the existing drivers and reinstall: 3. Reinstall Windows.

Hi @lokobob99 For AD2 digital-in (Logic Analyzer) captures are transferred over USB as 16bit samples (16 DIOs) or 2x16 if data compression or noise capture is enabled. The API has options to return these as 8,16 or 32 bit samples. In your implementation you can probably forward the samples even at 1bit/sample if you want.

Hi @ZhaoSQ The IA SDK/functions are not working in 3.20.1 but it is fixed in the newer beta version:

Hi @chiznut Only one interface can control a specific device instrument at a time. You should add all 3 SPI interpreters in one Logic Analyzer and use 4th device configuration which has more buffer Logic and/or use Record mode to capture even more data.