Pic 18f Usb

[kirtcathey]

I want to use EasyHID, so purchased Microcode Studio about one week ago. Since then, Mecanique has not responded to two emails, I cannot find where to download EasyHID, and am at a loss. Have since sent a complaint to WorldPay and have requested a refund... just in case.

Where can one get hold of a copy of EasyHID? Or, are there other solutions out there, so I don't have to beg for the software from some vendor?

Is Mecanique going out of business? Why doesn't anybody respond?

[Archangel]

Is Mecanique going out of business? Why doesn't anybody respond?

Holiday season many businesses are closed. Try again Monday.

[Darrel Taylor]

EASY ....

Down boy, down ... That's better.

David is a busy man.
With MicroCode Studio, the PROTON IDE, Swordfish Basic, and others, the poor guys got his hands full.
Please don't report him to Internet squeelers.

Be nice, ask real questions ... he'll get back to you.
<br>

[kirtcathey]

Thanks again Darrel. Okay, I can understand that situation very well, since I tend to be a one-man band. However, it seems like with that much going on, he'd hire a spare geek or two to handle the front end.
Getting back to the subject....

I am building a proof-of-concept prototype (aren't we all!!) that will sit between the keyboard and host. When the end-user types in a certain character string or key combination, the microcontroller will send a control signal to another receiving device to start and stop a motor. Should I make this a keyboard HID, a generic device HID, or none at all and somehow pull information off the wire?

Regards,
Kirt

[Demon]

....

I am building a proof-of-concept prototype (aren't we all!!) that will sit between the keyboard and host. When the end-user types in a certain character string or key combination, the microcontroller will send a control signal to another receiving device to start and stop a motor.

...

What micro-controller will you use? Last I heard (maybe over a year ago), the PIC could not act as host to a USB device. Has a new model been released?

Robert

[kirtcathey]

Robert,

Thank you.

I'm using an 18F2550, since it's only 28 pins. Yes, I understand that it cannot be a USB host, which is why I am at a loss. What I am doing right now with somewhat positive results is programming for a keyboard device, then plugging the straight-wiring the keyboard to the host, then pulling power and data taps to the PIC. All is recognizing fine, except am working on finding the right host driver for this funky keyboard.

Going to catch a train to Akihabara in a few minutes to pickup a generic USB keyboard and some other stuff.

[Demon]

Robert,

Thank you.

I'm using an 18F2550, since it's only 28 pins. Yes, I understand that it cannot be a USB host, which is why I am at a loss. ...

Courtesy of Mister E, check out the PIC24 et PIC32 family.

[kirtcathey]

Somebody at Mecanique was kind enough to get Microcode Plus to me so that I can now use EasyHID, but it doesn't work. I fo through all the dialogs, then in the last dialog I get Generation Error: Unable to locate device item.

After reading other posts, I paid careful attention to the mfr name and product name, making sure there were no special characters. Am trying to create a USB device with an 18F2550,

Any help is appreciated.

[Demon]

[QUOTE=kirtcathey;68507]
...

All is recognizing fine, except am working on finding the right host driver for this funky keyboard.

...QUOTE]


Something tells me this might be a case of RTFM. When you say "funky keyboard", do you mean an uncommon keyboard that will run separately from the USB/PIC device? Or are you referring to the USB/PIC device itself?

If you are referring to a keyboard not known by your operating system, I fail to see how Mécanique can be held accountable. But if you are referring to a custom PIC/USB device, doesn't EasyHID generate the code for the PIC as well as the code for the PC (driver)?

I haven't used EasyHID in a long time, I've been using another USB code generation software so I might be getting them confused.

[kirtcathey]

Finding the right driver for the keyboard is irrelevant to EasyHID functioning or not. And I have USB devices working without EasyHID, but do not have EasyHID working. The keyboard issue was resolved minutes after that post. Please do not mix and try and match issues - RTFposting history - my questions about EasyHID have nothing to do with keyboards. Is there a manual, besides the cursory online help that offers no troubleshooting pointers, for EasyHID?

And no.... EasyHID is now only available with the plus version of MCS. When you run it all the way to the end without the plus version, it says that it cannot find the device and that you have to upgrade.

The unspoken truth about this matter, is that I have to resort to a forum to see if anybody knows what is going on.... or try and resolve this matter....

I am selecting PicBasic Pro as my compiler, since that is the only thing available on the pull-down. Is this okay? Or, should I be selecting MPASM, which is not an available choice?
Does the device need to be in the programmer and recognized before running EasyHID? Do I need to have the ICD working? Do I need to have MS VC++ or Delphi installed on the same system that will run EasyHID? Any help would be appreciated since I cannot rely on the software vendor.

Robert Quote
But if you are referring to a custom PIC/USB device, doesn't EasyHID generate the code for the PIC as well as the code for the PC (driver)?
End Quote

No. I need the PC side of the code and I want/paid for EasyHID to do it. No. EasyHID does not work as described in previous posts.

[Darrel Taylor]

I should mention that EasyHID comes with MicroCode Studio.

It's located in the "C:\Program Files\Mecanique\MCSP\EasyHID" folder. (assuming default installation).

In that folder, there is a file EasyHID.chm.
Should answer most of your questions.

[kirtcathey]

Right. And after reading a bunch of posts on these forums (many by you) about it... I want it even more! Or, do I? I am thinking that things may work out with just a generic keyboard HID for the time being, but not sure.