Search found 552 matches
- 25 May 2014, 19:12
- Forum: Mindstorms Hardware
- Topic: NXT 2.0 Mainboard burned
- Replies: 4
- Views: 26439
Re: NXT 2.0 Mainboard burned
Might cost you a fortune to source & purchase components, and if you don't find the root cause then it could happen again. Now that the EV3 is out, NXT's are coming on ebay at about half what they fetched a few months ago. Saw a partial kit (NXT, some motors & sensors plus other bits) going ...
- 22 May 2014, 01:24
- Forum: Mindstorms Software
- Topic: New tab in BRIXC
- Replies: 3
- Views: 12376
Re: New tab in BRIXC
OK, thanks Helmut. The more I think about it, I suspect that the post was about having more than one program open at a time, which involved unchecking one of the preferences. What I was looking for was a way to have parts of the same program shown in different tabs but I don't think that is possible.
- 21 May 2014, 06:51
- Forum: Mindstorms Software
- Topic: New tab in BRIXC
- Replies: 3
- Views: 12376
New tab in BRIXC
I seem to recall that there was some way of opening a new tab in the BRIXC editor using some combination of keys (not 'New File').
Been through all the preferences and help files but can't find anything.
Has my memory finally gone kaput or am I just looking in the wrong places?
Been through all the preferences and help files but can't find anything.
Has my memory finally gone kaput or am I just looking in the wrong places?
- 17 May 2014, 12:21
- Forum: Mindstorms Hardware
- Topic: NXT Bluetooth connection
- Replies: 1
- Views: 19700
Re: NXT Bluetooth connection
When I had this problem I deleted the connection from both the PC and NXT, restarted both and set up a new connection.
- 13 Mar 2014, 12:30
- Forum: Mindstorms Software
- Topic: motor problems
- Replies: 11
- Views: 37272
Re: motor problems
Some useful NXC guides -
http://www.engineering.uiowa.edu/~cie/L ... torial.pdf
http://bricxcc.sourceforge.net/nbc/nxcdoc/
Did you get your program working yet?
http://www.engineering.uiowa.edu/~cie/L ... torial.pdf
http://bricxcc.sourceforge.net/nbc/nxcdoc/
Did you get your program working yet?
- 12 Mar 2014, 17:35
- Forum: Mindstorms Software
- Topic: motor problems
- Replies: 11
- Views: 37272
Re: motor problems
The 'OFFEX' command would have to be given before any other commands for that motor.
Try making it the first line of code.
Try making it the first line of code.
- 08 Mar 2014, 14:34
- Forum: Mindstorms Software
- Topic: motor problems
- Replies: 11
- Views: 37272
Re: motor problems
The brick seems to keep track of the motors so, if you move a motor manually then run a program to move that motor, it resets the motor to the original position before following the move command. Not saying it is the cause of your problem, but I got some weird behaviour out of my rig until I found a...
- 08 Mar 2014, 02:48
- Forum: Mindstorms Software
- Topic: motor problems
- Replies: 11
- Views: 37272
Re: motor problems
The code you have given will only work for one turn each way before stopping so you need to put a loop round it if you want it to repeat.
Perhaps you should look at the 'line follower' programs which abound on the web to see how others have coded similar actions.
Perhaps you should look at the 'line follower' programs which abound on the web to see how others have coded similar actions.
- 08 Mar 2014, 02:44
- Forum: Mindstorms Software
- Topic: Basic Loop Program
- Replies: 2
- Views: 9712
Re: Basic Loop Program
I'm not familiar with EV3 either but it looks as if you have put all the turns in a loop before backing up, which is exactly what you describe the robot acting. Perhaps you should just set it to run in a circle until it hits an obstacle (inside the IF loop) then telling it to back up. This sounds ve...
- 08 Mar 2014, 01:37
- Forum: Mindstorms Software
- Topic: motor problems
- Replies: 11
- Views: 37272
Re: motor problems
Try putting this before the motor commands -
OffEx (OUT_B, RESET_ALL); // Reset the motor counters
Wait (100); // Give sensor time to update
OffEx (OUT_B, RESET_ALL); // Reset the motor counters
Wait (100); // Give sensor time to update