Company policy is that the computers used for product development may not be connected to the Internet. There are very good reasons...I am sure that you understand.
Allow me a few minutes to extract the code that is in question, run it on my 40 pin DIP breadboard, and post the code for you to compile and run.
I extracted only the code that is necessary to start and run the Zaxis COG and placed that code in a TEST program. Outputs P(9), P(10), P(11), and P(12) toggle perfectly. There is no problem here.
The only instruction in the main() is cogstart.
There is a change in planning. I will begin to add back pieces of the full blown operating program until the problem shows again. This process should identify the culprit.
All the code that generates the stepper motor signals was successfully inserted into a test program. All twelve output signals are correct and stable. All COGs are working properly on the Propeller Activity Board.
More system control code will be inserted tomorrow...hopefully the problem will be found.
Even though the code compiles correctly and runs properly...the compiler generates a lot of warnings.
I decided to clear out all these warnings before adding more control code to the program. Since I am a novice at "C" language programming I figure that eliminating the warnings would insure that the code is free of any ancillary effects. This proved not to be the case,
.
Somewhere in the process of inserting void where it was left out caused several of the square wave signals generated in COG#1 to stop being generated.
interesting problem; I have had experiences with this in other boards; Grounding issues
and connection problems. If you used this pin for driving alot of other devices, it may have
affected your fanout capability. I would suggest putting an optocoupler on the pin to drive
your devices. (I have used a window comparitor, to sense high or low, then drive the opto
accordingly. Also avoids noise, and takes a load off of the pins.)
If the problem can not be found, It may be a good idea to let Parallax have it for failure
analysis, if you can not use it. Good luck!
Comments
Allow me a few minutes to extract the code that is in question, run it on my 40 pin DIP breadboard, and post the code for you to compile and run.
Sincerely,
Discovery
I extracted only the code that is necessary to start and run the Zaxis COG and placed that code in a TEST program. Outputs P(9), P(10), P(11), and P(12) toggle perfectly. There is no problem here.
The only instruction in the main() is cogstart.
There is a change in planning. I will begin to add back pieces of the full blown operating program until the problem shows again. This process should identify the culprit.
Sincerely,
Discovery
More system control code will be inserted tomorrow...hopefully the problem will be found.
Sincerely,
Discovery
I decided to clear out all these warnings before adding more control code to the program. Since I am a novice at "C" language programming I figure that eliminating the warnings would insure that the code is free of any ancillary effects. This proved not to be the case,
.
Somewhere in the process of inserting void where it was left out caused several of the square wave signals generated in COG#1 to stop being generated.
This issue is being addressed.
Sincerely,
Discovery
and connection problems. If you used this pin for driving alot of other devices, it may have
affected your fanout capability. I would suggest putting an optocoupler on the pin to drive
your devices. (I have used a window comparitor, to sense high or low, then drive the opto
accordingly. Also avoids noise, and takes a load off of the pins.)
If the problem can not be found, It may be a good idea to let Parallax have it for failure
analysis, if you can not use it. Good luck!
Discovery