Everything posted by JColvin

Hi Simon, Going off the forum post you linked to, you will need an 8 GB SD card since the setup requires more than 4 GB. The particular SD card I linked to is the one Digilent used for the development of the ZYBO project. As for the name of the partition, the name itself does not matter very much; it's more so that partition type needs to be correct. Let me know if you have any more questions. Thanks, JColvin

Hi, You may also find this post helpful on creating a 400 MHz clock out of a 100 MHz clock. As for Vivado synthesizing taking awhile, that is (unfortunately) just going to be the case for programming any FPGA. Hamster explains the reasons here. Thanks, JColvin

This isn't directly related to this particular post topic, but you can always upload an image to our Gallery and then link to it from the forum post if you're out of space to upload photos directly. Granted, this isn't quite the same as dragging a photo that you can see within the post, but at least it's something.

Hi Jorge, We do not actually know the value of the capacitor C23 on the PCB since we do not have access to the schematic of this multimeter. I would recommend contacting Mastech, the company that makes this particular multimeter, here. Thanks, JColvin

Hi, You can set the jumpers of MD2, MD1, and MD0 to the correct setting to enable I2C mode with a corresponding device address of 0x48. Here is a summary of the appropriate jumper settings from the PmodCLS reference manual. For Rev D boards, the jumpers MD2, MD1, and MD0 need to be loaded, unloaded, and unloaded, respectively. For Rev E boards, the jumpers MD2, MD1, and MD0 need to be unloaded, loaded, and loaded, respectively. Let me know if you have any more questions. Thanks, JColvin

Hi Andres.Hortua, I presume you are talking about the Analog Discovery. Did you try using a different USB port/cable as recommend in the troubleshooting post? If your cable is especially long, that could be a potential issue as well. Thanks, JColvin

Cool! We have the Digilent MakerSpace located in part of Digilent's building. The address for it is 1300 NE Henley Ct. Suite 3 Pullman, WA 99163 The MakerSpace is open when Digilent has it's doors unlocked during the normal business hours of 9am-5pm, although we can arrange other times if necessary. We'd love for you to come by if you get the opportunity!

Hi scottcjordan,
For your first question, the Chip Select numbers are pin 2 for the ADC and pin 5 for the DAC. I was able to determine this by looking at the analogShield.h file contained in the library that is available for download on it's resource center and by looking at the Analog Shield silk screen. The schematic shows numbers 3 and 6 since it does not start at an index of "0" like the software does.
As for the second question; chipKIT boards all use 3.3V for their I/O voltage, and should correspondingly use the 3.3V jumper setting. An Arduino board operates at its own set voltage (either 5V or 3.3V), but you may use the IOREF pin, so that the Analog Shield appropriately uses the reference voltage the Arduino board inherently supplies. Unforunately, there is no easy way to determine the correct jumper setting from the schematic of the Analog Shield because as a shield, it is restricted to the operating voltage of the microcontroller board that it is plugged into; making it up to the user to look for the operating voltage of the microcontroller.
Let me know if you have any more questions.
Thanks,
JColvin

Hi, How are you powering your motors? Are you using an external power supply? As for braking, there is no way with this hardware setup to dynamically brake the motors, but there are a few ways that you can emulate braking. You could use a lower PWM value on the "Mode" pin to induce the motors to run at an effectively lower voltage, consequently lowering their speed and emulating a "braking" effect. Alternatively, you could also just no longer provide any power to the motor by driving the "enable" pin to a logic high voltage state so that the motors would quickly coast to a stop. The fastest way to brake to the motors would be to start running them in the reverse direction that they are currently going in. Thanks, JColvin

Hi Lefteris, I can't comment on all of your project (although it does sound cool), but in terms of programming an FPGA to non-volatile memory, you can check these two forum posts that explain how to get the bit stream stored on flash memory for Digilent FPGAs here and here.

Yes, that kit can work effectively for connecting the Pmod to the Basys 2. The split 12-pin cable can have its two 6-pin ends connect to two of the Basys 2 6-pin headers and the second 12-pin cable will be able to make the final needed connection for the remaining 6 pins on the PmodCLP. Note that for the split cable that the "B" side of the split is the side oriented to the "marked" 12-pin end of the cable. I'm not sure how this was supposed to make sense when that cable was selected for the kit, but at least it is an easy adjustment.

Hi Mark, Looking at the code, all of the non NI Linx portions will run just fine on a max32. The question that you will need to ask Sam on that link you provided is if you can replace the #include <LinxChipkitUc32.h> with #include <LinxChipkitMax32.h> as his comments indicate, and still have the program work correctly. Or you can always just make the replacement I suggested and see what happens. The biggest thing that I can see that would be an issue (in my admittedly limited experience with NI Linx interfacing with microcontroller boards) is that the pin numbers the program is using for the uC32 may not appropriately match the pins of similar functionality on the Max32. Let me know if you have any more questions. Thanks, JColvin

Hi JGRMSL, For a long time at Digilent we did not work with other microcontrollers besides our own; from my understanding this will be changing in the future, but nevertheless we do not have an .ino file for the PmodALS. It looks like the "DPSI" that the Teensy uses is a DMA SPI, so I would think that rather than converting it to arduino SPI, it would be easier to just start with the arduino SPI library since in terms of what the user sees, the two SPI types should be very similar in output. The biggest things that you need to be aware of are that the PmodALS needs to receive a clock frequency between 1 MHz and 4 MHz and sends out 4 leading zeroes, then the 8 bits of data (MSB first), and then 4 trailing zeros; all of these are limitations of the hardware component present on the PmodALS. I have given you a "pseudo C" example below in the arduino/MPIDE style: Let me know if you have any more questions. Thanks, JColvin