Interfacing the PIC to a computer

Status
Not open for further replies.
I don't think we should even think of using PCI for this application. Serial will be sufficient for few servos. We should look for the simplyest solution, not for the best looking. 8)
 

As I mentioned before, this is a VERY SLOW application, anything mechanical is going to be slow - so there's no need for incredibly fast communication between devices.

If it's taking 500mS to move the steering wheel, what does it matter if it takes 1mS or 1uS to send the information?.

'Real time' is governed by the outside world, this moves relatively slowly, PIC's and PC's both work a great deal faster - both PIC's and PC will be spending the vast majority of the time just wasting time, slowing themselves down to match the 'real world'.

I mentioned the Mythbusters car, this was radio controlled - which means that the FASTEST possible change takes at least 20mS - this makes the car drivable, and no slower than it would be if manually driven.
 
I don't think we should even think of using PCI for this application. Serial will be sufficient for few servos. We should look for the simplyest solution, not for the best looking.
Click to expand...

That's for the thread starter to decide. Let's not be too patronizing to decide what's good for him/her. Just offer what's out there and let him/her decide.
 
motion said:
That's for the thread starter to decide. Let's not be too patronizing to decide what's good for him/her. Just offer what's out there and let him/her decide.
Click to expand...

The whole point of asking for suggestions is to receive them!, if he didn't want them he wouldn't have asked!.

Building a PCI card isn't a good solution to the project as stated, so why would we suggest it was?.

Where building a PCI card (or simply buying a suitable one?) 'might' be useful is in using the PC totally to control the car - no PIC's or other controllers, everything done in the PC, and interfaced through a PCI card (or cards).
 
Where building a PCI card (or simply buying a suitable one?) 'might' be useful is in using the PC totally to control the car - no PIC's or other controllers, everything done in the PC, and interfaced through a PCI card (or cards).
Click to expand...

That is exactly what I suggested. That is why I would not rule out using PCI entirely, specially if the requirement is to use a PC.
 
I think using Paralel port of the PC would be a good compromise Between PCI and USART+PIC solution. Paralel port could controll more than 8 devices, and that would be sufficient for this project.
 
There was I time I studying ways to interface to the PC using the PCI bus and one of the things I came across was PCI card which can display the diagnostic POST codes of the PC.

**broken link removed**

I bought a sample to study and it contained just a couple of GAL chips and PIC clone chip to drive the display. You can probably implement a similar interface for your project. This card might not exactly meet the PCI bus signaling specs but if you're after a hobbyist PCI implementation, this is one idea to consider.
 
That card is just displaying POST informations that are present on the PCI bus. To make the Interface we need is harder, it will require more than GALs, you also need to write suitable driver and software for it, because that PCI card needs to communicate with CPU (unlike that POST card).
 
To make the Interface we need is harder, it will require more than GALs, you also need to write suitable driver and software for it, because that PCI card needs to communicate with CPU (unlike that POST card).
Click to expand...

Of course it's harder but I am just pointing out the possibilites. Anyway, I think reading from the card shouldn't be too much harder than writing from it, unless your mind is already closed to that idea.
 
As I said, the POST card is just showing what's happenning on the PCI bus. It has no connections to the CPU or memory. And it is gonna be VERY difficult to start building such a special card from scratch. There is no difference between reading and writting, main problem is just to make it work with all the IRQs, DMAs, Addresses, BIOS and OS.
 
motion said:
Of course it's harder but I am just pointing out the possibilites. Anyway, I think reading from the card shouldn't be too much harder than writing from it, unless your mind is already closed to that idea.
Click to expand...

Jay is right. The PCI interface part would make your entire project look like child's play. Most of the customised interface cards require at least a CPLD, not to mention a customized kernel driver. And those who have written drivers before should understand that it's one of the most difficult aspects of PC programming. I don't know about Linux drivers, but at least for WDM drivers, it's hell.
 
Finally somebody understands how difficult PCI really is...
 
I would avoid PCI for more reasons than I care to count.

For starters, if this is supposed to be mounted in a vehicle, why not use a laptop instead of a desktop machine? Going the PCI route would prevent that flexibility in the future. Of course modern notebooks have mini-PCI, but the physical connectivity is completely different.

Dan East
 
Dear everyone,

After carefully reading all your suggestions and recommendations, my partners and I are now seriously considering the serial port solution instead of going for the PCI. Not that we don't like challanges, but the project itself is huge enough that we need to find easier solutions for some of its parts. But I was wondering:

Would it be difficult to set the baud rate under linux?

What is the longest possible time that it could take for 3 bytes to reach 3 different PICs from the PC through the serial port and also for about 4 bytes to reach the PC from the PICs assuming that I will use a master PIC to receive the bytes from the PC and then distribute them to the other PICs and the same PIC to take the bytes from the other PICs and send them one by one to the PC as well?!
I'm not sure about the most suitable baud rate and the PICs available are the 16F628, the 16F876, and the 16F877.
Thanks.
 
I can assure you, that it's a very short time, for example if BaudRate is 9600, than it takes about 3.1 mS, that's pretty short. And with Baudrate of 115200 it takes 0.26 mS...
 
Status
Not open for further replies.

Similar threads

F
  • Question
Issue with Interfacing LCD with PIC16F877A
2
Replies
22
Views
3K
Farhaad
F
reverse engineer calculator to update the constants.
2
Replies
21
Views
4K
ZipZapOuch
  • Question
How to find the direction of target in complex environment?
Replies
7
Views
3K
sk001
D
  • Question
How to create a Bitmap For a Dinosaur using PIC16F877A
2
Replies
33
Views
6K
Tocaboca
T
A
  • Question
MSP430G2553 issue in Transistor interfacing
Replies
14
Views
2K
danadak
Menu
Log in
Register
Cookies are required to use this site. You must accept them to continue using the site. Learn more…