User Activity

  • Posted a comment on discussion General Discussion on Snap7

    reading szl: Job.ID =0x0424; Job.Index =0x0000; opData[7]: W#16#0001: STOP (update) W#16#0002: STOP (reset memory) W#16#0003: STOP (self-initialization) W#16#0004: STOP (internal) W#16#0005: STARTUP (cold restart) W#16#0006: STARTUP (warm restart) W#16#0007: STARTUP (hot restart) W#16#0008: RUN (solo mode) W#16#0009: RUN-R (redundant mode) W#16#000A: HOLD W#16#000B: LINK-UP W#16#000C: UPDATE W#16#000D: DEFECTIVE W#16#000E: SELFTEST W#16#000F: NO POWER

  • Modified a comment on discussion General Discussion on Snap7

    hi Davide, i run snap7 on linux and found that DBread cost over 1000ms,bock size was 2000 and plc was s7-400.tcpdump showed timeintval between read request and plc response was almost 300ms.gdb also indicated the program took too much time at TMsgSocket::WaitForData,snap_msgsock.cpp:258,SysSleep(1). here is the loop,snap_msgsock.cpp: 252 while((WaitingData()<size) &&="" (lasttcperror="=0))" {="" checks="" timeout="" if="" (deltatime(elapsed)="">=(longword)(Timeout)) LastTcpError =WSAETIMEDOUT; else...

  • Posted a comment on discussion General Discussion on Snap7

    hi Davide, i run snap7 on linux and found that DBread cost over 1000ms,bock size was 2000 and plc was s7-400.tcpdump showed timeintval between read request and plc response was almost 300ms.gdb also indicated the program took too much time at TMsgSocket::WaitForData,snap_msgsock.cpp:258,SysSleep(1).

  • Posted a comment on discussion Bugs reporting on Snap7

    if (Result==0) { switch (opData[7]) { case S7CpuStatusUnknown : case S7CpuStatusRun : case S7CpuStatusStop : Status=opData[7]; break; default : // Since RUN status is always $08 for all CPUs and CPs, STOP status // sometime can be coded as $03 (especially for old cpu...) Status=S7CpuStatusStop; } } else *Status=0; .......... .......... so we know the status is not always $08 or $04 LUL

  • Posted a comment on discussion Bugs reporting on Snap7

    Set Job.ID as 0x0071 and set Job.Index as 0x0000 then read byte opData[6],the result could be 0x10 or 0x20 or else. 0x10 indicates H status of CPU in rack0 is master CPU,0x20 means rack1's CPU is master. See the s7sfc_en-EN.pdf in page 730: 34.19 SSL-ID W#16#xy71 - H CPU Group Information System Software for S7-300/400 System and Standard Functions Volume 2/2 730 Reference Manual, 05/2010, A5E02790053-01 Contents Length Meaning Mwstat2 1 byte Status byte 2 Bit 0: Status of the synchronization link-up...

View All

Personal Data

Username:
novara
Joined:
2018-12-26 01:19:00

Projects

  • No projects to display.

Personal Tools

MongoDB Logo MongoDB