We are actively looking into website issues. You may encounter degraded performance on the site as we perform maintenance. Thank you for your continued patience!
Track My Order
Frequently Asked Questions
International Shipping Info
Mon-Fri, 9am to 12pm and
1pm to 5pm U.S. Mountain Time:
Chat With Us
February 20, 2007
about 6 years ago
Any chance you would offer spare probes separately (digital and analog)?
about 7 years ago
For info: It seems the provided source does NOT match what is flashed in the current batch of uLogs. I.e, the device works fine if you use it as is, but just recompiling the provided source and flashing the logger gives faulty operation. Logging works, but readback doesn’t, so it’s mess if we want to change something in the code as we don’t have a working starting point, and firstly have to debug code that should work in the first place before being able to work…
I checked the serial signal with my new Logger and found that for some reason the baudrate (defined by bitwidth) was too far off the 38400 mark (about 37000), so even if the logger actually sent the correct data, the receiving device wouldn’t receive it properly. A device with originally loaded firmware yielded about 39000bps, which is closer, and gives proper operation.
To solve this, replace delay_us(24); by delay_us(23); in getc() and putchr(), and delay_us(36); by delay_us(35); in getc().
Apparently sparkfun “corrected” this for production, but didn’t update the source file on this page.
When it flashes every second, it’s currently logging. To communicate you need to power it off, connect the serial port to a computer for example, and power on. It will detect it’s connected and go into command mode. A high impedance connection like a scope won’t be detected.
No public wish lists :(
Forgot your password?
No account? Register one!