-
Posts
6,651 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Gallery
Posts posted by attila
-
-
Hi @laurent
In case your script quits the device gets closed and the outputs stopped.
Set the following parameter before opening the device to keep it running on quit/close:
dwf.FDwfParamSet(DwfParamOnClose, c_int(0)) # 0 = run, 1 = stop, 2 = shutdownThe VIO could be stopped due to over-current.
See the SDK/ samples/ py/ AnalogIO_DigitalDiscovery.py -
Hi @nikko
The device looks to be detected by the OS correctly.
I'm not sure how critical the "Resource temporarily unavailable (11)" info is...Did you install the digilent.adept.runtime and digilent.waveforms packages ?
https://reference.digilentinc.com/digilent_adept_2
https://analogdiscovery.com/Do you get any error when you lunch the application ?
-
Hi @Ferda
You can find the latest manual, corresponding to the software version in the SDK installation:
-
Hi @Camarillo
Probably some high voltage transient input or accidentally having the probe at 1x with high voltage damaged the ADG612.
Before replacing the ADG612 you could verify the VREF_SC2 and VOFF_SC2 voltages.
https://reference.digilentinc.com/reference/instrumentation/analog-discovery-2/reference-manual#scope_reference_and_offset
- the VREF should be about 2V
- the VOFF with:
0V offset about 2V
+2.5V offset with 500mV/div range about 3V, like the screenshot below
--2.5V offset with 500mV/div range about 1VSome further troubleshooting posts:
-
Hi @Ferda
The minimal differences between in AD1-2 are the analog io, power supplies and monitoring:
-
Hi @nikko
The entire board, including the USB controller is powered from the 12V power supply. Make sure this is working correctly.
Does the lsusb list "ID 1443:0007 Digilent" device ? -
Hi @dave slagle
The part number for the USB (micro B surface mount, right angle, through hole) is USBC-FC05RB2N4, but I can't find any source for it.
Here you have the specs for it:
For manual soldering one similar, with same pinout-pitch should do it. -
Hi @dave slagle
The consistent 5 minute could indicate some system sleep or USB suspend, rather than contact issue...
Please try disabling sleep as @Mr.Spriggs suggested. -
Hi @sib
The earlier spi-custom code I posted was tested with Pmod ACL2.
It looks like you have receive the correct device ID code using the 'spi-master', so the communication is working.
What do you get when you run the spi-custom code ? -
Hi @sib
Here you have script for ACL2.
// Pmod ACL2 - ADXL362 Select.Active.value = 0; Clock.Polarity.value = 0; Clock.Phase.value = 0; if(Clock.Frequency.value > 1e6) Clock.Frequency.value = 1e6; Start(); Write(8, 0x0B, 0x00); // Read Register, Device ID var rgID = Read(8, 4); Stop(); if(rgID[0] != 0xAD || rgID[1] != 0x1D || rgID[2] != 0xF2){ return "Device ID mismatch "+rgID; } Start(); Write(8, 0x0A, 0x2D, 0x02); // Power Control Register, Measurement Mode Stop(); Start(); Write(8, 0x0B, 0x0E); // Read Register, Data var rg = Read(8, 8); Stop(); // convert data bits to signed value relative to gravitational constant // MSbit sign, LSBit 0.001g for default 2g mode var gx = (0.001* ((rg[1]<<28) | (rg[0]<<20)) /1048576).toFixed(3); var gy = (0.001* ((rg[3]<<28) | (rg[2]<<20)) /1048576).toFixed(3); var gz = (0.001* ((rg[5]<<28) | (rg[4]<<20)) /1048576).toFixed(3); var tp = (0.065* ((rg[7]<<28) | (rg[6]<<20)) /1048576).toFixed(2); return "X: "+gx+"g Y: "+gy+"g Z: "+gz+"g Temp: "+tp+"*C";
The measurements seem to be less accurate, see the ADXL362 datasheet regarding specs and calibration...
-
Hi @dave slagle
You can find the system monitor in the status bar and in the Supplies window.
The earlier script i just added to see how does the temperature rise. -
Hi @dave slagle
What temperature are you reading?
In this device without active cooling, around 50*C is normal or more if you have loads. -
Hi @dave slagle
The USB connector in the AD2 is strong and reliable. I'm using some since many years and never had any problem with it. Except some cables are not making good contact with one device or the other kind of devices.
On your device some USB cable or try to reversely plug could have damaged the socket.I don't think the two year old device is in warranty... You should try to replace the USB connector.
-
Hi @dclock
Thank you for the feedback.
-
Hi @dave slagle
This is likely a connection-contact issue. The error indicates loss of USB communication.
Try using other cables eventually powered USB hub. -
Hi @dclock
Did you try installing the driver from the installer DMG?
Could you try the latest beta version?
https://forum.digilentinc.com/topic/8908-waveforms-beta-download/
This updates the USB libraries for macOS.Install the dwf.framework form the DMG and try running the following:
$ python /Application/WaveForms.app/Contents/Resources/SDK/samples/py/Enumerate.py -
Hi @sib
Thank you for sharing your code. I will test the example and your code as soon I find the ACL2, or get a new one...
You may need a Protocol.SPI.Stop/Start() between "SPI RESET" and "Read Device ID".
-
-
Hi @sib
Thank you for the photo and screenshot. The wiring looks good.
At the moment I can't find ACL2, only ~20 other PMods, but the last time I've checked it was working.You have selected the example for ACL with ADXL345. This has different command set than the ACL2 with ADXL362 IC. Probably you wanted to say ACL2 and not ACL5.
Under the Custom tab select the ACL3/2 with ADXL362 and Run. These is a typo mistake, it should be ACL2 instead ACL3.
In case you use the Logic Analyzer, the Protocol tool won't be able to read data, so the uncheck this option otherwise you will get "Device ID mismatch".You can also use the Master tab
-
-
Hi @sib
You should have:
CS to Select, SCLK to Clock, MOSI to DQ0, MISO to DQ1
Pin-5 or 11 to GND and Pin-6 or 12 to V+ 3.3VThe other interrupt pins and DQ2-3 are not required.
You can find info about the Pmods at:
https://reference.digilentinc.com/reference/pmod/pmodacl/start
https://reference.digilentinc.com/reference/pmod/pmodacl2/start -
Hi @sib
You can find script examples in Protocol tool/ SPI-I2C Custom and Sensor tabs.
You can also find SPI/I2C examples in the SDK:
-
Hi @caesun
For such purpose you could use the OpenScope or OpenLogger:
https://store.digilentinc.com/usb-scopes-instruments-circuits/ -
Hi @m72
Thank you for the observation. I managed to reproduce the issue.
Until this gets solved, please use lower cursor numbers as reference.
I think it's broken
in Test and Measurement
Posted
Hi @Camarillo
I meant measuring the VOFF_SC2 relative to the device GND with external DMM.
Having the scope channel 2 range 500mV/div or lower, changing the offset between -2.5V and 2.5V should change the VOFF_SC2 between ~1V and ~3V
Above 500mV/div for offset between -25V and +25V change VOFF between ~1V and ~3V.