I have a K8055 and a K8055N. They both work with either a PIC18F2550 or a PIC18F25K50. They can do a bit more than the original, like controlling standard servos on the 8 digital outputs or counting frequencies up to 2 kHz on all 5 digital inputs.
All the software for that, the firmware and the DLL, are open source. You have the links to that already.
OpenK8055 is a very good project, I would not reinvent the wheel if you do not have the basic knowledge.
I would not reinvent the wheel if you do not have the basic knowledge.[/quote]
hhhhhhaaaaahhhhhhh.
do not Worry dear these fourm to understand and to Discussion.
beast regard
[quote=“ruf”]
hhhhhhaaaaahhhhhhh.
do not Worry dear these fourm to understand and to Discussion.
beast regard[/quote]
You seem to grossly underestimate the complexity of something like this. Building a USB device has 4 moving parts.
[ul][li]Part one is building the hardware, that can actually run a PIC. For PICs that require an external crystal oscillator, this will not work on a breadboard setup, since the wires introduce any amount of unknown capacitance. You definitely need a properly designed PCB for that. Fortunately, we have the P8055-1 or P8055N-2 board, so that’s taken care of.[/li]
[li]Second you need a firmware for the PIC that controls the IO ports and communicates via packets on the USB. Have you ever created such firmware?[/li]
[li]Third you need a DLL that implements function calls that represent functionality of the USB device, like turning an output on/off or reading an input. That DLL will translate between those function calls and sending/receiving the USB packets to/from the device. Obviously you don’t know how to implement this, because that was your original question.[/li]
[li]And fourth you need an application program that is interacting with the user (you) and translating the user input/output to those DLL calls. How good are your application development skills?[/li][/ul]
If you have never done ALL of the above, it is extremely hard to start from scratch. A single mistake in only one of those four, interrelated problems, will make the whole chain fail. But it is difficult to isolate which part has failed.
I am doing these things for over 30 years now. I have built my own circuits, programmed early microcomputers (6809, 8080 and Z80 CPUs, and even 370 Mainframe computers in Assembler). I have fixed bugs in UNIX kernel device drivers and written thousands of lines of C code in database server backend code as well as client applications. This is why I can develop all of these things myself. Very few people can do this.
It is a lot easier and far less frustrating if you start with a working example, and then try to change/improve/replace one component at the time.
Do yourself a favor and start by getting the Open8055 stuff running on your K8055. Then take it from there by modifying one bit at a time.
[quote=“MostlyHarmless”][quote=“ruf”]
hhhhhhaaaaahhhhhhh.
do not Worry dear these fourm to understand and to Discussion.
beast regard[/quote]
You seem to grossly underestimate the complexity of something like this. Building a USB device has 4 moving parts.
[ul][li]Part one is building the hardware, that can actually run a PIC. For PICs that require an external crystal oscillator, this will not work on a breadboard setup, since the wires introduce any amount of unknown capacitance. You definitely need a properly designed PCB for that. Fortunately, we have the P8055-1 or P8055N-2 board, so that’s taken care of.[/li]
[li]Second you need a firmware for the PIC that controls the IO ports and communicates via packets on the USB. Have you ever created such firmware?[/li]
[li]Third you need a DLL that implements function calls that represent functionality of the USB device, like turning an output on/off or reading an input. That DLL will translate between those function calls and sending/receiving the USB packets to/from the device. Obviously you don’t know how to implement this, because that was your original question.[/li]
[li]And fourth you need an application program that is interacting with the user (you) and translating the user input/output to those DLL calls. How good are your application development skills?[/li][/ul]
If you have never done ALL of the above, it is extremely hard to start from scratch. A single mistake in only one of those four, interrelated problems, will make the whole chain fail. But it is difficult to isolate which part has failed.
I am doing these things for over 30 years now. I have built my own circuits, programmed early microcomputers (6809, 8080 and Z80 CPUs, and even 370 Mainframe computers in Assembler). I have fixed bugs in UNIX kernel device drivers and written thousands of lines of C code in database server backend code as well as client applications. This is why I can develop all of these things myself. Very few people can do this.
It is a lot easier and far less frustrating if you start with a working example, and then try to change/improve/replace one component at the time.
Do yourself a favor and start by getting the Open8055 stuff running on your K8055. Then take it from there by modifying one bit at a time.[/quote]
I really appreciate your interaction and the way your education
you charming me.
Which makes me try hard learning from you I hope you have a mind is not.
where you thik of these 18f4550.com/????
I think that this has nothing to do with Velleman kits.