Hi Folks

quick introduction and some questions. My robot is called Kryten, after the humanoid robot in the Red Dwarf series. He is pretty much build standard Gael, with the addition of the articulating stomach.

he stands on a manequin leg set liberated from a local department store, which makes him, ohh, about 6 foot 8 inches tall

currently the host computer is win10, with Nixie 1.1.16178093 running 2 arduino megas

am at the point where I am doing test runs and am running into a few anomalies.

if I set ScriptType=Virtual, in the _InMoov.config file, the chatbot remembers the robot name and my name, every time I set ScriptType=Full, it insists its the first time it runs and wants to know what the robot name is, to name a few. set Full back to Virtual, reboot, and it knows all these facts again. 

question: why should it matter if the robot is in Full or Virtual mode, and where is the flag that signals First Time run??

when I start in Full, and have isHeadActivated= True in skeleton_head.config. when the head services start, the head.neck and the head.rothead services show they are attached, but i can't move them with the sliders. If I detach, and re-attach, then stop and start the head.timer , these servos will spring to life. sometimes I have stop and start the head timer, sometimes just stop the head timer. But i always so far have to do a detach re-attach sequence for those two servos. Yes the speed is set high enough.

Does anybody have asuggestion as to why alwasy just these two servo's?

looking for a way to test the ultrasonic sensor(s) attached, maybe a single line of py code or so. May I suggest an enhancement to the ultrasonic service in the web gui, by having a Test button, that would fire of a single measurement and display this in the web page?

even with isNeopixelActivated=False, Nixie seems to want to see something on that particular comport, mine is via USB so has a NeopixelMasterPort=COM10 entry. Should it just not care with activated set to False?

lastly, for those who have gone before me with the articulating stomach, how have you hooked the servo up? A suggestion was made to use lowStom, but currently the torso config file only has an entry for topStom and midStom, although the torso.py in the skeleton subdir does have a single small entry to set lowStom speed but nothing more. At this point I was going to add lines for lowStom in torso.py, commensurate to the lines already there for topStom and midStom. 

any pitfalls by doing this?

 

rv8flyboy

3 years 6 months ago

in the startup script there is a small error preventing copying of the log file automatically:

echo ------------------------------------------------------
echo Rotate log files for clean no worky
 
del myrobotlab.log.1 > NUL
mv myrobotlab.log myrobotlab.log.1
 
 
the last line, in windows anyway, should be:
move /y myrobotlab.log myrobotlab.log.1
 
 

 

Not sure what you are asking?

The inmoov files show up after doing the java -jar myrobotlab.jar --install. I don't know where the install script pulls them in from, they show up after clicking the install all services button

rv8flyboy

3 years 6 months ago

trying to test the ultrasonic sensor. someone suggested the phrase "measuring the distance"

tried this and did not work, found following in the log file:

08:58:38.655 [i01.chatBot] INFO o.a.a.MagicBooleans [MagicBooleans.java:47] input: measuring the distance, that: What s it like to be that way, topic: firstinit, chatSession: org.alicebot.ab.Chat@4e1a154a, srCnt: 0
08:58:38.656 [i01.chatBot] INFO o.a.a.Graphmaster [Graphmaster.java:307] Matched: MEASURING THE DISTANCE <THAT> * <TOPIC> * _inmoovGestures.aiml
08:58:38.660 [i01.chatBot] INFO o.a.ab.Bot [Bot.java:415] writeCertainIFCaegories learnf.aiml size= 72
08:58:38.661 [i01.chatBot] ERROR c.m.f.Service [Service.java:2038] i01.chatBot error could not find method ProgramAB.publishOOBText(String)
08:58:38.662 [python] INFO c.m.s.Python [Python.java:462] exec(String) 
ultraSonic("in centimeters I measure ")
08:58:38.663 [i01] INFO c.m.s.a.AbstractSpeechSynthesis [AbstractSpeechSynthesis.java:555] i01.mouth processing 
08:58:38.667 [python] ERROR c.m.f.Service [Service.java:2038] python error Traceback (most recent call last):
  File "<string>", line 1, in <module>
NameError: name 'ultraSonic' is not defined
 
08:58:38.667 [python] INFO c.m.s.Python [Python.java:557] finishedExecutingScript
 
 
 
edit:
running the one-liner in python window does produce a measurement result:
print "ultrasonicSensor test is ", i01.getUltrasonicSensorDistance()

rv8flyboy

3 years 6 months ago

Hi Folks

 

just sent a NoWorky, noticed whenever I set isTorsoActivated=True i get following error in the log file:

12:26:59.503 [python] ERROR c.m.f.Service [Service.java:2038] python error Traceback (most recent call last):
  File "<string>", line 42, in <module>
  File "InMoov/system/InitCheckup.py", line 63, in <module>
    if os.path.splitext(filename)[1] == ".py":execfile(RuningFolder+'skeleton/'+filename.encode('utf8'))
  File "C:/nixie/InMoov/skeleton/torso.py", line 42, in <module>
    torso.topStom.load()
AttributeError: 'NoneType' object has no attribute 'load'
 
This is with 'virgin' files, only change made is setting isTorsoActivated=True
 
 

 

yeah the torso explodes - this is in the noworky you posted ...
 

runtime cannot callback to listener subconsciousMouth does not exist for onStarted 
12:57:07.549 [python] ERROR c.m.f.Service [Service.java:1930] copy failed
java.lang.NullPointerException: null
	at org.myrobotlab.service.InMoovTorso.broadcastState(InMoovTorso.java:144) ~[myrobotlab.jar:1.1.300]
	at org.myrobotlab.framework.Service.startPeer(Service.java:1824) ~[myrobotlab.jar:1.1.300]
	at org.myrobotlab.framework.Service.startPeers(Service.java:1924) ~[myrobotlab.jar:1.1.300]
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:na]
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:na]
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:na]
	at java.base/java.lang.reflect.Method.invoke(Method.java:566) ~[na:na]
 


So .. I go to the InMoov folder and how exactly do I replicate what you did ? - you can use video if you want for a reply



      
    
          
  • 
      

    

  








    

  

    

      

  


    

  

  

    
    

              
        

        
            
            
Hey GroG


all i do is switch ON the torso in the torso config ( i believe in /inmoov/config/torso.config, but not home right now) by setting  isTorsoActivated=True, 


then starting with START_INMOOV.bat.  


I have not found a correlation with any other of the services, i.e., it doesnt seem to matter if I activate arms, or hands, or not, or any combination, I have not tried with the head switched off, but I would suspect it won't matter. All other services appear to start correctly.



      
    
          
  • 
      

    

  








    

  

    

      

  


    

  

  

    
    

              
        

        
            
            
Cool, this is helpful ..

	This is what you do and what you observe ..


	Now what is it that you want ?   I'm sure having no errors and control over the torso.

	But what goals or ideas do you have ?

	How do you want to control Kryten ?  How is working with the WebGui ?  and anything else you can think of ...


	BTW - we appreciate the fact you volunteered as a guinea pig ...  :)


Also to let you know .. since my fix for the simulator/JMonkeyEngine service ... I'm now currently working on the kwatter's ServoMixer - which should provide a easier way to make poses/gestures/sequences


	



      
    
          
  • 
      

    

  








    

  

    

      

  


    

  

  

    
    

              
        

        
            
            
lol, I would like the basic functionality to work


i am happy I switched from jetson nano back to win10, i would have thought these errors are Jetson induced and would have been pulling my hair out.


My goals for Kryten? I don't have a specific end result in mind, it is something to learn and tinker with. I think an interactive robot in the end, animatronics. For now, new things to learn. Would love to learn more about the programming aspect. I started working in python on the jetson nano to learn about AI. 


My daytime job is it to find out why things break, (forensics) so I don't mind being a guinea pig(let) to test things out, bring it on. I'll analyze it and report back as good as I can. Can't tell ya how many times in the last weeks I switched Java, MRL versions, to figure out the differences.


on my wish list?, a good chatbot. I think the more interactive the robot can become the better it is. One off the reasons i switched to Nixie is that in manticore, I could not get rid of calls to askpannous, which would cause the chatbot to 'freeze' in its tracks. 


I think on a sooner timescale, IF you are working on the torso bit anyway, how about incorporating for upper, mid AND lower Stom? right now it looks only upper and mid stomach are in the configfile and skeleton_torso???


 


anyway, easy is good, creating gestures easier would be a very nice additions


 


Oh and i learned a new trick today. Been looking for a replacement for the unix/linux Tail command to follow myrobotlab.log on a windows machine. .. One can use PowerShell with the following one-liner:   "Get-Content /nixie/myrobotlab.log -Wait"


Tally HO Guys, time for bed here, lemme know when the stomach bit starts working so I can move on with my project.


 


 



      
    
          
  • 
      

    

  







    

  

    

      

  


    

  

  

    

      
rv8flyboy

      
3 years 6 months ago

                

    

              
        

        
            
            
Being a tinkerer in heart and body, mechanics, electronics, the works, I like to 'improve' on things, my latest quest is to incorporate a better servo control for the articulating stomach. my idea is to use a BNO055 3 axis sensor to measure tilt in 2 directions, sideways, front to back. and use this signal to control the servos. I would like to use the acme threads used in 3D printers to replace the plastic threads used in various locations as they are prone to breaking. However, that means that the servos will need external feedback as they now have to be multi turn. I want to capture the servo signal from the arduino mega for the stomach control, and want to mix this with the tilt and roll info to drive the servo (the capture part is working, the BNO055 part is working, now figuring out driving the servos.


I was raking my brains as I need to take the pot out of the servo to make them multi rotational. There are some ideas on thingiverse to mount these pots externally but because the movement in 2 axis (rather than Gael's single axis) these solutions look ungainly. So I was gonna drive the servo with a separate H bridge, remove the existing electronics.


It struck me I could remove the existing pot and use a 2 resistor voltage divider. basically a pot in a fixed middle position. Then use a regular PWM servo signal to drive the existing servo controller, less than 90 degrees, the servo drives one way, more than 90 degress, the servo drives the other way. HA, so now I can go take the new servo signal directly from an arduino nano output if I have to... simple...


 


 



      
    
          
  • 
      

    

  















    

  

    

      

  


    

  

  

    
    

              
        

        
            
            
Hi Gael


Great Thanks.


 


as a suggestion, why not populate the values for low stomach also as standard in config/skeleton_torso.config?


I.e.:



	[SERVO_MINIMUM_MAP_OUTPUT]



	;your servo minimal limits



	topStom=60



	midStom=60



	lowStom=60



	 



	[SERVO_MAXIMUM_MAP_OUTPUT]



	;your servo maximal limits



	topStom=120



	midStom=120



	lowStom=120



	 



	[SERVO_REST_POSITION]



	topStom=90



	midStom=90



	lowStom=90



	.



	etc



	.



	etc.



	 



	for those who have the full articulating stomach.



	This probably means also populating skeleton/torso.py



	 



	just a thought



      
    
          
  • 
      

    

  








    

  

    

      

  


    

  

  

    
    

              
        

        
            
            
Hello,


okay it's now populated and should be available with the next build.


I have done it for InMoov(1) and InMoov2


The original goal was to remove InMoov (1) in Nixie, but there is still plenty of work to get InMoov2 fully stable.



      
    
          
  • 
      

    

  








    

  

    

      

  


    

  

  

    
    

              
        

        
            
            
Hi Gael


Thanks!!


did you also populate skeleton/torso.py??


 


there is a small issue with torso, the software does not populate the controller choice, after startup i have to manually choose left arduino and attach. This is a fairly new issue. 


I will look at inmoov2 when I have a free moment 


 


 


 



      
    
          
  • 
      

    

  














    

  

    

      

  


    

  

  

    
    

              
        

        
            
            
when will the updated START_INMOOV.bat and the updated torso files propagate into the release version?


Just downloaded 401 and the files were not in there yet.


 



      
    
          
  • 
      

    

  








    

  

    

      

  


    

  

  

    
    

              
        

        
            
            
Hello,


They are already updated in InMoov2 because the correct directory is pulled during the build process.


As you may have followed on the chatbox, Grog and Kwatters are setting up a new oven to bake the cookies, and by the way making the build process for InMoov, InMoov2 and ProgramAB a simpler task for them.


But apparently during this process the wrong directory for InMoov was chosen.


Grog is aware about the issue.



      
    
          
  • 
      

    

  








    

  

    

      

  


    

  

  

    
    

              
        

        
            
            
Hi Gael


for inmoov2, in config/skeleton.torso.config:


I think the following lines need changing:



	[MINIMUM_MAP_INPUT]



	topStom=60 ==> topStom=0



	midStom=60 ==> midStom=0



	lowStom=0



	 



	[MAXIMUM_MAP_INPUT]



	topStom=120 ==> topStom=180



	midStom=120 ==> midStom=180



	lowStom=180



      
    
          
  • 
      

    

  








    

  

    

      

  


    

  

  

    

      
hairygael

      
3 years 6 months ago

                    
          

    

              
        

        
            
            
Hello,


No these should not be changed yet in Nixie. We need the restriction at the input to avoid brackage of parts.


It is the same for the arms, we have input limitations:


[MINIMUM_MAP_INPUT]

	bicep=0

	rotate=40

	shoulder=0

	omoplate=10


	[MAXIMUM_MAP_INPUT]

	bicep=90

	rotate=180

	shoulder=180

	omoplate=80



      
    
          
  • 
      

    

  







    

  

    

      

  


    

  

  

    
    

              
        

        
            
            
Hi Gael


 


in config/skeleton_torso.config (nixie at least) the values are reversed for:



	[SERVO_MINIMUM_MAP_OUTPUT]



	;your servo minimal limits



	topStom=0



	midStom=0



	 





		[SERVO_MAXIMUM_MAP_OUTPUT]



		;your servo maximal limits



		topStom=180



		midStom=180




and the values for



	[MINIMUM_MAP_INPUT]



	topStom=60



	midStom=60



	 





		[MAXIMUM_MAP_INPUT]



		topStom=120



		midStom=120



		 


so [SERVO_MINIMUM_MAP_OUTPUT] and [MINIMUM_MAP_INPUT] labels need to swap


and [SERVO_MAXIMUM_MAP_OUTPUT] and [MAXIMUM_MAP_INPUT] labels need to swap


 


currently the file says that the output swing of the servo is always 180 degrees




 



      
    
          
  • 
      

    

  








    

  

    

      

  


    

  

  

    

      
hairygael

      
3 years 6 months ago

                    
          

    

              
        

        
            
            
I suspect that we have something swapped in java, I will check if I can find that problem.



      
    
          
  • 
      

    

  







    

  

    

      

  


    

  

  

    
    

              
        

        
            
            
Hi Gael


 


in config/skeleton_torso.config (nixie at least) the values are reversed for:



	[SERVO_MINIMUM_MAP_OUTPUT]



	;your servo minimal limits



	topStom=0



	midStom=0



	 





		[SERVO_MAXIMUM_MAP_OUTPUT]



		;your servo maximal limits



		topStom=180



		midStom=180




and the values for



	[MINIMUM_MAP_INPUT]



	topStom=60



	midStom=60



	 





		[MAXIMUM_MAP_INPUT]



		topStom=120



		midStom=120



		 


so [SERVO_MINIMUM_MAP_OUTPUT] and [MINIMUM_MAP_INPUT] labels need to swap


and [SERVO_MAXIMUM_MAP_OUTPUT] and [MAXIMUM_MAP_INPUT] labels need to swap


 


currently the file says that the output swing of the servo is always 180 degrees




 



      
    
          
  • 
      

    

  







    

  

    

      

  


    

  

  

    

      
rv8flyboy

      
3 years 6 months ago

                

    

              
        

        
            
            
nixie 1.1.398 wont install


clean empty directory


I use java -jar myrobotlab.jar --install


 


 


this is end of log file


 



	10:30:57.754 [main] INFO c.m.f.Service [Service.java:860] Repo info installProgress 



	10:30:57.755 [main] INFO c.m.f.Service [Service.java:860] Repo warn installProgress :: problems summary ::



	10:30:57.756 [main] INFO c.m.f.Service [Service.java:860] Repo warn installProgress :::: WARNINGS



	10:30:57.757 [main] INFO c.m.f.Service [Service.java:860] Repo warn installProgress  [NOT FOUND  ] inmoov.fr#inmoov;1.1.22!inmoov.jar (75ms)



	 



	10:30:57.757 [main] INFO c.m.f.Service [Service.java:860] Repo warn installProgress  ==== myrobotlab: tried



	 



	10:30:57.759 [main] INFO c.m.f.Service [Service.java:860] Repo warn installProgress    http://repo.myrobotlab.org/artifactory/myrobotlab/inmoov/fr/inmoov/1.1…



	 



	10:30:57.761 [main] INFO c.m.f.Service [Service.java:860] Repo warn installProgress  ::::::::::::::::::::::::::::::::::::::::::::::



	 



	10:30:57.762 [main] INFO c.m.f.Service [Service.java:860] Repo warn installProgress  ::              FAILED DOWNLOADS            ::



	 



	10:30:57.763 [main] INFO c.m.f.Service [Service.java:860] Repo warn installProgress  :: ^ see resolution messages for details  ^ ::



	 



	10:30:57.763 [main] INFO c.m.f.Service [Service.java:860] Repo warn installProgress  ::::::::::::::::::::::::::::::::::::::::::::::



	 



	10:30:57.764 [main] INFO c.m.f.Service [Service.java:860] Repo warn installProgress  :: inmoov.fr#inmoov;1.1.22!inmoov.jar



	 



	10:30:57.764 [main] INFO c.m.f.Service [Service.java:860] Repo warn installProgress  ::::::::::::::::::::::::::::::::::::::::::::::



	 



	 



	10:30:57.765 [main] INFO c.m.f.Service [Service.java:860] Repo info installProgress 



	:: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS



	10:30:57.768 [main] INFO c.m.f.Service [Service.java:860] Repo info installProgress :: retrieving :: org.myrobotlab#myrobotlab-core



	10:30:57.769 [main] INFO c.m.f.Service [Service.java:860] Repo info installProgress  confs: [compile, runtime, test]



	10:30:58.229 [main] INFO c.m.f.Service [Service.java:860] Repo info installProgress  conflict on C:\nixie\libraries\jar\[originalname].jar in [compile]: 0.3.13-1.5.5 won



	10:32:18.588 [main] INFO c.m.f.Service [Service.java:860] Repo info installProgress  728 artifacts copied, 0 already retrieved (2284208kB/80819ms)



	10:32:18.590 [main] ERROR c.m.f.Service [Service.java:857] runtime error download failed: inmoov.fr#inmoov;1.1.22!inmoov.jar



	10:32:18.591 [main] ERROR c.m.f.Service [Service.java:857] runtime error download failed: inmoov.fr#inmoov;1.1.22!inmoov.jar



	10:32:18.591 [main] ERROR c.m.f.Service [Service.java:857] runtime error download failed: inmoov.fr#inmoov;1.1.22!inmoov.jar



	10:32:18.592 [main] ERROR c.m.f.r.Repo [IvyWrapper.java:456] had errors - repo will not be updated



	10:32:18.610 [main] INFO c.m.s.Runtime [Runtime.java:1300] stopping service security@giddy-robot-launcher



	10:32:18.612 [security] INFO c.m.f.Service [Service.java:2078] security info shutting down



	10:32:18.613 [runtime] INFO c.m.f.Service [Service.java:2078] runtime info shutting down



	10:32:18.613 [runtime_outbox_0] INFO c.m.f.MethodCache [MethodCache.java:155] already cached Runtime methods



      
    
          
  •