If you're not seeing the first line, I think something is going wrong in the detector sketch. You should see text as the detector. The code just does basic Serial.print and println to show the values.
How are you slowing down the detector? You're only messing with this line correct: "SPI.setClockDivider(SPI_CLOCK_DIV64)"
I think 64 should be more then enough but 128 is the slowest it'll go.
Ohw Jee, sorry but I have no experience with (any) forum and only a little with English, so excuse
my mistakes.
Answer to Ikazone:
How are you slowing down the detector? You're only messing with this line correct: "SPI.setClockDivider(SPI_CLOCK_DIV64)"
I am just doing what Nick tells me to , but I dont know what I am doing.. So I dont understand this, Sorry
Answer to Lefty:
Did you make sure the baud rate value for the serial monitor (lower right menu) is set to the same value as Nick's board detector sketch is using?
OK, This I understand, but where do I find those values? Lower right menu, where?
Will You please guide me here?
bobbele:
Yes! Yes I found it XD. I was searching and looking for days now.... everywhere but in the serial monitor itself.
I used the serial monitor before in several sketches, it always worked fine without changing anything.
Thanks very mutch for your reactions.
Bob
Every running sketch using the serial USB will have a Serial.begin(xxxx); statement usually in it's setup function, where xxxx is the baud rate the sketch will be using when communicating to and from the PC.
The serial monitor of the IDE has no way of knowing what value the sketch is using so it's up to the user to tell the serial monitor what baud rate to use. The serial monitor will 'remember' whatever value you last set it at when you run it again, but that might not be correct of the next (different) sketch you upload and run.