Hello On Wed, Mar 12, 2014 at 7:31 PM, Kujawski, Joseph <[email protected]> wrote: > Jack, > > Thanks. For reference, the way to enter the command in the KATCP directly > (at least in my version) is: > > ?tap-start Riometer0 one_GbE 192.168.6.29 4321 02:02:00:00:00:00 > > Where > Riometer0 - name of the device > one_GbE - Simulink name of the yellow block > 192.168.6.29 - IP Address > 4321 - Fabric Port address > 02:02:00:00:00:00 - MAC address (built into the yellow block).
what does ?tap-info say ? If you don't have that command consider upgrading, as it will tell you about its arp table contents. > I still do not get pings to this device (or anything useful), but I am > getting this message in the KATCP window: > > #log info 964232438571 raw > detected\_time\_warp\_or\_stall,\_rescheduling\_periodic\_task\_for\_964232438.574052s > #log info 964232439151 raw > detected\_time\_warp\_or\_stall,\_rescheduling\_periodic\_task\_for\_964232439.154737s > #log info 964232439732 raw > detected\_time\_warp\_or\_stall,\_rescheduling\_periodic\_task\_for\_964232439.735326s > #log info 964232440313 raw > detected\_time\_warp\_or\_stall,\_rescheduling\_periodic\_task\_for\_964232440.315948s Impressive error. Are you running ntpd or similar ? Is it slewing the time ? Or is there something else competing for CPU time ? [Unrelated: It is probably a good idea to trim list emails to the important material - it makes searching list archives much more pleasant as it eliminates numerous duplicates] regards marc
