I have created a pull-request on GitHub (github.com/sq6sfo/espBode/pull/4) that enables the full FY6900 instruction set. It hasn't been merged yet, so feel free to clone my repo (github.com/timkoers/espBode) until it is merged.
I saw in your video that the symbol for WIFI cannot be seen in the Oszi. That means that where you shot the video, you connected the ESP8266 yourself via Ethernet and router. In AP mode, do I have to select and connect the WIFI_SSID that I previously specified via the WLAN stick in the SGS1204X-E, OR: Do I enter my WIFI_SSID of my router home network there and can I get access to ESP8266 from the SGS1204X-E with an Ethernet cable via the router? Do I have to go to esp_config.h except: #define WIFI_MODE_AP continue to make entries? What about: #define WIFI_SSID "wlan_ssid" #define WIFI_PSK "wlan_key" or here with: #ifdef STATIC_IP #define ESP_IP 192,168,1,6 #define ESP_MASK 255,255,255,0 #define ESP_GW 192,168,1,1 My SGS1204X-E reports "Unknown AWG found" and I can't get any further. The programming worked without errors and I can access the AP and client from the PC. So where comes "Unknown AWG found"? Please a couple of tips, the rest I'll fight for myself. greetings
You can access the ESP8266 from your scope with the scope connected via both Ethernet and WiFi. You need to make sure the ESP8266 is in STA mode though. You can also directly connect to the ESP8266's AP network with your scope, but you'll need to setup manual IP addresses for both your scope and for the ESP8266. Please use telnet to debug the ESP8266 remotely.
What can I do ? Who can help me, on this point? The WLAN connection is established via the AP and the client. But there is no bodeplot connection. That's why I specifically checked the signal quality and the levels that go into my FY6800 via RX / TX. The signal levels were not good. After using a levelshifter the ESP-01s TX increased 3.3V to 5V and now OK and the SDS does now not hangup. The FY6800 now receives clean signals on the RX input of the FY6800, but does not respond to TX. When I use the USB interface via CH340, the levels are the same and on RX / TX and the FY6800 responds without any problems. What else can I do? - Which FW is on your FY6800? My FW is V 1.7.1.
- Do you have a log of the RX / TX data as a CSV log file where I can see functional communication?
Hi Tim, thanks for your work! I am also trying to get this BodePlot working. However there seems to be a problem with my FY6900. I can connect my sds1104x-e to the esp and start bodeplotting and everything. However the FY6900 just doesn´t care. When I control it with my computer using the integrated USB port it´s working all fine. But not if I connect the ESP-01 in any way (no matter if it´s vonnected through the TTL pins nor the USB port using an UART to USB Converer). I wrote an issue in the original espBode on github from sq6sfo. It would be great if you or someone who might have a clue could look at this and help me. I hope someone can help me! Thanks!
@@TimsElectronicsLab I have tried another ESP. I have also tried using my computer's USB and this a FTDI serial to UART converter. Computer usb worked but not the FTDI
I still have the same problems as you describe elsewhere here. WLAN via client connection and also via AP connection is established. There is probably no problem in the network configuration. But when I configure Bode Plot on the Seglent DSO, either an unknown AWG comes in or the DSO hangs. So I am most likely to assume that the pure communication to the ESP01s and to the AWG itself does not work. The Seglent DSO only reported a successful connection to the AWG once and only for 5 seconds. These are level errors on TX / RX and so I now look at the 300R resistors. Anyone already successfully achieved a change there?
Hi Tim, Why after finish uploading the program my ESP01 doesnt show it connection status. It only show some weird unexplain language and stuck there. Can you help me out?
@@TimsElectronicsLab Hi Tim, thank you for the reply. Yeah the baudrate was setup to 115200. When i inserted/reset the ESP01 after programming, only junk language is shown in serial monitor. It does not respond like in your video whereas junk language > Connecting to > WiFi connected as well IP add stated. Mine only show junk language then it just stuck there and not responding. However if i try to replace "DEBUG" with "Serialprint/Serialprintit", the esp01 is responding, connected to wifi and manage to get the IP. But in this configuration, my scope will completely Freeze when attempt connect to the AWG. Sometime it succesfully connected and sometime not it just froze. Any idea which part i do wrong? AFAIK in the network config.h you only need to set the SSID, pass and Wifi mode right? Again thank you for your response
@@azeemnazri2462 You need to remove #define DEBUG_PRINTS on line 54 in the esp_config.h once you've found your IP address. Then connect the ESP-01 to your AWG and fire it up. The garbage you are seeing is probably the ESP-01 trying to communicate with the AWG. Once the ESP-01 setup, you can open a telnet session with it to view debug output.
@@TimsElectronicsLab Okay after i remove #define DEBUG_PRINTS on line 54, my esp01 finally show same as yours as in the video. But Tim, i got new problem. When trying to connect my 1104xe to the AWG, my scope gone completely freeze cant even restart or do anything. Only thing i can do is remove the mains power and turn on the scope back again. Any idea why the scope freeze when trying to connect with the AWG? I already set my scope with DHCP off
I have compilation problem ? C:\Users\48509\OneDrive\Pulpit\espBode-master\espBode\esp_network.cpp: In function 'uint8_t handleVxi11(uint8_t*, WiFiClient)': C:\Users\48509\OneDrive\Pulpit\espBode-master\espBode\esp_network.cpp:222:1: error: control reaches end of non-void function [-Werror=return-type] 222 | } | ^ cc1plus.exe: some warnings being treated as errors exit status 1 Compilation error: control reaches end of non-void function [-Werror=return-type]
I have created a pull-request on GitHub (github.com/sq6sfo/espBode/pull/4) that enables the full FY6900 instruction set. It hasn't been merged yet, so feel free to clone my repo (github.com/timkoers/espBode) until it is merged.
Great!! Ty 🙂
thanks Tim !
No worries! I hope you enjoy the video
Good connection establishing, thanks! But, I think that you are already aware that you did Bode plot wrong.
I saw in your video that the symbol for WIFI cannot be seen in the Oszi. That means that where you shot the video, you connected the ESP8266 yourself via Ethernet and router.
In AP mode, do I have to select and connect the WIFI_SSID that I previously specified via the WLAN stick in the SGS1204X-E,
OR:
Do I enter my WIFI_SSID of my router home network there and can I get access to ESP8266 from the SGS1204X-E with an Ethernet cable via the router?
Do I have to go to esp_config.h
except:
#define WIFI_MODE_AP
continue to make entries?
What about:
#define WIFI_SSID "wlan_ssid"
#define WIFI_PSK "wlan_key"
or here with:
#ifdef STATIC_IP
#define ESP_IP 192,168,1,6
#define ESP_MASK 255,255,255,0
#define ESP_GW 192,168,1,1
My SGS1204X-E reports "Unknown AWG found" and I can't get any further.
The programming worked without errors and I can access the AP and client from the PC. So where comes
"Unknown AWG found"?
Please a couple of tips, the rest I'll fight for myself.
greetings
You can access the ESP8266 from your scope with the scope connected via both Ethernet and WiFi. You need to make sure the ESP8266 is in STA mode though. You can also directly connect to the ESP8266's AP network with your scope, but you'll need to setup manual IP addresses for both your scope and for the ESP8266. Please use telnet to debug the ESP8266 remotely.
Hello,
I've got an JDS6600 and wonder if it's possible to use your modification . Thanks
Yes it should be, but you'll have to code it yourself
What can I do ? Who can help me, on this point?
The WLAN connection is established via the AP and the client.
But there is no bodeplot connection.
That's why I specifically checked the signal quality and the levels that go into my FY6800 via RX / TX. The signal levels were not good.
After using a levelshifter the ESP-01s TX increased 3.3V to 5V and now OK and the SDS does now not hangup.
The FY6800 now receives clean signals on the RX input of the FY6800, but does not respond to TX.
When I use the USB interface via CH340, the levels are the same and on RX / TX and the FY6800 responds without any problems.
What else can I do?
- Which FW is on your FY6800? My FW is V 1.7.1.
- Do you have a log of the RX / TX data as a CSV log file where I can see functional communication?
I do not have a log of the commands, but there should be one floating on the internet. You can search for FY6900 UART protocol and you'll find it
Hi Tim,
thanks for your work!
I am also trying to get this BodePlot working. However there seems to be a problem with my FY6900.
I can connect my sds1104x-e to the esp and start bodeplotting and everything. However the FY6900 just doesn´t care. When I control it with my computer using the integrated USB port it´s working all fine. But not if I connect the ESP-01 in any way (no matter if it´s vonnected through the TTL pins nor the USB port using an UART to USB Converer).
I wrote an issue in the original espBode on github from sq6sfo. It would be great if you or someone who might have a clue could look at this and help me.
I hope someone can help me!
Thanks!
Try to control the FY6900 manually with the serial port. If that works, try another ESP
@@TimsElectronicsLab I have tried another ESP. I have also tried using my computer's USB and this a FTDI serial to UART converter. Computer usb worked but not the FTDI
@@TimsElectronicsLab or what exactly do you mean by controlling it manually with the serial port?
Try and send the commands that the ESP would normally send to the FY6900. Something totally different, what firmware runs on the FY6900?
@@TimsElectronicsLab I did do send those commands using my PC. It worked when I used USB. I am running Firmware Version 1.4.1
I still have the same problems as you describe elsewhere here.
WLAN via client connection and also via AP connection is established. There is probably no problem in the network configuration. But when I configure Bode Plot on the Seglent DSO, either an unknown AWG comes in or the DSO hangs.
So I am most likely to assume that the pure communication to the ESP01s and to the AWG itself does not work.
The Seglent DSO only reported a successful connection to the AWG once and only for 5 seconds.
These are level errors on TX / RX and so I now look at the 300R resistors.
Anyone already successfully achieved a change there?
Did you connect to telnet? I would do that and see what happens when you connect your scope to it
Hi Tim, Why after finish uploading the program my ESP01 doesnt show it connection status. It only show some weird unexplain language and stuck there. Can you help me out?
Hi Azeem,
Please change the baudrate of your serial monitor to 115200
@@TimsElectronicsLab Hi Tim, thank you for the reply. Yeah the baudrate was setup to 115200. When i inserted/reset the ESP01 after programming, only junk language is shown in serial monitor. It does not respond like in your video whereas junk language > Connecting to > WiFi connected as well IP add stated. Mine only show junk language then it just stuck there and not responding. However if i try to replace "DEBUG" with "Serialprint/Serialprintit", the esp01 is responding, connected to wifi and manage to get the IP. But in this configuration, my scope will completely Freeze when attempt connect to the AWG. Sometime it succesfully connected and sometime not it just froze. Any idea which part i do wrong? AFAIK in the network config.h you only need to set the SSID, pass and Wifi mode right? Again thank you for your response
@@azeemnazri2462 You need to remove #define DEBUG_PRINTS on line 54 in the esp_config.h once you've found your IP address. Then connect the ESP-01 to your AWG and fire it up. The garbage you are seeing is probably the ESP-01 trying to communicate with the AWG. Once the ESP-01 setup, you can open a telnet session with it to view debug output.
@@TimsElectronicsLab Okay after i remove #define DEBUG_PRINTS on line 54, my esp01 finally show same as yours as in the video. But Tim, i got new problem. When trying to connect my 1104xe to the AWG, my scope gone completely freeze cant even restart or do anything. Only thing i can do is remove the mains power and turn on the scope back again. Any idea why the scope freeze when trying to connect with the AWG? I already set my scope with DHCP off
Try to update the firmware of your scope
I have compilation problem ?
C:\Users\48509\OneDrive\Pulpit\espBode-master\espBode\esp_network.cpp: In function 'uint8_t handleVxi11(uint8_t*, WiFiClient)':
C:\Users\48509\OneDrive\Pulpit\espBode-master\espBode\esp_network.cpp:222:1: error: control reaches end of non-void function [-Werror=return-type]
222 | }
| ^
cc1plus.exe: some warnings being treated as errors
exit status 1
Compilation error: control reaches end of non-void function [-Werror=return-type]