@Nikos-Mavr I have an extra ac1300 to use that lsusb recognizes but I don't think the driver is implemented. Ac600 Antenna might be malfunctioning after all because even if it lights up on other pcs and identifies WiFis it cannot connect. Is there a way to implement a driver for ac1300?
Posts made by Nikos Mavr
-
RE: No Wifi Interface Detectedposted in Ask your questions right here!
-
No Wifi Interface Detectedposted in Ask your questions right here!
Hi all,
while I was making some changes on voxl2, the Wifi antenna stopped blinking.
The message is:
Configuring 2ghz SoftAP mode...
No WiFi interface detected
SoftAP mode configured on 2ghz!
The devices works perfectly on other PCs and other USB devices are recognised by voxl2 on the same port. This one cannote get recognised.
The Antenna is the AC600. -
RE: I2C reading of 12S batteryposted in Support Request Format for Best Results
@Nikos-Mavr Oh wow, it works now. Thank you for your help. By the way during this process my tp link antenna stopped responding and when I do voxl-wifi it says wifi devices not detected, while the device works for other PCS and voxl recognizes other USB devices. Are there any ideas why?
-
RE: I2C reading of 12S batteryposted in Support Request Format for Best Results
@Eric-Katzfey upgraded to latest SDK now it is smooth
pxh> qshell ina226 start -X -b 4
INFO [qshell] Send cmd: 'ina226 start -X -b 4'
INFO [muorb] [uORB] Marking DeviceNode(qshell_req) as advertised in process_remote_topic
INFO [muorb] [qshell] qshell gotten: ina226 start -X -b 4
INFO [muorb] [qshell] arg0 = 'ina226'
INFO [muorb] [qshell] arg1 = 'start'
INFO [muorb] [qshell] arg2 = '-X'
INFO [muorb] [qshell] arg3 = '-b'
INFO [muorb] [qshell] arg4 = '4'
INFO [muorb] [drivers__device] *** I2C Device ID 0xd04121 13648161
INFO [uORB] Marking DeviceNode(battery_status) as advertised in process_remote_topic
INFO [muorb] [drivers__device] Set up I2C bus mutex for bus 4
INFO [muorb] ina226 #0 on I2C bus 4
INFO [muorb] (external)
INFO [muorb] address 0x41
INFO [muorb]INFO [muorb] [qshell] Ok executing command: ina226 start -X -b 4
INFO [qshell] qshell return value timestamp: 1170693307, local time: 1170694295 -
RE: I2C reading of 12S batteryposted in Support Request Format for Best Results
@Eric-Katzfey
Thank you for your constant help. Unfortunately, this is what I get with this package with both command and even when I am trying to scan i2c now.
pxh> qshell ina226 start -X -b 4
INFO [qshell] Send cmd: 'ina226 start -X -b 4'
ERROR [uORB] Error Sending [qshell_req] topic data over comm_channel
ERROR [qshell] command timed out
ERROR [qshell] Command failed -
RE: I2C reading of 12S batteryposted in Support Request Format for Best Results
@Vinny yes I removed the level shifter for that setup and yes the voltage drops to 3s for the highlighted area.
-
RE: I2C reading of 12S batteryposted in Support Request Format for Best Results
@Eric-Katzfey Yes, that worked, identified bus 4 channel 41. No while INA228 is enabled, I am not sure whether I should change the power_manager in voxl-px4.conf to NONE or EXTERNAL.
-
RE: I2C reading of 12S batteryposted in Support Request Format for Best Results
@Eric-Katzfey the level shifter works properly with arduino right. The power module is holybro PM02D. Both pins are stuck to high which means communication is not successful.
-
RE: I2C reading of 12S batteryposted in Support Request Format for Best Results
@Eric-Katzfey thank you for the reply. I have tried the j4 with a level shifter and j19 ports. What would be the proper command to see them?
-
I2C reading of 12S batteryposted in Support Request Format for Best Results
Hi all,
I am trying to replace the voxl2 i2c inputs with those of an i2c power module installed closer to the supply source that can read the actual 12S source of the drone I am working on . The problem with this is that even with a level shifter or without I am not able to even find my device with i2cdetect, let alone receive readings. The module uses sen228, but i suspect that the problem could be the different pull up circuit of the different module. Could there be any feedback on that?

