Thank You to everyone involved in the last 48 hours of SSA to SVA FW crossflasing experimentation
Its amazing what you can learn in 48 hours
Special thanks to tv84 for his helping hand in helping us to 'get up' when we fall along the path (best analogy I could think of this late at night)
Now its time to check out the fully loaded SVA to see if she lives up to her potential
Thank You to everyone involved in the last 48 hours of SSA to SVA FW crossflasing experimentation
Its amazing what you can learn in 48 hours
Special thanks to tv84 for his helping hand in helping us to 'get up' when we fall along the path (best analogy I could think of this late at night)
Now its time to check out the fully loaded SVA to see if she lives up to her potential
Clearly more work to be done by tv84 and I.. pro mode has exposed more options on your main menu!
Also as far as your name hack... thats not the important one.. ;p It does still think of itself as an SSA at the kernel level, the true conversion will most likely take tv84/myself getting a hold of a copy of the SVA base software that we can dissect as what siglent posts truly are just patches.. not the entire OS
usbtmc_para = insmod /usr/bin/siglent/drivers/g_usbtmc.ko idVendor=0xf4ec idProduct=0x1305 iManufacturer=Siglent iProduct=SSA3032XPlus iSerialNum=SSABBBBBCCCDDD
Thank You to everyone involved in the last 48 hours of SSA to SVA FW crossflasing experimentation
Its amazing what you can learn in 48 hours
Special thanks to tv84 for his helping hand in helping us to 'get up' when we fall along the path (best analogy I could think of this late at night)
Now its time to check out the fully loaded SVA to see if she lives up to her potential
Clearly more work to be done by tv84 and I.. pro mode has exposed more options on your main menu!
Also as far as your name hack... thats not the important one.. ;p It does still think of itself as an SSA at the kernel level, the true conversion will most likely take tv84/myself getting a hold of a copy of the SVA base software that we can dissect as what siglent posts truly are just patches.. not the entire OS
usbtmc_para = insmod /usr/bin/siglent/drivers/g_usbtmc.ko idVendor=0xf4ec idProduct=0x1305 iManufacturer=Siglent iProduct=SSA3032XPlus iSerialNum=SSABBBBBCCCDDD
Interesting
Yeah, the name hack is nothing
- change in NSP_trends_config_info
- I think you are correct it simply modifies some internal tag but nothing in the base software, as there are other snags which revert to the SSA
The serial number is also a problem
- easy way is to use the SCPI :SRLN <serial_num> command.
- This works , but it will wipe your license settings.
Not sure if there is a proper license number 'fix' which does not screw with the system??
- not a fan of doing temp paches which are prone to failure
These two things are certainly challenging - short of patching hex files (not recommended) would be great to have a nice solution that does not get wiped with FW updates.
BTW
Has anyone got their WEB Server interface working??
Not sure what I'm doing wrong - but having problems in connecting
EDIT: Its OK - my network cable was loose - the plastic clip which secures the cable into the socket snapped-off and cable was loose.
Should have noticed this on the SVA screen - there is a blue symbol in top RH corner - indicating an active connection, was too busy trying to figure out what's wrong rather than checking cable or looking at screen - I guess too much fiddling for one day
Thank You to everyone involved in the last 48 hours of SSA to SVA FW crossflasing experimentation
Its amazing what you can learn in 48 hours
Special thanks to tv84 for his helping hand in helping us to 'get up' when we fall along the path (best analogy I could think of this late at night)
Now its time to check out the fully loaded SVA to see if she lives up to her potential
Clearly more work to be done by tv84 and I.. pro mode has exposed more options on your main menu!
Also as far as your name hack... thats not the important one.. ;p It does still think of itself as an SSA at the kernel level, the true conversion will most likely take tv84/myself getting a hold of a copy of the SVA base software that we can dissect as what siglent posts truly are just patches.. not the entire OS
usbtmc_para = insmod /usr/bin/siglent/drivers/g_usbtmc.ko idVendor=0xf4ec idProduct=0x1305 iManufacturer=Siglent iProduct=SSA3032XPlus iSerialNum=SSABBBBBCCCDDD
Interesting
Yeah, the name hack is nothing
- change in NSP_trends_config_info
- I think you are correct it simply modifies some internal tag but nothing in the base software, as there are other snags which revert to the SSA
The serial number is also a problem
- easy way is to use the SCPI :SRLN <serial_num> command.
- This works , but it will wipe your license settings.
Not sure if there is a proper license number 'fix' which does not screw with the system??
- not a fan of doing temp paches which are prone to failure
These two things are certainly challenging - short of patching hex files (not recommended) would be great to have a nice solution that does not get wiped with FW updates.
There is
Thanks for the tip with SCPI wiping out the license file... interesting option for something I am investigating now and it appears the license file low level itself is key to unlocking more features than just changing the program and typing the keys in
Have just completed my crossflash successfully, only extra step was to make the filesystem writable.
Do we know why some of the licenses disappear (particularly Refl) or is it not an issue?
Before:
(Attachment Link)
After:
(Attachment Link)
Shouldnt be an issue, from my investigations the program will use only the licenses that the hardware AND program can use
This stemming from that ALL can license everything but only adds into the license files the correct options for the given hardware and program executable
This is why you can see the real time options in pro mode for the VNA program even though the hardware cant handle that.. i did try and it put out bus errors that it could not contact the needed components.
But once you license the unit it will return only the ones it should have and the realtime options drop off completely.. not even being a disabled option
Have just completed my crossflash successfully, only extra step was to make the filesystem writable.
Do we know why some of the licenses disappear (particularly Refl) or is it not an issue?
Before:
(Attachment Link)
After:
(Attachment Link)
Yeah, when I first found this - I was very impressed at the level of work he did - even all the SimSmith stuff - excellent information, not to mention the fantastic insight into getting 'linear rf response' in SMD resistors - 2 x 100 in parallel better response than 1 x 50 - however does not scale beyond the 2 - very interesting stuff.
I guess once the SVA's VNA option is calibrated - we can then investigate how to 'home' the calibrations for the instrument to ensure the measurements we make ourselves thereafter are accurate
- not sure if the above statement made sense - I just wanted to use the 'bootstrap' effect - get going first - then use device to improve
Shouldnt be an issue, from my investigations the program will use only the licenses that the hardware AND program can use
This stemming from that ALL can license everything but only adds into the license files the correct options for the given hardware and program executable
This is why you can see the real time options in pro mode for the VNA program even though the hardware cant handle that.. i did try and it put out bus errors that it could not contact the needed components.
But once you license the unit it will return only the ones it should have and the realtime options drop off completely.. not even being a disabled option
Ok, thank you
Of course I suppose that Refl from the SSA is now redundant as you have a VNA that supersedes it.
Have just completed my crossflash successfully, only extra step was to make the filesystem writable.
Do we know why some of the licenses disappear (particularly Refl) or is it not an issue?
Before:
(Attachment Link)
After:
(Attachment Link)
Shouldnt be an issue, from my investigations the program will use only the licenses that the hardware AND program can use
This stemming from that ALL can license everything but only adds into the license files the correct options for the given hardware and program executable
This is why you can see the real time options in pro mode for the VNA program even though the hardware cant handle that.. i did try and it put out bus errors that it could not contact the needed components.
But once you license the unit it will return only the ones it should have and the realtime options drop off completely.. not even being a disabled option
Can you confirm that 'EMI Measurement' is a valid license option for the SVA?
If it is, why is it then that it is no longer visible in the Mode Options menu?? (see screenshot from tubularnut)
(I suspect we might be indirectly involved at solving same problem )
There are in fact TWO forms of EMI
One is a basic EMI that is limited to you having to use it in scanner mode over your given range
the other is REAL TIME EMI and is the 6th option in the mode list for a real time SA
That is what you are seeing
There are in fact TWO forms of EMI
One is a basic EMI that is limited to you having to use it in scanner mode over your given range
the other is REAL TIME EMI and is the 6th option in the mode list for a real time SA
That is what you are seeing