|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools | Rate Thread | Display Modes |
|
#1
|
||||
|
||||
|
Code compile time?
Hey there, FLL'ers! About how long does your code take to compile? Does the NXT LabVIEW software compile any faster than vanilla LabVIEW?
|
|
#2
|
|||
|
|||
|
Re: Code compile time?
I have not had recent experience with NXT-G, but ROBOLAB (which is exactly like LabVIEW) compiles and downloads within a few seconds. (less than ~10s) So yeah, it is a TON faster.
NXT-G is a bit clumsy and keeps throwing insane-object errors. |
|
#3
|
||||
|
||||
|
Re: Code compile time?
I'll definitely look into ROBOLAB for coding my NXT projects. LabVIEW 8.6 was taking around 10 minutes to compile a standard motor control + touch sensor.
|
|
#4
|
||||
|
||||
|
Re: Code compile time?
NXT-G software only takes seconds to compile ordinary programs. Don't know how complex your are but I've never had it take more then 10 and that was with a program that was actually a mini operating system.
|
|
#5
|
|||||
|
|||||
|
Re: Code compile time?
I'm sorry, but I don't really have anything useful to add here. However, when your code is compiling there's always:
![]() |
|
#6
|
||||
|
||||
|
Re: Code compile time?
Haha nice!
We have used both LabView and RobotC for FTC, and have examined NXT-G on the team we mentor for FLL. NXT-G takes a few seconds and RobotC usually takes ~2-3 seconds. However, LabView kills us. It usually takes 1-2 minutes OR MORE to download a simple program. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|