excel4x

The machine (windows 7 VirtualBox VM) just locks up and the only option is to shut it down. I do not want to corrupt my working VM, so I need to set up a separate test VM and see if I can reproduce it. It seems intermittent, so I do not know how successful that will be.

I'll try 2.70 and see what happens. FYI, I have been using 2.0 because I experienced several system crashes when using 2.70. It seemed to happen after changing terminal settings.

Thanks! FYI - I set the log file location to another folder and I checked that folder for log info. Also, the command returns immediately. The text file for sending has some programmed delays, so it takes some time to complete, so I think the command is aborting early in the process.

I am testing yat 2.0 batch file execution oer serial. I am using /tf /ot and /ln options. This appears to work properly. However, I would prefer to have this run in the background without the GUI. If I add /nv then the program terminates immediately without logging any data. I can't tell whether it is sending the text file. Is there a way to run yat without the GUI, but still execute asend file and log data?

OK. BTW, I found another command that uses "\x0B" instead of the calcuated "\X0A". I suspect the device is doing this because "\x0A" is line feed and could stop transmission. I haven't found a CRC spec for the device, but this seems plausible. Because of this I will probably just include the CRC codes directly with the commands.

Thanks for the prompt response! I am not sure. \x prefix seems like what it wants, but I don't know if that is the only reason it is failing. I have also discovered another issue I do not understand. One of the commands is "POP02". The XMODEM CRC is \xE2\x0A". However, the device does not accept this CRC. What it accepts is "\E2\x0B". So, it apparently is not a pure XMODEM CRC. Given this behavior, it may not make sense to add \x - unless there are other use cases that will benefit from it.

I am sending and receiving data from an MPP solar inverter. The inverter appears to be using CRC16-Xmodem based on matching CRC codes. I am using YAT 2.7.0 The following text string works in text mode with EOL=<cr>, Western 1252 encoding. In this case I am providing the CRC: "QPIGS\xB7\xA9"</cr> However, if I tell YAT to append the CRC, it shows: "QPIGSB7A9" If I use 0x hex mode it shows: "QPIGS0xB7A9" But neither of this is accepted by the device. I tried switching to binary mode, but I did not...

I am sending and receiving data from an MPP solar inverter. The inverter appears to be using CRC16-Xmodem based on matching CRC codes. I am using YAT 2.7.0 The following text string works in text mode with EOL=<cr>. In this case I am providing the CRC: QPIGS\xB7\xA9</cr> However, if I tell YAT to append the CRC, it shows: QPIGSB7A9 If I use 0x hex mode it shows: QPIGS0xB7A9 But neither of this is accepted by the device. What settings do I need to have YAT properly append the CRC? Thanks much!