I keep myself away from the hardware guys because it's normal that it takes many iterations to reach at the final design but still if something require revisit then the blame game starts as to who is responsible for this mistake and a software person is a convenient scapegoat for them. In projects were I do both things, I allways have the PIC datasheet at hand during the routing process, and usually there is some (a lot), adjustements on the initial pin assignement to sort out routing problems. There are many different processors to choose from and they have widely varying pinouts and functionality.īesides that the PIC I/O can be mapped, either PPS or simple code changes, so its important for the firmware developer to be in close contact with the PCB designer. JorgeF Hi PStechPaul The hardware design usually must be done in close collaboration with the software engineer. Thanks a lot for your very helpful starting point and over-all code architecture. You do see how your very basic questions make people nervous since this is an item that can kill people if it malfunctions. this can take as long as the codding, maybe more in this case. If you are in a country with a safety code you will need to document and have your code approved. on some systems if all the calls are done the car will go to the Lobby floor, other wise it will stop and wait for more calls. it will repeat this until there are no more calls. when it finishes one direction, it will either stop or reverse in to other direction.

as more calls are added the car will decide if it needs to stop at a floor. the elevator is started in the correct direction. so step one is to scan all you switches to look for button presses. assuming 12 floors (1 call button per floor, or an up and a down?) 12 floor buttons in the car. NKurzman You need to first figure out how you elevator works.

What is altium designer elevator