JColvin

Administrators
  • Content Count

    3303
  • Joined

  • Last visited

  • Days Won

    115

Everything posted by JColvin

  1. 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.
  2. 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
  3. 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
  4. 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
  5. 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
  6. 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
  7. A customer asked the following question:
  8. 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
  9. 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.
  10. 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
  11. I'll defer to hamster as I'm just the Pmod guy. Thank you for the correction.
  12. 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
  13. 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
  14. 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
  15. 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
  16. That would be sweet if it was set up for a quad or a quint. It makes sense that frequency profile would be the same on a single drum since you want the heads of drums to be at a consistent tension while playing. For the whole orchestra, it might be interesting to just look into a microphone to pick up the frequencies (much like the sound sensor Tommy's team had for senior design) since I'm guessing the piezo sensor only grabs the physical vibrations, hence the percussion instruments. Its curious that it didn't pick up the vibrations off of the cymbal though... too much vibration should not be an issue and it's not like there are frequencies on the cymbal that cancel each other out, otherwise we wouldn't be able to really hear the cymbal in the first place.
  17. Hi ricardo_lara_gomez, We don't have a Pmod that is specifically designed for measuring liquid height. The PmodMAXSONAR would be able to detect how far away the liquid is from the top of the tank (presuming that is where the sensor was placed. There is demo code available for it on it's product page. This Pmod only has a resolution of 1 inch though, so if you need a higher precision sensor you would need to look outside of Digilent for that. Thanks, JColvin
  18. Hi, I can see within a particular forum subgroup that certain questions have been marked as the best answer, but if I click on a particular post, I cannot immediately/visually see which answer was marked as the "best" answer. Is there a way to implement that with this new forum setup? Thanks, JColvin
  19. Hi M, What you're describing when you press BTN2 and then having the MX3CK board blinking a green LED is indicative that there is an electrical short somewhere with the servo motors, causing the MX3CK to use its shut-down circuitry. It does seem a little weird that even when you adjust the knob for the PmodLS1 that the sensors still light up even on a dark surface, although this is unrelated to the short. Could you post a picture(s) of your setup so I can take a look at it? You can use our Gallery or some other way to post/host the photo. Thanks, JColvin
  20. Hi Sam, From the errors listed on your screen shot it would seem that there is an issue with semi-colon somewhere in the WireIA.cpp library. Since I'm not able to replicate your exact error, you could either try re-downloading the library to see if that fixes the error or post the WireIA.cpp and WireIA.h files in a comment (preferably in an attached file) and I'll see if I can find out what's wrong. Thanks, JColvin
  21. As you can see, we also updated our forum today to a new server so everything should run a little smoother and faster. However we also lose all of our customization during upgrades, but it'll be back to the green forum that you know and love by early next week. Thanks for understanding! JColvin
  22. Hi, I believe a demo for receiving data through UART was being worked on; I'll ask around and find out the status on that. In the mean time, you can check out these two reference designs for RS232 which utilizes UART here and here. Thanks, JColvin
  23. Hi, Here is a link to a "beta" version of the project at this dropbox link. From what I understand, it is a working project that just needs a little more work in terms of explanations about timing constraints. There are also some notes about the project that I was told to pass on: Thanks, JColvin
  24. Will you have it so that the type of drum hit (the frequency that the piezeo sensor picks up) proportionally changes the color as well? I.e. low frequency/soft hits for red, harder hits for green, and rimshots for blue?
  25. Hi ReiVilo, After talking with our chipKIT guy I found out that those nobootloader linker scripts were only for debugging purposes. Microchip's MPLAB X has been updated to load bootloaders as well as the rest of the code, so that the nobootloader scripts are no longer necessary for the chipKIT PGMs. The ones that you see are there just for compatibility reasons, but are otherwise not used. Thanks, JColvin