|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools |
Rating:
|
Display Modes |
|
|
|
#1
|
|||
|
|||
|
Is OpenVex a dead project?
Here's a link to the project: http://personalpages.tds.net/~jwbacon/vex.html
I've been trying to get it to work for some time now and I've even contacted the project manager and it seems that he/she is MIA. It looks extremely complicated just to get it working. Anyone have any luck? If you're wondering why I want to use this, it's because I like Opensource programs. |
|
#2
|
||||
|
||||
|
Re: Is OpenVex a dead project?
I'm not sure if this applies here or not, but I will put it out there for anyone who might be interested.
Kevin Watson has made a Vex default code set based on his 2008 FRC default code replacement. It is built for the v .5 controller, not Cortex. It works well with MPLab 8 and either the 2.4 or 3.0 or 3.5 compiler. I currently have it running with Line Tracker code and a Vex US sensor. It comes set up for 6 encoders and a gyro. Kevin has also provided his Serial port code, PWM code, ADC code. |
|
#3
|
||||
|
||||
|
Re: Is OpenVex a dead project?
Quote:
I'm also working on code for the Vex Cortex, but it's been hard to make much progress with the demands of my day gig. It'll happen, though. -Kevin |
|
#4
|
|||
|
|||
|
Re: Is OpenVex a dead project?
Hello,
I recently stumbled upon Open Vex and think it is a very solid implementation on the Pic controllers (hoping for Cortex support but w/e). Anyway I was wondering if the only working repo is the one at http://personalpages.tds.net/~jwbacon/Ports/distfiles/ or if there is a public repo where one can commit changes (like a git.) If not I'd be happy to maintain it ![]() P.S. Does anyone know how to detect competition start signals and what not. I figure its just a serial call however if there is a working method no need to reinvent the wheel |
|
#5
|
|||
|
|||
|
Re: Is OpenVex a dead project?
Jason Bacon responded at http://www.vexforum.com/showthread.php?t=7681
|
|
#6
|
|||
|
|||
|
Re: Is OpenVex a dead project?
Note to the community: OpenVex is being actively developed and maintained.
I did respond to Godzilla's email the day I received it, so perhaps it was delayed somehow. To clarify, Godzilla is using a Cortex controller, which is not yet supported by OpenVex. OpenVex for PIC controllers is fairly well developed and stable. It should not be too difficult to use for PIC controllers, but I welcome any feedback/questions from newbies. Quote:
|
|
#7
|
|||
|
|||
|
Re: Is OpenVex a dead project?
My apologies for reopening a very old thread. I have been trying to make an account on the Vex forum so I can ask there, but despite it looking like I have an account it won't let me post.
I have been using openvex as a free Linux alternative to EasyC or RobotC and have found it to be easy enough to use. Has anyone implemented a routine to read a gyro with openvex? Has anyone implemented an API to the second TX/RX port (the ones exposed on the controllers TX/RX pins)? I'm sure I can figure these out myself, but would like to save the effort if someone has already done it. thx |
|
#8
|
||||
|
||||
|
Re: Is OpenVex a dead project?
Quote:
http://kevin.org/frc Follow the directions for merging the gyro code for the FRC controller, which is almost identical to the Vex controller. Once you have it working, you should be able to merge the pieces of code you want into the OpenVex framework. -Kevin |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|