I got the cognew blues!

Comments

• Microcontrolled Posts: 2,461

  2010-04-01 20:34 edited 2010-04-01 20:34

  You are only declaring pins 7..7 (that would be just 7) outputs and then outputting on pins higher then that. The default is input. If you would have it repeating a
  
  dira[noparse][[/noparse]pin]~~
  
  with every repeat loop in the BlinkLed PUB then it should work.
  
  ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
  Don't click on this.....
  
  Use the Propeller icon!!
  
  You had better not start ANOTHER PropII thread.
• Thomas Fletcher Posts: 91

  2010-04-01 20:43 edited 2010-04-01 20:43

  Man, you guys are fast. That fixed it. Thanks. Weird. I thought it
  was something to do with cognew and I was looking in the wrong
  place all afternoon.
• kuroneko Posts: 3,623

  2010-04-02 01:19 edited 2010-04-02 01:19

  Thomas Fletcher said...
  I thought it was something to do with cognew and I was looking in the wrong place all afternoon.

  In a way it was. You defined dira behaviour for the main cog (which exits after cognew). The cog started by cognew needs its own dira/outa setup.
• Microcontrolled Posts: 2,461

  2010-04-02 02:01 edited 2010-04-02 02:01

  Good! This is the first time that my advice has worked!
  
  I must say that I would have never thought of this exept that I, too, have run into this problem multiple times, mainly forgetting the dira all together!
  
  ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
  Don't click on this.....
  
  Use the Propeller icon!!
  
  You had better not start ANOTHER PropII thread.
• Phil Pilgrim (PhiPi) Posts: 23,514

  2010-04-02 03:14 edited 2010-04-02 03:14

  Eh, no. The point that kuroneko was making is that dira was set in the top level cog, but that those settings have no effect whatsoever in another cog. Each cog has its own dira register and, to create an output in any cog, it's own dira bits have to be set for the output pins.
  
  -Phil
• Sariel Posts: 182

  2011-06-21 10:15 edited 2011-06-21 10:15

  I am having a hard time wrapping some concepts up in my head, and I was hoping that someone could lend a different explanation to me. It is along the lines of:
  

  those settings have no effect whatsoever in another cog.

  
  here is the scenerio:
  Top file runs in cog 0, and that calls the cog start method in "Object A"
  "Object A" in it's init, starts cog1 with an infinite loop.
  Later on, Top file needs "Method Z" from "Object A". Method Z is not used by the infinite loop in cog 1.
  
  I am just about positive that the infinite loop will not prevent this from happenening. If this the case, does it run "Method 1" in cog 0, or would it run it in cog 1, interrupting the loop?
  
  I really hope that made sense to everyone. If not, I can try to re-phrase it.
• Ariba Posts: 2,694

  2011-06-21 11:14 edited 2011-06-21 11:14

  Hello Sariel
  
  Yes, you can call your MethodeZ in the sub-objectA. It will run in Cog0, if called from the Top object. You can the same methode also call from your "infinite cog1 Loop", then it will run in cog1. It's the Spin interpreter in a cog that decides in which cog a methode is executed and not the methode, or the object.
  
  Hope this helps
  
  Andy
• Sariel Posts: 182

  2011-06-21 11:51 edited 2011-06-21 11:51

  Ahh. gotcha. I thought that was how it went, but I could not be sure. Good to have someone verify this a little for me. THank you.
• Microcontrolled Posts: 2,461

  2011-06-21 12:03 edited 2011-06-21 12:03

  This thread is a year old.