View allAll Photos Tagged debuging
These gestures are generated by a software program, creating a sort of idealized and synthetic paint. This set shows the splines and curve interpolation used to generate the forms.
How to debug a C/C++ program with Nemiver debugger
If you would like to use this photo, be sure to place a proper attribution linking to xmodulo.com
Busted URL's suck
Damn link in the article , Simplicity is broken. I hate this becuase the link that's broken (or missing) is always the one you want to read.
It's interesting because I know Joel runs Citydesk in debug mode. So if the app was checking the links it would have been noticed. Citydesk is a solid product (way back when it was a new product I gave it a severe bashing and it came out trumps in every department.. even sent back some improvements which they took aboard and improved beyond what I suggested.) but it looks like Citydesk does not have a link checker.
Link rot is a minor problem, but it is annoying to users who digest sites. As developers this is solvable. Especially for links on your own site.
Django URLField
One nice thing I found with django is the URLField type that checks the existance of an url at the time you associate data with the field (AFAICT), You still have to regularly check for link rot with link checking tools.
We had a bit of a sticky job this afternoon trying to tune a load of radio microphones.
We've got a school production coming up in December. Do you remember when to get cast in a school production you needed a loud voice? Not any more! This production requires the use of all ten of our headset microphones.
Five are working well, one has a dodgy PSU on the receiver which shouldn't be hard to replace, but four of them are giving us real headaches, and we're suspecting some kind of RF interference, or knackered transmitters.
One thing that does make our life easier is this very useful stage box which runs on a digital snake.
Using the AES50 protocol, this box connected 16 XLR inputs and 8 outputs through one Cat5 cable to the mixer at the back of the room. This is really useful, as trying to drag big XLR bundles across rooms is a pain. The AES protocol doesn't use standard ethernet packets and can't be routed through conventional routers and switches. That's not really a problem in the theatre context, where direct patches are easier to manage.
finally debugged the code, freakin 2150 lines of ASM and it turned out to be a stupid CARRY bit, which was screwing up the setpoint display, but only when messing with the menu buttons.
Phew, I'm glad to have this done. Next step is pump control...
The chipKIT™ Uno32 is a prototyping platform that adds the performance of the Microchip® PIC32 microcontroller. It features a USB serial port interface for connection to the IDE and can be powered via USB or an external power supply. To download the IDE, please visit www.chipkit.net/started
The Uno32 board takes advantage of the powerful PIC32MX320F128 microcontroller. This microcontroller features a 32-bit MIPS processor core running at 80 MHz, 128K of flash program memory, and 16K of SRAM data memory.
The Uno32 can be programmed using the Multi-Platform Development Environment (MPIDE). In addition, the Uno32 is fully compatible with the advanced Microchip MPLAB® IDE and the PICKit3 in-system programmer/debugger.
store.digilentinc.com/chipkit-uno32-basic-microcontroller...
Right extruder prints fine. Left extruder (the Inverted stepper one) prints too little plastic at the bottom and too much plastic on top of my Aztec Pyramid test.
Feels like a firmware bug.
Update: Turns out this was caused by a sticky filament spool.
Could this be any less helpful? Google found a really good document on debugging debugger problems, but it's not in there.
And, obviously, clicking Help tells me that help isn't installed. Nice. Bloody Visual Studio.
AAAAARGH!
Learning a new word every day, from the debugger this time! ^_^
(since I had a power outage this week, my fileserver refuses to rewrite the parity on the raid-array... (which it wants to do because the filesystem was shut down unclean). It simply stops rewriting and hangs... not good. Here I removed a drive from the raid1-array and wanted to add it again so it would rebuild to that drive, but well, it rather stays quiet as you can read... ;-))
My maternal grandfather was a service engineer for Allis-Chalmers from approximately WW2 until the early 1970s, and this involved flying to various customer sites to debug A-C machinery.
Various customer sites everywhere except maybe the poles, and this included at least one trip to Peru, where he got a rug that we assumed was made of pieced together furs. I don't know exactly when he make the peruvian trip, but I remember this rug sitting in the basement den of their West Allis house from as early as I can remember things.
Well, eventually my grandparents all died, and this rug ended up in my mother's hands, where it hung on the wall for many years until it got (what we thought was) a little moth-eaten and was taken down for repairs, only to be forgotten until today when I cleaned out the closet it was stored in.
When I saw it, it was covered with dust, so I picked up and gave it a vigorous shake only to discover that it was NOT pieced together furs, but hides that had appropriately dyed fur glued to it. Glued to it over 50 years ago, so it wasn't so much /glue/ anymore as powder, so the shake resulted in an explosion of fur all over the room it was in.
I can't fix this (well, I *could* fix this in a perfect world where I wasn't constantly fighting depression or wasn't 60+ years old, but this ain't that world) so I'm afraid we're going to have to toss it in the bin.
This is as annoying to find out as it was to discover that 578 was scrapped after the enthusiast who bought it from the Brillion & Forest Junction lost interest.
Damnit.
webcam image with stk11xx driver and 05e1:0501 device.
Image of white paper, please notice the blue line at the top (it should not be there).
How to debug a C/C++ program with Nemiver debugger
If you would like to use this photo, be sure to place a proper attribution linking to xmodulo.com
Enabling PWM for the backlight pin seems to mux *all* PWM pins to PWM mode, which isn't good if you're using them in GPIO mode already to toggle other logic
RenderGlow = TRUE
RenderGlowIterations = 2
RenderGlowLumWeights
* X = 0.299
* Y = 0.587
* Z = 0.114
RenderGlowMaxExtractAlpha = 0.065
RenderGlowMinLuminance = 0.000
RenderGlowResolutionPow = 9
RenderGlowStrength = 0.550
RenderGlowWarmthAmount = 1.000
RenderGlowWarmthWeights
* X = 1.000
* Y = 0.500
* Z = 0.700
RenderGlowWidth = 0.000
Posted by Second Life Resident Torley Olmstead. Visit Highgate.
Here is my SGS Nanocomputer in a completed state, with an 82C51 hardware USART fitted (rear edge of the board), an updated monitor ROM (to control the USART instead of providing a software UART) and my updated utility ROM. The utility ROM provides various test facilities, and full loading and dumping of Intel hex files, as well as an interactive serial port tester and debug dumper.
Upgrading the board to use the 82C51 hardware USART was quite straightforward, though SGS went to great pains to make it as difficult as possible. The schematics deliberately omitted the USART and nearly all the interface logic to it, so I had to work out its addressing and baud rate clock circuit by probing the board. As well as this, the standard NC-Z monitor used a PIO output on the serial line for its software USART, so this output had to be disabled in order to avoid contention. Another problem is that the USART's TTL-level CTS input was wired to an undocumented pin on the serial connector, and this has to be grounded for correct transmit operation. Therefore, it is simply not possible to use the standard NC-Z monitor with a hardware USART, so an updated monitor was required. I had to completely disassemble the existing monitor, and then make all the required changes, removing the software UART and instead interfacing to the new 82C51 device.
I also revamped my utility ROM to interface to this updated monitor, and also to provide an interactive serial port tester; this was not possible with the original half-duplex serial UART in the old monitor (as you cannot transparently check for buffered serial chars while scanning the keyboard - something you can do with the hardware USART).
The board now runs blisteringly fast at 9600 baud full duplex, a 16x speed improvement on the old half-duplex 600 baud software UART
Haven't tracked down the cause of this perimeter retraction issue while printing with the latest PLA. Documenting it here for the moment.
Strange how it seems to be Z-height dependent.
Update: Turns out this was caused by a sticky filament spool.
The hard disk on Julie's old Macbook Pro died tonight (bad block right in the middle of /etc/launchd) and before we discovered this we spent a while looking for the magic command+X codes that tweak the boot sequence. Dust Mite helped, too.
Haven't tracked down the cause of this perimeter retraction issue while printing with the latest PLA. Documenting it here for the moment.
Strange how it seems to be Z-height dependent.
Update: Turns out this was caused by a sticky filament spool.
Once again, if the debug room would just let you fly . . .
This is what the other shot should have looked like but it was way beyond me.
Japanese hint book to the rescue, its just kind of grainy, that's all.
Not intending to sound like a downer (yesterday's entry wasn't particularly upbeat) but today was spent debugging code we hoped to release today. We found a very interesting problem that has us stumped. This is as much joy as we could find.
Thanks to Mike for modeling. In truth, after the shot, we were laughing.
This is my "Joy" entry to the 2009 Photo Challenge hosted by photochallenge.org.
How to debug a C/C++ program with GDB command-line debugger
If you would like to use this photo, be sure to place a proper attribution linking to xmodulo.com
After some adventures in debugging all of the parts on the PC board are cooperating nicely, and I have started on the code. As it turns out the edge sensors have a VERY narrow adjustment band, which is a challenge. Still, I have the initial version running, detecting the edge of the ring, and successfully staying inside.