|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools | Rate Thread | Display Modes |
|
#1
|
||||
|
||||
|
Has WPI fixed the timing errors from 2015?
I recall timing errors with java in 2015 made it very hard for teams to use PID loops (the D part, mostly). Does anyone know if these have been fixed? I scanned over the wpilib website and found no information on this.
![]() |
|
#2
|
||||
|
||||
|
Re: Has WPI fixed the timing errors from 2015?
I don't recall any timing errors other than built in scheduler functions being unable to resolve themselves properly because the RIO doesn't keep time when turned off, and this hasn't changed at all. What timing issues are you referring to? System.currentTimeMillis() works fine iirc
|
|
#3
|
||||
|
||||
|
Re: Has WPI fixed the timing errors from 2015?
Quote:
http://www.chiefdelphi.com/forums/sh...1&postcount=20 |
|
#4
|
||||||
|
||||||
|
Re: Has WPI fixed the timing errors from 2015?
The notifier class was added to java, but it doesn't look like the PIDController class was updated to use it.
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|