To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.robotics.rcx.legosOpen lugnet.robotics.rcx.legos in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Robotics / RCX / legOS / 3613 (-10)
  Re: Sensor Power
 
(...) Take a look at the functions ds_power_on() & ds_power_off() as defined in the dsensor.c kernel file. When you've set the sensor to passive mode, you should be able to manipulate the sensor power bits using these functions[1] or just use the (...) (21 years ago, 6-Jan-04, to lugnet.robotics.rcx.legos)
 
  Re: Motor Display
 
(...) This problem has been fixed in the most recent CVS source file (dmotor.c), but as far as I can tell it hasn't been part of an offical release yet: (URL) (21 years ago, 5-Jan-04, to lugnet.robotics.rcx.legos)
 
  Re: The BrickOS Task Manager
 
tid_t -> thread ID pid_t -> process ID ? "nanobapt" <nanobapt@wanadoo.fr> wrote in message news:3FF95FD4.608020...adoo.fr... (...) (21 years ago, 5-Jan-04, to lugnet.robotics.rcx.legos)
 
  Sensor Power
 
ok, I have a real question. I'm interested in sending messages between RCXs using only the sensor ports. I've tested and found by switching between active and passive, signals can be sent, however, when the port is set to active, it is not powered (...) (21 years ago, 5-Jan-04, to lugnet.robotics.rcx.legos)
 
  Motor Display
 
For some silly reason, I was browsing through the BrickOS code and I noticed this: void motor_a_dir(MotorDirection dir) { dm_a.dir = dm_a_pattern[dir]; dlcd_hide(LCD_A_LEFT); dlcd_hide(LCD_A_RIGHT); if (dir == fwd || dir == brake) (...) (21 years ago, 5-Jan-04, to lugnet.robotics.rcx.legos)
 
  Re: The BrickOS Task Manager
 
(...) only as a side note: you shouldn't really do this. you are burning precious cpu-cycles here. it should look something like while(!(rowdone && coldone)) msleep(5); if you're in a hurry you can make smaller msleep's... (21 years ago, 5-Jan-04, to lugnet.robotics.rcx.legos)
 
  Re: The BrickOS Task Manager
 
in version 2.6.1 (I've just download it) extern tid_t execi(int (*code_start) (int, char **), int argc, char **argv, priority_t priority, size_t stack_size); declare in unistd.h ! So use the tid_t and not the pid_t ! (like say ROSCO) Does anyone (...) (21 years ago, 5-Jan-04, to lugnet.robotics.rcx.legos)
 
  Re: problems wirh installing driver for usb-tower under linux
 
Von: "Annedore Rößling" <u15780@hs-harz.de> Betreff: Re: problems wirh installing driver for usb-tower under linux Datum: Sonntag, 4. Januar 2004 13:25 (...) When I tried ./configure --with-linux-include...n/include/ confiure.in continued but (...) (21 years ago, 4-Jan-04, to lugnet.robotics.rcx.legos)
 
  Re: The BrickOS Task Manager
 
(...) [snip] (...) Hi Mike, What version of BrickOS are you using? IIRC the correct type for thread IDs in the current version is tid_t, not pid_t. Also, I dunno if it was a typo, but you should include tm.h, not tm.c. HTH ROSCO (21 years ago, 5-Jan-04, to lugnet.robotics.rcx.legos)
 
  Re: The BrickOS Task Manager
 
(...) Hmm... it doesn't seem to recognize pid_t as a valid type. I have a document of the functions in brickOS that indicates execi returning an int. Which is it? (...) Still confused... I'll post the poignant code: pid_t rowthread; pid_t colthread; (...) (21 years ago, 5-Jan-04, to lugnet.robotics.rcx.legos)


Next Page:  5 more | 10 more | 20 more

Redisplay Messages:  All | Compact

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR