![]() the fact that the timeout value is not saved, always reset to 25ms after start of UCCNC. Mach3 will not add automaticaly any choice for Port Num.: but this will be the same port you have seen in the modbus tester application so if it was showing Com5 write in Port Num.: 5. I don't see a pattern in when this is happening, but there is definitely a pattern in the first part, i.e. In Mach 3 go to top menu->setup serial modbus controll and in popup window press test modbus. Is there any possible work-around this? Even if it means some quick and dirty patch, I'd be very happy if this could be fixed somehow.Īlso, some times the loaded settings are totally wrong, for example port number field is empty, bps is set to 9600, RS485 is unselected. Question: How to configure 2.2KW VFD for Modbus communication with Mach3. I tried to find out where that 25 comes from so I could manually patch it but it seems impossible. Changing timeout to 100ms (even 75ms) solves the problem, but the value is not saved, so next time I restart it is reset to 25ms. The video title is Mach3 and MPG Modbus by Cesar Mendoza, and the authors name is Cesar Mendoza. When Mach3 reads an input that weve mapped to our MODBUS device it actually reads the MODBUS configuration buffer in memory (Cfg1) in this case. ![]() ![]() The Timeout value is not saved and is reset every time I restart UCCNC, as a result the Modbus communication is not reliable because the 25ms default value is far too short, so messages simply time out, read values become unreliable and random. The following is saved in Default.pro file: There seems to be a bug in the Modbus handling. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
March 2023
Categories |