=var foo=5
#popupshowquestion "User input" foo "One" "Two" "Three"
="User input was "+foo
When I run the above with V142 I get the pop up with the three buttons. But, no matter what button I push the last line shows variable foo un-modified at its original value of 5. In debug mode DOS window I see no errors.Once again some great new functionality added, thanks. I am trying to use the #POPUPSHOWQUESTION and having trouble understanding it. I tried the following short script:Code: [Select]=var foo=5
When I run the above with V142 I get the pop up with the three buttons. But, no matter what button I push the last line shows variable foo un-modified at its original value of 5. In debug mode DOS window I see no errors.
#popupshowquestion "User input" foo "One" "Two" "Three"
="User input was "+foo
I had assumed that #POPUPSHOWQUESTION second argument varName meant pushing the buttons would assign one of 0, 1, or 2 to varName. Why doesn't this script's #POPUPSHOWQUESTION change variable foo?
Not sure what macOS Big Sur has broken, but the graphics on the selected tab have gone a bit odd?
Tried it on 2019 27" iMac and 2020 13" MacBook Pro
With the program SignalAnalyzer you can easy view measurements in the time and frequency domain (fft). Also a histogram and a post process filter exists. It has the possibility to easy connect it with a small program to realize live measurements. www.signalanalyzer.de
With the program SignalAnalyzer you can easy view measurements in the time and frequency domain (fft). Also a histogram and a post process filter exists. It has the possibility to easy connect it with a small program to realize live measurements. www.signalanalyzer.de
I could easily add FFT to TestController, but I do not believe that it is very useful at the low frequencies that it is designed for. If SignalAnalyzer can read CSV files and do FFT at low frequencies, it can be used on the log files from TestController.
The low frequencies I am talking about is sample rates at maximum 100Hz often around 1Hz.
Can you please share a csv file, I will trie to import in SignalAnalyzer.
With the program SignalAnalyzer you can easy view measurements in the time and frequency domain (fft). Also a histogram and a post process filter exists. It has the possibility to easy connect it with a small program to realize live measurements. www.signalanalyzer.de
I could easily add FFT to TestController, but I do not believe that it is very useful at the low frequencies that it is designed for. If SignalAnalyzer can read CSV files and do FFT at low frequencies, it can be used on the log files from TestController.
The low frequencies I am talking about is sample rates at maximum 100Hz often around 1Hz.
The Dataset you send is not very good. You need many periods of the signal of interest in you dataset. Maybe you record for a longer time, or decrease the sample rate. Your dataset is a lot over sampled. So the frequency range of interest is only a very small band. Record for low frequency over a much longer time.
Can you please share a csv file, I will trie to import in SignalAnalyzer.
The Dataset you send is not very good. You need many periods of the signal of interest in you dataset. Maybe you record for a longer time, or decrease the sample rate. Your dataset is a lot over sampled. So the frequency range of interest is only a very small band. Record for low frequency over a much longer time.
#verifyDevice txrx? &
:readmath: "S200"
#idString "S200"
#name Kollmorgen S200 Servo
#handle S200
#port com
#eol \_
#comfixedbaud
; 19200 baud, Odd parity, 8 data bits, 1 stop bit
#baudrate 19200O81
#driver SingleValue
But I don't really know what the "SingleValue" driver means/does.I am trying to make a device file for a device with a very low level serial protocol. It is pure binary. It does not use ascii. The PC always sends two binary bytes and gets one binary byte in return. No hand shaking and no end of line characters. When reading the first byte is the address with lsb = 0 for read and the second byte is just a null. The device replies with a single binary byte with the value. When writing the first byte is the address with lsb = 1 for write and the second value is the binary data value to store at the requested address.
How to specify binary values in the writes? While in debug mode when I try txrx? 0x04 0x00 the DOS debug window implies TC sends 0x04 0x00 as 9 ascii characters and does not convert to two binary bytes.
I am trying to make a device file for a device with a very low level serial protocol. It is pure binary. It does not use ascii.
V1.44 contains a new driver called "Block" for this purpose, the driver is NOT finished yet, but can be used.
#verifyDevice txrx1? \0x26 \0x00
:readmath: "S200"
#idString "S200"
#name Kollmorgen S200 Servo
#handle S200
#port com
#comfixedbaud
; 19200 baud, Odd parity, 8 data bits, 1 stop bit
#baudrate 19200O81
;#eol \_
;#driver ascii
;#driver SingleValue
#driver Block
#author gby
Starting
;; Start thread for: COM1 - Kollmorgen S200 Servo
;; COM1: Set params: 19200
java.lang.NullPointerException
at dk.hkj.devices.DeviceBlock$TranslatingCommInterface.cmdIdn(DeviceBlock.java:64)
at dk.hkj.devices.DeviceBlock$TranslatingCommInterface.write(DeviceBlock.java:201)
at dk.hkj.comm.CommInterface.writeRead(CommInterface.java:106)
at dk.hkj.comm.CommInterface.writeRead(CommInterface.java:101)
at dk.hkj.main.InterfaceThreads$DeviceThread.initDevice(InterfaceThreads.java:1340)
at dk.hkj.main.InterfaceThreads$DeviceThread.run(InterfaceThreads.java:1413)
java.lang.NullPointerException
at dk.hkj.devices.DeviceBlock$TranslatingCommInterface.cmdIdn(DeviceBlock.java:64)
at dk.hkj.devices.DeviceBlock$TranslatingCommInterface.write(DeviceBlock.java:201)
at dk.hkj.comm.CommInterface.writeRead(CommInterface.java:106)
at dk.hkj.comm.CommInterface.writeRead(CommInterface.java:101)
at dk.hkj.main.InterfaceThreads$DeviceThread.initDevice(InterfaceThreads.java:1343)
at dk.hkj.main.InterfaceThreads$DeviceThread.run(InterfaceThreads.java:1413)
;; Stopping thread for: COM1 - Kollmorgen S200 Servo
;; COM1: Close
The above happens with the device's serial cable plugged in or not plugged in. So, you should be able to duplicate without any device.