If you uncomment the USR_CXXFLAGS line from omsAsynApp/srcMakfile: https://urldefense.us/v3/__https://gcc02.safelinks.protection.outlook.com/?url=https*3A*2F*2Fgithub.com*2Fepics-motor*2FmotorOmsAsyn*2Fblob*2Fc0ae4c740d699e64f264ce6f53f23a492abf19fa*2FomsAsynApp*2Fsrc*2FMakefile*23L8&data=05*7C02*7Ctech-talk*40aps.anl.gov*7C7e3fe92b9b424215f20008de69b98d6c*7C0cfca18525f749e38ae7704d5326e285*7C0*7C0*7C639064442806712722*7CUnknown*7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ*3D*3D*7C0*7C*7C*7C&sdata=IsSeeSktdQtqxbUAm78EBMPBRKKuaeeVMwjL6twDhJc*3D&reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJQ!!G_uCfscf7eWS!dHAFdnK_8UCdKq79G1haFr6fBekEzpWidjPb_DFqdwo4ay3zoLBMSFNLS5cE3c_-4xyP5YpScJ97LyAV-ZVAUZk$ and uncomment the motorOMSBASEdebug variable in omsAsynMAXnetSupport.dbd: https://urldefense.us/v3/__https://gcc02.safelinks.protection.outlook.com/?url=https*3A*2F*2Fgithub.com*2Fepics-motor*2FmotorOmsAsyn*2Fblob*2Fc0ae4c740d699e64f264ce6f53f23a492abf19fa*2FomsAsynApp*2Fsrc*2FomsAsynMAXnetSupport.dbd*23L2&data=05*7C02*7Ctech-talk*40aps.anl.gov*7C7e3fe92b9b424215f20008de69b98d6c*7C0cfca18525f749e38ae7704d5326e285*7C0*7C0*7C639064442806731460*7CUnknown*7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ*3D*3D*7C0*7C*7C*7C&sdata=8*2FNXRHoWvIBsMbSZGt4*2F7b2YGiRabV0Fymtm9Xn1kKc*3D&reserved=0__;JSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUlJSUl!!G_uCfscf7eWS!dHAFdnK_8UCdKq79G1haFr6fBekEzpWidjPb_DFqdwo4ay3zoLBMSFNLS5cE3c_-4xyP5YpScJ97LyAVTJLwSnw$ and rebuild motorOmsAsyn and the IOC, you should then be able to set the variable on the IOC's shell: var("motorOMSBASEdebug", 4) which should result in a "setting Problem flag" message being printed. Kevin