JColvin

Administrators
  • Content Count

    3263
  • Joined

  • Last visited

  • Days Won

    111

Everything posted by JColvin

  1. 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
  2. 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.
  3. Hi, I'm not sure what changes you are referring to. Could you post the link you got that explains these changes? Thanks, JColvin
  4. Hi, I have a couple of clarifying questions before anybody will be able to effectively help you. What license file are you referring to? A Vivado license? What board are you using? Thanks, JColvin
  5. Cool! Thanks for sharing!
  6. 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.
  7. Hi Alex, I think he is using Arch Linux on his ZYBO board, although I can't speak for his framerate. Thanks, JColvin
  8. JColvin

    Warmark

    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
  9. JColvin

    Basys3:xadcdemo question

    If you need to, you can upload larger images to our Gallery instead.
  10. 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
  11. Welcome to our Forum Marvin! Feel free to post on our any of our technical Forums and we'll do our best to help you out.
  12. Hi M, I apologize for not getting back to you over the weekend. In terms of the right servo moving faster than the left servo you can do one of two things. Inside the code for MPIDE, there are the three functions that move the robot: Foward(), TurnRight(), and TurnLeft(). Inside each of those functions you can either choose to slow down the right servo by providing the right.write() function inside each of them with a smaller number. Or you may change the value in the left.write() functions to a larger number. In other words, to make the robot go perfectly straight it will be a matter of trial and error since the default values will inevitably not work for every servo motor. As for your two outer sensors not responding; I would be inclined to think that the sensors themselves would be more like experiencing the problem as opposed to the PmodLS1, but without testing them both, it's hard to know which component is at fault. In terms of response times, I'm not seeing any way to make the response faster in software -- the biggest thing that I can think of, which you already did, would be to replace the batteries. All of the robots, especially the line following ones, will deteriorate in performance as the batteries get used up. You could also adjust the algorithm that turns the robot right or left by excluding all of the external sensor values (1, 3, 7, 8, 12, and 14), but I do not think this would improve the performance. Please let me know if I forgot to address something. Thanks, JColvin
  13. Hi JimW, Welcome to the Forum! I believe the Waveforms3 software that is coming out and runs the Analog Discovery will be able to support OS X 10.10. Feel free to post in the Scopes and Instruments section of the forum to find out for sure though, and send an email to waveforms (at) digilentinc (dot) com to receive Waveforms3 link. Thanks, JColvin
  14. Hi, I don't know if this is possible with this particular forum software but, for the Q&A setup on the technical forums, is there a way to comment on a question instead of just having the clarification questions be labeled as answers and then maybe have comments on answers so users can see the whole discussion nicely lumped all together instead of spread out between different answer posts? Kinda like how electronicsstackexchange does it? Thanks, JColvin
  15. JColvin

    adi i2s driver err ?

    Hi hogen, I haven't used ALSA before so I don't know if this will answer your "I don't understand the meaning of "axi-i2s: probe of 43c20000.axi-i2s-adi failed with error -2"" question, but I know another member on our forum ended up reworking the I2S core so that it works on Vivado 2014.4. You check the other forum post here. Let me know if this helps. Thanks, JColvin
  16. Hi, Have you checked out the support documents at the bottom of it's product page? There are several demonstration projects for the PmodCLP written in a variety of languages including C, C++, Verilog, and VHDL available for download. Let me know if you have any more questions. Thanks, JColvin
  17. A customer asked the following question:
  18. Hi, For your first video with you plugging in the last battery and seeing the motors jerk for a brief moment and then having a green LED blink several times, that is the chipKIT MX3 performing its internal bootup sequence so the microcontroller chip operates correctly. The motors jerk because they suddenly receive some power; this is the expected behavior of the board. As for your second video, it is a little weird that the robot does not start when you initially place it on the black line and that it completely stops when the far left sensor "hits" the black line between the tiles. The third time that the robot stops though is because all four sensors are noticing the black caulk line on your tile floor. Based on this, I have two recommendations. The first is to try adjusting the sensitivity of the PmodLS1 again. What I did was turn the robot upside down so that its sensors were facing the ceiling and rotated the knob until just before the LEDs on the PmodLS1 turned on. I put a photo in the gallery of where my knob was rotated to. The second recommendation is to replace part of the code that tells the robot to turn left or right with new code (mostly because I thought the old code wasn't written very well). This made the SRK robot that I was testing work a little more efficiently (at least in my opinion). Let me know how it goes! Thanks, JColvin
  19. From the album: Forum photos

    This is where I adjusted my PmodLS1 on the SRK line following robot to have the sensors work correctly. This is the angle just before the LEDs on the PmodLS1 lit up while the robot was powered, upside-down and facing the ceiling.
  20. There are some walkthroughs available; they are buried a little bit in the folder so they aren't the easiest to find, but here are the ones that I am aware of: On the Digilent reference site, both the Network Shield and the WiFi Shield have a support document in the Downloads section and will have "This zip file contains libraries and documentation for using the Network Shield, Wifi Shield..." as it's description. Within this file users may follow the chain chipKIT Network and USB Libs-20150115 >> libraries >> DWIFIck >> examples and view the documentation available as a text file within any one of those 8 examples. Since it uses some code from Microchip, you'll need to agree to a licence agreement before being able to download it. Alternatively, on the page for the chipKIT WF32 it has under the Reference Projects a Network Stack file with a description of "This zip file contains the Digilent embedded open-source...". Within this file user may follow the chain deIPcK >> DEWFck >> examples >> deWebServer >> Content >> SrvSetup.html which will lead them to an html document that seems to walk through getting an example http server setup. I believe the reason for these two different documents is that one set is for a shield or a Pmod and the other is designed for an on-board WiFi module, but I wouldn't quote me on that. There are also a number of MPIDE files that you can bring up and load onto your chipKIT board, but I do not know how clear they are for new users (such as myself). Thanks, JColvin
  21. I'll defer to hamster as I'm just the Pmod guy. Thank you for the correction.
  22. Hi M, I checked out your photos and may (or may not) see your issue. It looks like everything is set up nicely and in the correct Pmod headers, but I want to double check on the placement. Is your PmodBTN plugged into the top row of JD and the PmodCON3 and PmodLS1 plugged into the bottom rows of both JC and JB, respectively? It looks like they are, but I want to double check. I also presume that you are pressing BTN2 on the PmodBTN as opposed to the reset button the MX3 (the reset button would also produce the described behavior). Thanks, JColvin
  23. Hi Jesse, I talked with our chipKIT guy who wrote the deIP stack and unfortunately the short answer is that we do not have an example in C. Here his response: We can help you get the C++ MPIDE demo running if you would like to though. Let me know if you have any more questions. Thanks, JColvin
  24. Hi Jay, I know hamster already gave you some feedback on your other post, but here's some more information in case you need it -- if you're just needing to store your program onto the SRAM, you can generate the appropriate bitstream file in ISE or Vivado and then target the CellularRAM (the 'SRAM' that the Nexys 4 has) to store the bitstream. You can use the USB/JTAG interface which is the small micro USB port labeled "Prog" and "UART" on the Nexys 4 board. The control interface to transfer all of the data transfer from the computer to the Nexys 4 is already taken care of for you so you don't have to worry about it. Let me know if you have any more questions. Thanks, JColvin
  25. Hi Stuart, I don't be believe we have anything specifically for the Zedboard, but feel free to take a look at these two VHDL reference designs for the PmodRS232 here and here. The PmodNIC100 uses a Wifi stack from Microchip, so it hasn't been ported over to FPGAs (at least to my knowledge). I'll ask our support team if we have any other tutorials that are a little more oriented to the Zedboard or not. Thanks, JColvin