|
 | | Re: Rotation sensor bug found (maybe!)
|
| (...) You've got a point here. What if we hardwire STATE_0_VALUE to the following? #define STATE_0_VALUE (ds_unscale(1023U)-RANGE_SIZE) Or, for a more general approach: #define MIN(a,b) (a<b?a:b) #define MAX(a,b) (a>b?a:b) #define STATE_VALUE(k) ( \ (...) (25 years ago, 17-Apr-99, to lugnet.robotics.rcx.legos)
| |
|  
range
(score: 1.631)
|
|
| | Mars with video capture
|
| I finally got my Mars Expansion Pack working with my Pinnacle Video Capture Card, type DC10 Plus. I can switch between the tiny black and white camera that fits on a robot much better, viewed through the card, and the USB QuickCam Pro golf ball (...) (24 years ago, 16-Apr-00, to lugnet.robotics.rcx)
| |
|
usb
(score: 1.631)
|
|
| | Re: Blocking IR
|
| Regarding your program. Try sending 0s, not xs, i.e.: char *buffer = "\0\0\0\0\0"; Zeros are coded with the IR on 91% of the time, while xs are coded with the IR on only 45% of the time, neglecting the modulation, which cuts that all down by half. (...) (25 years ago, 16-Jun-99, to lugnet.robotics.rcx.legos)
| |
|
ir
(score: 1.631)
|
|
| | Rotation sensor bug found (maybe!)
|
| I think I might have found a bug in the ds_rotation_handler (direct-sensor.c). The problem arises when the STATE_0_VALUE is checked using the IN_RANGE macro. As STATE_0_VALUE is 1023U<<6, which is about the max value for an unsigned, adding to it (...) (25 years ago, 17-Apr-99, to lugnet.robotics.rcx.legos)
| |
|
range
(score: 1.631)
|
|
| | Re: Blocking IR
|
| Hi Kekoa, Could you post your working IR .srec code or email me if possible? I have tried the examples with the LegOS read sensor routines and I still get the same results. i.e. it works at about 2mm from the unit but fails after more than 5mm. I (...) (25 years ago, 21-Jun-99, to lugnet.robotics.rcx.legos)
| |
|
ir
(score: 1.631)
|
|
| | light values?
|
| Another question before I call it a night- under LegOS 0.1.6, light-sensor values were restricted to the range 0-100. Under 0.1.7, I'm now getting a max value (pointed straight at a light bulb) of about 263, or once even 272. 255 would make sense to (...) (25 years ago, 12-Apr-99, to lugnet.robotics.rcx.legos)
| |
|
range
(score: 1.631)
|
|
| | tm-and-ir (again)
|
| Hi all, I've been using Legos without any major problems but never got the tm-and-ir demo to work properly. I can receive characters on the RCX fine but when the 'view' button is pressed (within 3 seconds) the results are normally junk on the screen (...) (25 years ago, 7-Jun-99, to lugnet.robotics.rcx.legos)
| |
|
ir
(score: 1.630)
|
|
| | Re: Rotation sensor bug found
|
| (...) It wouldn't, though. First it gets the maximum of the given value or RANGE_SIZE. That is done to prevent a similar overflow at the low end, even though, with current values, that won't happen. Then, that value is compared against the safe (...) (25 years ago, 19-Apr-99, to lugnet.robotics.rcx.legos)
| |
|
range
(score: 1.630)
|
|
| | Re: Blocking IR
|
| (...) Do you mean dir_write? This is a problem with LegOS only. If you want non-blocking writes, comment out (in version 0.1.7 at least): while(dir_tx_state==TX_ACTIVE) ; // FIXME: scheduler integration if(dir_tx_state==TX_OK) return len; // (...) (25 years ago, 10-Jun-99, to lugnet.robotics.rcx.legos)
| |
|
ir
(score: 1.629)
|
|
| | Re: Blocking IR
|
| (...) I forgot to mention. At the top of dir_write, you probably want to add: if (dir_tx_state == TX_ACTIVE) return -1; Or something to that effect, so you don't transmit a second message while a first is still transmitting, and so you have a way of (...) (25 years ago, 10-Jun-99, to lugnet.robotics.rcx.legos)
| |
|
ir
(score: 1.629)
|
|
| | is IR considered broken?
|
| The precompiled tm-and-ir, kinda works for me. It is pretty good at receiving data, but the transmitted message often has garbage. When I compile it myself using the latest legOS snapshot, it always transmits garbage, others seem to have seen the (...) (25 years ago, 12-Jul-99, to lugnet.robotics.rcx.legos)
| |
|
ir
(score: 1.628)
|
|
| | Re: Blocking IR
|
| In addition to what I mentioned in the previous message, I also set the sensor input port to active. Setting it to passive also works, in which case the ambient light level seems to be around 480-495, and the sensor aimed directly at the IR port (...) (25 years ago, 21-Jun-99, to lugnet.robotics.rcx.legos)
| |
|
ir
(score: 1.628)
|
|
| |
|
ir
(score: 1.628)
|
|
| | Re: Blocking IR
|
| (...) I doubt you have a broken RCX. If you did, firmdl.c would not download firmware correctly. (...) That is a good thing to try; I suppose it did not help things? (...) I don't see why you couldn't post the .srec file. I don't know if you also (...) (25 years ago, 20-Jun-99, to lugnet.robotics.rcx.legos)
| |
|
ir
(score: 1.628)
|
|
| | Re: Blocking IR
|
| Thanks for your help but I think I might have a broken RCX. The code I've been testing and the examples you have help me with all work if I place the light sensor about 2 mm from the IR transmitter. At about 2cm it no longer works at all. I have (...) (25 years ago, 20-Jun-99, to lugnet.robotics.rcx.legos)
| |
|
ir
(score: 1.628)
|
|
| | Re: is IR considered broken?
|
| (...) I have working IR code, but it does not work with LegOS. It works with that "custom, as-yet-unreleased version of Librcx" I mention every so often. It probably wouldn't take much to port it to LegOS. Changes would be: - modify hook to get a (...) (25 years ago, 16-Jul-99, to lugnet.robotics.rcx.legos)
| |
|
ir
(score: 1.627)
|
|
| |
|
ir
(score: 1.627)
|
|
| |
|
ir
(score: 1.626)
|
|
| | Re: emulegOS: a new release
|
| Just a note about a small bug. The supplied sample program ir-rover.cpp doesn't work on the real RCX. I think this may be due to IR complications under legOs. I'm working on a version which will work on both the emulator and the real system and will (...) (25 years ago, 21-Jul-99, to lugnet.robotics.rcx.legos)
| |
|
ir
(score: 1.625)
|
|
| | Re: signals / legOS internals
|
| (...) When a frame or character has been received by the IR port it signals an interrupt to the processor. The processor (OS) handles this by invoking an ISR (Interrupt Service Routine). In OSE ISR's are known as interrupt processes and they execute (...) (25 years ago, 25-Jun-99, to lugnet.robotics.rcx.legos)
| |
|
ir
(score: 1.625)
|
