1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 <2022> 2023 2024 2025 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 <2022> 2023 2024 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | vxworks booting werid script and I can't moving motor |
From: | whitetiger1123 via Tech-talk <tech-talk at aps.anl.gov> |
To: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
Date: | Tue, 13 Dec 2022 16:11:37 +0900 |
Hi, Recently I set up booting vxworks and I saw my motor stage moving well. But today I try to moving motor stage, it does not connect CSS. I set up css ip(edit>preferences>css core>epics>addr_list as 10.4.49.170) correctly. When I booting vxworks, I can see this weird script. I’ve never seen this script before when I booting vxworks This is my weird script: ## Support for the OMS MAXv (VxWorks shell or iocsh) < MAXv.cmd dbLoadTemplate("MAXv.substitutions") value = 0 = 0x0 # OMS MAXv driver setup parameters: # (1)number of cards in array. # (2)VME Address Space - A(16,24,32). # (3)Base Address (see motorOms/omsApp/src/README). # (4)interrupt vector (0=disable or 64 - 255). # (5)interrupt level (2 - 6). # (6)motor task polling rate (min=1Hz,max=60Hz). MAXvSetup(1, 16, 0xF000, 200, 5, 10) value = 0 = 0x0 #!MAXvSetup(1, 24, 0xFF0000, 200, 5, 10) #!MAXvSetup(1, 32, 0xFF000000, 200, 5, 10) #!drvMAXvdebug=4 # OMS MAXv configuration string: # (1) number of card being configured (0-14). # (2) configuration string; axis type (PSO/PSE/PSM) MUST be set here. # For example, set which TTL signal level defines an active limit # switch. The "config" example below sets X,Y,Z,T to active low (LTL), # sets U,V,R,S to active high (LTH) and sets all axes to open-loop # stepper (PSO). See MAXv User's Manual for LTL/LTH and PSO/PSE/PSM # commands. # config="AX LTL PSO; AY LTL PSO; AZ LTL PSO; AT LTL PSO; AU LTH PSO; AV LTH PSO; AR LTH PSO; AS LTH PSO;" # (3) SSI based absolute encoder bit flag. Bit #0 for Axis X, bit #1 for # Axis Y, etc.. Set a bit flag to '1' for absolute encoder values; '0' # for the standard incremental encoder values. # (4) SSI based absolute encoder grey code flags (0/1 - yes/no, 0x12 -> UY) # The max command-line length of the VxWorks shell is 128 chars str = malloc(200); New symbol "str" added to kernel symbol table. str = 0x4521ed0: value = 72530704 = 0x452bb10 strcpy str, "AA; LMH,H,H,H,H,H,H,H;" value = 72530704 = 0x452bb10 strcat str, "AX LTH PSO; AY LTH PSO; AZ LTL PSO; AT LTL PSO; AU LTL PSO; AV LTL PSO; AR LTL PSO; AS LTL PSO;" value = 72530704 = 0x452bb10 MAXvConfig(0, str, 0, 0) value = 0 = 0x0 free(str) value = 0 = 0x0 #< MAXv.iocsh ## Support for the OMS VME85 #< VME58.cmd ## Support for the OMS VME8 and VME44 #< VME8.cmd ## Support for the OMS PC68 and PC78 (requires asyn) #< PC68.cmd iocInit Starting iocInit ############################################################################ ## EPICS R3.15.6 ## EPICS Base built Oct 7 2022 ############################################################################ data access Exception current instruction address: 0x0x0497f08400 Machine Status Register: 0x1347d80000 b032 Data Access Register: 0xvxTaskEnt91014100ry Condition Register: 0x 28000284+0x Data storage interrupt Register: 0x4842000000 : 0x0022bbbc () 0x0022bbbc shellTask +0x488: shellExec () 0x0022b6b0 shellExec +0x12c: 0x0021ea30 () 0x0021ec64 shellInterpCInit+0x3f0: shellInterpCparse () 0x0021e590 shellInterpCparse+0xa5c: 0x00221668 () 0x00221698 shellInterpCInit+0x2e24: 0x00221a28 () 0x00221a68 shellInterpCInit+0x31f4: 0x00221b24 () 0x00221be0 shellInterpCInit+0x336c: shellInternalFunctionCall () 0x00219790 shellInternalFunctionCall+0xac : 0x04a58bb8 () 0x04a58bd0 iocInit +0x1c : iocBuild () 0x04a58b50 iocBuild +0x60 : 0x04a585d8 () 0x04a58670 iocRun +0x8f4: 0x0497fd20 () 0x049800d4 MAXV_send_recv_mess+0xd38: 0x0497ef1c () Done executing startup script 'host:/home/test/epics/synApps_6_1/support/motor-R7-1/modules/motorOms/iocs/omsIOC/iocBoot/iocOms/st.cmd'. I can see my pv is well when I typed “dbl” oms:m1_vCh oms:m1_twCh oms:m2_vCh oms:m2_twCh oms:m3_vCh oms:m3_twCh oms:m4_vCh oms:m4_twCh oms:m5_vCh oms:m5_twCh oms:m6_vCh oms:m6_twCh oms:m7_vCh oms:m7_twCh oms:m8_vCh oms:m8_twCh oms:m1 oms:m2 oms:m3 oms:m4 oms:m5 oms:m6 oms:m7 oms:m8 oms:movingDiff oms:alldone oms:alldoneBlink oms:allstop oms:m1_able oms:m2_able oms:m3_able oms:m4_able oms:m5_able oms:m6_able oms:m7_able and css motor opi’s pv is oms:m1 and oms:m2. I really want to know how to fix this problem thanks |