Skip to main content


This section allows you to view all Topics made by this member. Note that you can only see Topics made in areas you currently have access to.

Topics - cuagn

General discussion / Flatcam
I've bought a Chinese CNC a couple of months ago, and I was still looking for the "god link" between Gerber/Excellon files (Kicad output) and the G-Code driver.
An open source solution is on the build by JC Caram.
It's Python based and is working fine even if some improvements (goodies)  may be required.
Have a look here :


General discussion / Gerber to HPGL converter
I’ve already asked this question somewhere, may be in another forum, but I didn’t receive any operational answer (just the one like “Google is your friend…”)

I'm a pure hobbyist player. (Ham radio). I started designing PCB many (many) years ago, using MSDOS tools with a HPGL plotter and the result was good enough. Then I moved to Windows, and my outdated former solution was no more working.
The basic free solution I'm still using is ExpressPCB, with a laser printer.
Quick, simple, free but very specific and not used by hobbyist communities. 
More, the laser printing, and by the way the final result, is not as good as expected (like a HPGL plotter is).

Now, it's time to move to Eagle, in order to have a real PCB design capability.

However, Eagle also (as far as I understand, but I may be wrong) doesn’t enable a HPGL output.

I’m quite sure that someone, somewhere has written a good Gerber to HPGL translator.
At least for basic PCB this may be fine for prototyping.

Does somebody have successfully tried a such converter? Which one?

Thank you

Bus Blaster JTAG debugger / [resolved] Some questions with OpenOCD / Win7
Situation before
I’m working under Win7 Pro.
I’m also owning a DP FT2232H breakout board.
By the way the initial situation is that default FTDI drivers are installed on my computer, either for my old FT232HL serial converter or for the FT2232H dual converter.

Nota : I use USBDeview (see here) to get a synthetic view of the USB environment on my PC. A nice freeware!

All devices with VID=0403 (FTDI)

I’ve 3 virtual COM ports when I look to Device manager (click to see the screen copy)
That’s normal!

More details thanks to USBDeview:

Generic Microsoft parent for FT2232H (click to see the screen copy)
Interface A (click to see the screen copy)
Interface B (click to see the screen copy)
Serial converter FT232HL (click to see the screen copy)

Everything is working fine…

The issue…

I’ve received my DP BusBlaster (V2.0a) a couple of weeks ago.
Need first to adapt connectors to try to de-brick a Dockstar (Seagate Pogoplug) device and I decided to go with OpenOCD.
I installed the required USB environment, according to the WIKI setup

1. Install a driver (libUSB)
2. …

So did I, using the libusb documentation here.
The last version is (dated April 12th). See here.

“Starting from version, the inf-wizard.exe has embedded driver binaries and provide an option to install the driver at the end of the process.”

Fine, a few clicks and the driver is installed for both interfaces of FT2232H.
Interface 0 (click to see the screen copy)
Interface 1 (click to see the screen copy)

This is confirmed by testlibusb (click to see the screen copy)

Looking to Device Manager, I’m not happy however: the corresponding virtual ports have disappeared.

Note : the drivers are in a specific libusb-win32 devices group.

Which means that I can’t use the DP FT2232H breakout board.

But what about OpenOCD?
Just download (here) and install it…

The first strange and contradictory information is :

“OpenOCD 0.4.0 for Windows. An msi installer of complete package and it's md5 checksum. Due to alleged GPLv2 license incompatibility of using ftd2xx.dll libraries, this version was compiled to use libftdi + libusb-win32 libraries.”

Hmmm. DP wiki says that libusb is required but OpenOCD says that libftdi is required too.
What about libftdi?

As a result of the OpenOCD installation, a libftdi.dll and a libusb0.dll are included in the same directory of openocd.exe.
Fine, but this libfdti.dll may be a little old.
Let’s go here
Last version is from yesterday : 2011-05-23: Version 0.19 of libftdi released
No libftdi.dll is included and I did not find a way to generate it.

The good point is that at the end, I start openocd which seems to work (even with some difficulties at this time, but on the board side, ie. Dockstar)

Questions :

1 - I’ve lost the virtual ports for all the VID=0403 PID=6010 devices. How to fix this issue ?
2 – How to run with the last libftdi under windows ?

I may have some wrong understanding, but up to now, I do not find how.

Any idea ?

Open Bench Logic Sniffer / I'm lost in a basic testing
I've both devices, a Bus Pirate and an OLS.

In order to test (me and the OLS) and to understand the right parameters for the Sump client, I'm using the signal generation of the BP (1Khz-50%).
I monitor it with a real scope, no problem signal is delivered.
Then I'm trying (expecting) to have the trace in a Sump capture.

As it is a single basic signal input it should be simple.

That's not the case. I've a lot of glitches and wrong samples on all entries, and whatever the input port used (0-15), I'm not able to trace a 1KHz-50% signal... :(

Questions : what should be the parameters for the Sump capture ? Has anybody done a such basic test ?

USB Infrared Toy / Compiling the FW
Because before hacking it's better to just rebuild "as is", I've tried to recompile the FW.

After downloading, I've unzipped it.

The source directory is named : IRtoy-firmware

Using MPLAB version 8.43 (the last one is 8.46) I load the USBIRToy.mcp

As expected, some files are missing, and an attempt to build the FW gives the following errors
Code: [Select]
Error: File "D:@ElectroniqueIR toolUSBIRtoyIRtoy-firmware..MicrochipUsbusb_device.c" not found.
Error: File "D:@ElectroniqueIR toolUSBIRtoyIRtoy-firmware..MicrochipUsbCDC Device Driverusb_function_cdc.c" not found.
Error: File "D:@ElectroniqueIR toolUSBIRtoyIRtoy-firmwareusb_descriptors.c" not found.

Question : I suppose that these 3 files are the one we should download from the Microchip web site...

Let's do it. There is a big (very big) zip file named MCHP_App_ Lib v2010_02_09_Installer.
Which delivers (default) a big amount of directories and files in c:Microchip Solutions

There are a lot of USB related files.

Question : Where are the required one

Am I right (up to now)?
USB Infrared Toy / Driver under windows 7 (resolved)
I plug USB IR Toy in my Desktop (windows 7 x64).

Driver installation fails :
Code: [Select]
USBIRtoy (CDC-232) - No Driver found

I start USB-view and get the following information.

Code: [Select]
Device Descriptor:
bcdUSB:             0x0200
bDeviceClass:         0x02
bDeviceSubClass:      0x00
bDeviceProtocol:      0x00
bMaxPacketSize0:      0x08 (8)
idVendor:           0x04D8 (Microchip Technology Inc.)
idProduct:          0xFD08
bcdDevice:          0x0100
iManufacturer:        0x01
iProduct:             0x02
iSerialNumber:        0x00
bNumConfigurations:   0x01

ConnectionStatus: DeviceConnected
Current Config Value: 0x00
Device Bus Speed:     Full
Device Address:       0x03
Open Pipes:              0

On Microchip site, it is said that the driver corresponding to the 18F2550 is included in the OS distribution.

OK, solution found...

I just forget to get .inf file from
Then, update the (nonexisting) device driver, using the released .inf
Driver is now OK

And USB view says :
Code: [Select]
Device Descriptor:
bcdUSB:             0x0200
bDeviceClass:         0x02
bDeviceSubClass:      0x00
bDeviceProtocol:      0x00
bMaxPacketSize0:      0x08 (8)
idVendor:           0x04D8 (Microchip Technology Inc.)
idProduct:          0xFD08
bcdDevice:          0x0100
iManufacturer:        0x01
iProduct:             0x02
iSerialNumber:        0x00
bNumConfigurations:   0x01

ConnectionStatus: DeviceConnected
Current Config Value: 0x01
Device Bus Speed:     Full
Device Address:       0x03
Open Pipes:              3

Endpoint Descriptor:
bEndpointAddress:     0x82  IN
Transfer Type:   Interrupt
wMaxPacketSize:     0x0008 (8)
bInterval:            0x02

Endpoint Descriptor:
bEndpointAddress:     0x03  OUT
Transfer Type:        Bulk
wMaxPacketSize:     0x0040 (64)
bInterval:            0x00

Endpoint Descriptor:
bEndpointAddress:     0x83  IN
Transfer Type:        Bulk
wMaxPacketSize:     0x0040 (64)
bInterval:            0x00


I've connected  to my Laptop (Linux, last Debian).
Seems OK, but I want to work in Windows :(
Code: [Select]
[  409.172048] usb 2-2: new full speed USB device using uhci_hcd and address 3
[  409.364133] usb 2-2: configuration #1 chosen from 1 choice
[  409.375668] usb 2-2: New USB device found, idVendor=04d8, idProduct=fd08
[  409.375677] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  409.375681] usb 2-2: Product: USBIRtoy (CDC-232)      
[  409.375685] usb 2-2: Manufacturer:
[  409.607277] cdc_acm: This device cannot do calls on its own. It is no modem.
[  409.607426] cdc_acm 2-2:1.0: ttyACM0: USB ACM device
[  409.611057] usbcore: registered new interface driver cdc_acm
[  409.611066] cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters